Redirect mapped drives
I would like to know if anyone knows of a login batch file that could be used to redirect users mapped drives. I currently have 500+ users that have various mapped drives on each of their PC's to 3 different file servers. I would like to redirect these mapped drives to a new single file server (with all network shares). Basically, the shares are being moved to a new file server.
Software/Hardware used:
Software/Hardware used:
ASKED:
March 26, 2008 12:37 PM
UPDATED:
April 10, 2008 6:17 PM
Answer Wiki:
this may sound silly but
net use <drive letter :> /d --- to delete the drive letter
then
net use <drive letter :> \<server>share
am I missing something ?
Cheers
Daryl
<a href="http://www.myithelpdesk.com/it-support.htm">www.myithelpdesk.com </a>
, <a href="http://www.mailprotector.com.au">www.mailprotector.com.au</a>
*****************
I deployed a new file server for about 100 uses, but only had 10 scripts to edit, so it was easier.
If you have a lot of scripts to edit, it could be a daunting task. You could edit scripts and add the following line to the start of each:
if exist * net use * /d /y
You could try creating a GPO that would run this in a script of it's own for all users or specific OUs for a period of time. The VBscript to delete mappings is similar to this:
Dim wshNetwork
Set wshNetwork = CreateObject("Wscript.Network")
Set colDrives = wshNetwork.EnumNetworkDrives
Set ADSysInfo = CreateObject("ADSystemInfo")
Set CurrentUser = GetObject("LDAP://" & ADSysInfo.UserName)
Const OUNAME = "ou=OUNAME_HERE"
For i = 0 to colDrives.Count-1 Step 2
wshNetwork.RemoveNetworkDrive colDrives.Item(i)
Next
good luck
*********************
To see all answers submitted to the Answer Wiki: View Answer History.
If they all share the same common mapped drives as mentions using net use with the same drives should overwrite the previous mapping when ran.
It’s true you can change and force changes to drive mapping in login scripts, but you may run into other issues that could generate a lot of support calls. In particular people may have desktop shortcuts and even shortcuts in other folders that reference the old server names.
What I did when combining two old servers into a new one was to combine all the existing shares/folders and use DNS aliases to that old references would still work. This involves a registry mod to windows servers as they don’t normally listen to the aliases for netbios requests. It’s in the “strict name checking” reg.
see this link
http://www.sharepointblogs.com/echef/archive/2007/08/08/allowing-netbios-responses-on-a-dns-alias-in-win-2k3.aspx
This moves the issue of old shortcuts off the front burner.