Login Script Does not Map

[BillB]

Hi,
Currently our drives are mapped to a NAS via login script
in Active Directory. Simply
Net Use: N: \\Nas\...
etc

We have a new NAS, call it NASNEW, that we need to point
our users to (same share structure). The problem is that
when the user logins in, the script using
Net Use N: \\NASNew\...
does not map to the NASNEW; it maps to the old NAS, as if
the mappings are persistent on the workstation.

I've tried adding a Net Use N: /D in the script to clear
the connections but that doens't help.

The only workaround has been, to disconnect the mappings
on the PC, so there are none, then relogin. The new
mappings then execute properly.

Thanks,
Bill

 

[Jack]

Is the login script in the NETLOGON folder on every domain
controller, and if so are they identical (reflecting the
new NAS)?

 

[Guest]

In this test, we used the original script, wishing to test
the actual cut-over process. All we did was edit the
original script to reflect the new NAS name.

The script works if one manual disconnects the mapping on
at a desktop.

 

[Oguzhan Kayhan]

HI,
If you use vbs script for it..
I found a script on the net a while ago.
You can edit it for your settings..
It removes the drive first then adds the new one..
-----------------------------------------------------------------------
' VBScript.

Dim WshNetwork, oNet2 ,

on error resume next

'script to remove U:


Set WshNetwork = WScript.CreateObject("WScript.Network")
WshNetwork.RemoveNetworkDrive "U:"

'script to add drive U:

Set oNet2 = CreateObject("Wscript.Network")
oNet2.MapNetworkDrive "u:", "\\192.168.10.4\test2"

 

[Lanwench [MVP - Exchange]]

In your login script (presuming you don't have any 9x clients), try:

net use * /del

net use n: \\nas\sharename /persistent:no