Been having a problem with NT 4 systems at work. When a user logs into the sytem(on a domain, although the profile is stored locally), one out of 3 times the startup/desktop settings fail to run.
Any ideas?
Printable View
Been having a problem with NT 4 systems at work. When a user logs into the sytem(on a domain, although the profile is stored locally), one out of 3 times the startup/desktop settings fail to run.
Any ideas?
Oh yes I will also add that systems that don't experience this right out of the box never do. And ones that do experience it out of the box... it never goes away.
What are you running for workstations?
Also explain this a little better.Quote:
Originally posted by Bjackso:
Oh yes I will also add that systems that don't experience this right out of the box never do. And ones that do experience it out of the box... it never goes away.
Workstations? Dells. Um new optiplex ones and 3 year old ones aswell. Both have the issue...
Again on NT 4.
On what you want clarified:
When I first set-up the PC it will begin doing it right away, and I can't fix it, and it dosn't go away. Maybe one out of 20 PCs will do it. None of the others will. the PC setup process is the same on all PCs.
If the PC doesn't experience the profail problem right away it never does... the problem isn't one that appears later in the PCs life cycle.
Hope that helps...
All these PCs are aprt of a Domain aswell if you might think it is a glitch with the Domain controller.
Could it be that those PCs are authenticating to a BDC and the profiles are on a different Server?
I know that if you have policies and other on one server that you need to replicate the Netlogon folder to all the servers so they all get that info.
http://support.microsoft.com/support.../Q256/1/42.ASP This looks like a good possibility. Had to do a little research.
To answer both people :)
Ok, the profiles are stored locally on the PCs hard-drive. If they do somehow go into roaming mode(and thus get stored on the server), they would be on the same server they log into.
As per the memory leak issue. That is a problem that would cause the profile to be totally replaced, and would require the user to be using a roaming profile(this is rare here allmost everyone uses the profile locally)
Hmm on second thought I may have classified the problem wrong. Only certain parts of the profile appear to not load(i'll look into this again), I think it may just be items in the Startup folder for the user will not load. In fact items in the "all users" startup folder will fail(ONLY for the problematic user profile, not Administrator or other users).