We had an issue that was close to that about 2 years ago. It turned out to be new machines that had CPUs with H/T or dual cores. We ended up changing the GPO to have the setting "Always wait for the network at computer startup and logon. We have not seen the problem since.
The problem was also very random for us and very hard to duplicate in a lab but happened must often on a fresh reboot with a quick logon. Robert Hart GENEX Services, Inc Client System Engineer From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2008 11:06 AM To: NT System Admin Issues Subject: Strange login issues Server 2K3 Windows XP SP3 We just replaced 60 user PCs. We have GPOs that map needed drives for the users. One of the login scripts maps the user to their home directory, which looks like the following: Net use F: /d Net use F: \\server\%username% /Persistent:yes The issues we're getting are the following: 1) Randomly the F: drive will not be mapped at all. 2) Randomly the F: drive will be mapped to \\server\Users, instead of the person's personal folder. I mention the rollout of new PCs, because this behavior wasn't happening beforehand. My personal preference for mapping personal drives is to do it within ADUC, under the Profile tab, but that's not how it was when I got here, and I'm still trying to plan switching it over without disrupting users. There are no other login scripts that map the F: drive, so there's no conflict there. Sometimes having the person log out and back into the network fixes it, sometimes it doesn't. Also, when I mention random, I mean it. Random users, random times, random symptom between the above two. Any help on where I can look to figure out why this is happening would be great. Thanks, Joe Heaton AISA Employment Training Panel 1100 J Street, 4th Floor Sacramento, CA 95814 (916) 327-5276 [EMAIL PROTECTED] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
