Edit Group Policy to allow XP to wait for network initialization:
Navigate to Computer Configuration / Administrative Templates / System / Logon
Double-click "Always wait for the network at computer startup and logon" and enable this policy.
Ref:
http://msdn.microsoft.com/library/d...ry/en-us/policy/policy/logon_optimization.asp
To speed the startup and logon process, Windows XP Professional does not require that the network be fully initialized before a client computer can start up or before a user can log on. If a user has previously logged on to a particular client computer, he or she is subsequently logged on using credentials cached on that computer.
When a user switches from using a local profile to using a roaming profile, Windows XP Professional copies relevant portions of the user's registry from the server instead of from the local computer, to prevent an older local copy from overwriting the server copy. Thereafter, whenever the roaming user logs on, the computer always waits for the network, so the profile can be downloaded from the server.
When fast network logon is enabled (as it is by default in Windows XP Professional), if administrators remove the profile path from a user's object, it is recommended that they also either rename or delete the corresponding profile folder. If they do not, and an administrator later reenters the same path, the user will receive the older copy of the registry from the server.
Ref:
http://www.microsoft.com/mspress/books/sampchap/5566e.asp
--
Nicholas
----------------------------------------------------------------------
| Hi All,
|
| Just replaced an aging NT4 server with a brand spanking
| new Win 2003 Server (Thank you Michael Dell...)
|
| The problem is this:
| The old NT Workstation machines on the LAN log into the
| new server without a hitch, but new WinXP Professional
| machines hang for about 5-10 minutes with a "loading
| personal profile" window on the screen.
|
| Any idea of what is going on?
|
|
| TIA
|
| --MAB
