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/ ~
RE: Bad drive mappings
Well, yes, in the template it is as you say. When you create the user, it becomes \\server\users\weisenberg, or whatever the actual username is. From: Steve Moffat [mailto:[EMAIL PROTECTED] On Behalf Of NTSysAdmin Sent: Wednesday, October 29, 2008 11: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/ ~
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/ ~
RE: Bad drive mappings
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/ ~
RE: Bad drive mappings
Nope. Only one script that runs. Like I said, I can remove any h: drive mapping, run 'net use h: /home' from a command prompt and get the same wrong result - no deep mapping. From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 12:02 PM To: NT System Admin Issues Subject: RE: Bad drive mappings 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/ ~
Re: Bad drive mappings
Proper permissions on the folders? The users can access their folder and nobody elses? On Wed, Oct 29, 2008 at 11:52 AM, Eisenberg, Wayne [EMAIL PROTECTED] wrote: Nope. Only one script that runs. Like I said, I can remove any h: drive mapping, run 'net use h: /home' from a command prompt and get the same wrong result - no deep mapping. -- *From:* Joe Heaton [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, October 29, 2008 12:02 PM *To:* NT System Admin Issues *Subject:* RE: Bad drive mappings 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/ ~
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/ ~
RE: Bad drive mappings
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/ ~
RE: Bad drive mappings
Yep From: Steve Ens [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 1:30 PM To: NT System Admin Issues Subject: Re: Bad drive mappings Proper permissions on the folders? The users can access their folder and nobody elses? On Wed, Oct 29, 2008 at 11:52 AM, Eisenberg, Wayne [EMAIL PROTECTED] wrote: Nope. Only one script that runs. Like I said, I can remove any h: drive mapping, run 'net use h: /home' from a command prompt and get the same wrong result - no deep mapping. From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 12:02 PM To: NT System Admin Issues Subject: RE: Bad drive mappings 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/ ~
