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 < [email protected]> 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 . 97% of the time it works as > advertised. However, sometimes it just maps the H: drive to > \\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/> ~
