How about a GPO to make XP load all GPO's before displaying the desktop (well , sorta)? I have had to utilize that on some XP PC's before. Computer - Admin templates - System - Logon - Always wait for the network at computer startup and logon
Dave From: Joe Tinney [mailto:jtin...@lastar.com] Sent: Tuesday, August 11, 2009 8:13 PM To: NT System Admin Issues Subject: RE: Home drive mapping quizzler We are using the command USE: http://www.scriptlogic.com/Kixtart/htmlhelp/Commands/use.htm Also looks like we delete the connection if it exists (using USE) and then delete the registry key for the remembered connection from HKEY_CURRENT_USER\Network\. From: Eisenberg, Wayne [mailto:wayne.eisenb...@pbvllc.com] Sent: Tuesday, August 11, 2009 10:39 PM To: NT System Admin Issues Subject: RE: Home drive mapping quizzler Michael, We are all XP with a mix of SP2 and SP3 in a Win2003 native domain. It happens in both SPs, as far as I am informed. Joe, what kind of kixtart script command did you use? I have been thinking about converting us over from batch files to kix. Wayne ________________________________ From: Robert Cato [mailto:cato.rob...@gmail.com] Sent: Tuesday, August 11, 2009 6:23 PM To: NT System Admin Issues Subject: Re: Home drive mapping quizzler We're having the exact same issue, so I hope someone out there has some insight. All workstations here are XPSP3 fully patched in a Server 2008 domain. The two users that happen frequently have similar user names (eg TPain and TMPain) although it does happen to others. I have been focusing on other issues so I have not dug through the event logs as it is an easy fix and does not happen all that often...maybe once or twice a week. Other facts: Completely new infrastructure: new switches, all LAN drops tested to CAT5E specs as part of a VoIP roll out, new servers, new racks, new patch cords, new image on the workstations. Thanks, Robert On Tue, Aug 11, 2009 at 5:40 PM, Eisenberg, Wayne <wayne.eisenb...@pbvllc.com<mailto:wayne.eisenb...@pbvllc.com>> wrote: My google-fu is below par right now, maybe some of you have the answer: We use the AD home folder info (on the profile tab) to map users' H: drive to \\fileserver\users\username<file:///\\fileserver\users\username> . 97% of the time it works as advertised. However, sometimes it just maps the H: drive to \\fileserver\users<file:///\\fileserver\users> and doesn't go all the way to the next level. We unmap and remap the user to the proper location manually and life goes on. But why is this happening at all? Is it just a Microsoft-ism? Is there some bizarre glitch running amok? Any ideas? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
