November 12, 2008
1:55 am

In second part of Understanding How to Read a Userenv Log (Part 1), most of the time when we need to enable Userenv logging is due to a delay of getting to the desktop after entering our credentials. Normally the user will be stuck at “Applying Personal Settings” is most often the scenario we see. The problem can stem from several different problems. One can be that another process, usually the anti-virus, has a lock on a file within the profile and cannot open the file. When this happens the user will get a new default profile. A reboot of the client will temporarily resolve this forcing all handles to be released. This does not always work but at times it will allow the user to logon and receive his old profile. Eventually the problem will come back. There also could be permissions issue or network issues when attempting to load a roaming profile. There are many different scenarios that plague users and loading their profiles.

Full Article

Loading

Contextual Related Posts:

No followup yet

Leave a Response

Comment Preview
« How to read a Userenv Log in Vista or Windows Server 2008 – Part 1Upgrade to Windows 2008 Domain Controllers (ADPREP) »
Feed Icon

Subscribe via RSS or email: