Make sure they're not picking up the higher level mapping from another login script. I had that issue a while back.
Joe Heaton Employment Training Panel From: Phil Hershey [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 8:59 AM To: NT System Admin Issues Subject: RE: Bad drive mappings Or 'net use h: %homeshare%' - Philip This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. From: Steve Moffat [mailto:[EMAIL PROTECTED] On Behalf Of NTSysAdmin Sent: Wednesday, October 29, 2008 8:47 AM To: NT System Admin Issues Subject: RE: Bad drive mappings It should be \\server\users\%username%, From: Eisenberg, Wayne [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 12:36 PM To: NT System Admin Issues Subject: Bad drive mappings Has anyone seen this issue? Users log in, and the login script says 'net use h: /home' which should send them to \\server\users\<username>, per their AD attribute. However, what happens is that they map to \\server\users instead. It will also happen if you drop to a command prompt and type the same net use line there. You can always manually map to the deeper UNC without issue (so it's not an NTFS ACL issue). It seems to happen more frequently to laptop users than desktop users. Thanks, Wayne ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
