|
jlai -> slow login for OSD images (WinXP Sp2 and SP3) (5/9/2008 3:35:08 AM)
|
We have noticed that our SOE computers (WinXP SP2 and SP3) that have been built via OSD have a considerable longer login time than our SOE computers that were built via RIS with automated installation scripts. The slow login only occurs after a cold boot or a reboot - no such delays from a log off and log on and the system runs fine when logged in. We have a range of Dell desktop & notebook models, but the issue is not model specific. It occurs on all OSD computers [:@]
On a non-OSD computer, the user enters their credentials, Loading your personal settings../ Applying your personal settigns... occurs, XP toolbar appears, user login script starts running, desktop wall paper and shortcuts appear, and the script completes a few seconds later. Maximum time to login is about 15 to 20 seconds from entering credentials to a ready desktop.
On a OSD computer, the delay seems to occur when the Loading your personal settings... / Applying your personal settings... phase and also the desktop wallpaper & shortcuts don't appear until some time after the user logon script completes. Minimum time to login is over a minute from entering credentials to a ready desktop.
- OSD reference computer created on a Virtual Server 2005 virtual computer
- OSD reference computer contains Windows Installer, Windows Update Agent, SMS Adv Client (no site code set), scanwrapper.exe /extended /cache is executed and any missing Windows updates are also applied.
Things I have checked or tried...
- Deploying an OS only OSD package.
- No GPOs applied to computer or user
- Disabling roaming profiles
- Logging on with local admin account
- DNS, IP settings are obtained from DHCP
- Confirmed correct NIC drivers
- Checked event logs for errors
- Ran Autoruns.exe to compare the difference in startup apps/services/dlls in both build types
I am at the point of recapturing the WIM with just the OS (no WI, no WUAgent, no SMS Agent etc), but just wanted to see if anyone had experienced and resolved a similar issue before I go through the tedious task of recapturing the WIM.
Any help would be most appreciative.
Cheers,
Jerry
|
|
|
|
