I usually do this mapping within AD myself, but that's not how it was being done prior to my arrival...
Joe Heaton Employment Training Panel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 10:54 AM To: NT System Admin Issues Subject: Re: Bad drive mappings >From the thread, I understand there is a principle here. However, why use "net use..." in a script? OR, does filling in the "Home directory" space in the user's AD Profile tab essentially make a script (which will not run)? I've never had any problems creating the directory " \\server\users\<username>", sharing it as "\\server\<username>$", and connecting that way... -------------------------------------- Richard McClary, Systems Administrator ASPCA Knowledge Management 1717 S Philo Rd, Ste 36, Urbana, IL 61802 217-337-9761 http://www.aspca.org "Eisenberg, Wayne" <[EMAIL PROTECTED]> wrote on 10/29/2008 10:36:28 AM: > 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/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
