The issue my understanding pop up after XP SP3, to resolve the problem use
the FQDN so instead of \\fileserver\users\username use
\\fileserver.comp.com\users\username in AD you can get the FQDN by right
clicking on the server and go to properties.
HTH,
Bob Smith
--------------------------------------------------
From: "Eisenberg, Wayne" <[email protected]>
Sent: Tuesday, August 11, 2009 5:40 PM
To: "NT System Admin Issues" <[email protected]>
Subject: Home drive mapping quizzler
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/> ~
