Drive Mapping Script Problems with XP SP2 Clients

[Paul Christopher]

Hi,

this is probably an XP issue but I'm hoping a Windows 2000/2003 Admin may
have seen the same problem.

Scenario:

Forced drive mapping for users via login script, always delete any existing
mapping and re-do to allow moving shares around servers transparently to
users. We need to redirect existing mappings to new servers.

Problem:

S: is mapped on client to \\old_server_share.
The description of the map, e.g. share$ on server (S does not update
though the script runs without errors though the link does point to the
correct share.

Method:

VBS login script

MyNetwork.RemoveNetworkDrive "S:", True
MyNetwork.MapNetworkDRive "S:", \\new_server\share_name

OR Call cmd script

net use s: /delete /Y
net use s: \\new_server\share_name

Same if cmd script is run manually.
If the net use commands are entered manually via command line the display in
My Computer updates as expected so this looks like a timing issue.

Anyone else seen this?

TIA

Paul Christopher

 

[Jerold Schulman]

I haven't.
Could be a new bug with hidden (Share$) shares.

I would do 2 things.

net use s: \\new_server\share_name /Persistent:NO

Implement tip 8885 in the 'Tips & Tricks' at http://www.jsiinc.com

Hi,

this is probably an XP issue but I'm hoping a Windows 2000/2003 Admin may
have seen the same problem.

Scenario:

Forced drive mapping for users via login script, always delete any existing
mapping and re-do to allow moving shares around servers transparently to
users. We need to redirect existing mappings to new servers.

Problem:

S: is mapped on client to \\old_server_share.
The description of the map, e.g. share$ on server (S does not update
though the script runs without errors though the link does point to the
correct share.

Method:

VBS login script

MyNetwork.RemoveNetworkDrive "S:", True
MyNetwork.MapNetworkDRive "S:", \\new_server\share_name

OR Call cmd script

net use s: /delete /Y
net use s: \\new_server\share_name

Same if cmd script is run manually.
If the net use commands are entered manually via command line the display in
My Computer updates as expected so this looks like a timing issue.

Anyone else seen this?

TIA

Paul Christopher

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com