Note: This is really important to understand that when roaming profiles are implemented, group policy software installations and folder redirection requires that the user is NOT logged on before the network is initialized and processes policy synchronously- ONE AT A TIME . This is the default behavior and changing it could cause inconsistencies with your logon.
Note: If home folders are needed with roaming profiles there is a registry key tweak (SafeDllSearchMode) that can be added that will change the behavior. If you’re not sure that this is an issue in your environment, take a network trace at logon and see if DLL’s are being queried across the network to the home folder. There is also another tweak on the same page (StartRunNoHOMEPATH) that will assist with applications doing this behavior.
Before we get into troubleshooting a slow login we need to first identify
what is a slow login
. To be able to say a logon or boot up is slow you must know what a normal logon or boot time looks like in
environment. With the above expectations the next step is to document the time a logon takes under normal conditions and under load (morning and afternoon rush hours). This should be done with all the different operating system builds in your environment (desktops, laptops, servers, XP, Vista, Win 7, 2003, 2008, 2008 R2) to have a standard baseline to work with.
Here is a short starter list of things to include in your baseline documentation:
- Bob “My idea of a short hiatus is 18 months” Drake
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.