find mapped drives on workstations

Hello,

I've setup a new 2003 server to replace an old NT4 server. I found that all the users are mapping to different shares on the server. I would like to find a batch file that will determine what shares, drive letters are mapped on each workstation and delete those drives and remapp them to the new server.


The obvious answer is use net use to delete the old drives and remap the new ones. Since everyone has different shares mapped a standard batch file can't be used. I need something that will determine the mapp to the old server and replace it with the new.

any help would be appreciated.

Thanks

 

How many workstations and how many of you to do the work?

I'm thinking that even though it will be painful, your best option might be to delete all the current mappings and assign standardized ones via a logon script. Lots of setup time on the front end but over the long haul, much easier to administer.

 

A script is what I'm looking for. There are 3 servers and about 90 users. and guess what there is only me to remapp all the drives

The profiles on the pdc map them to z home drive so I can put a login script there.

but
Mary will have a map to y: on server finsrv1 to data$
And also w: finsrv1 to payroll$

John will have a map to y: on engsrv1 to data$
and also w: finsrv1 to payroll$

The new servers name will be finsrv2 and engsrv2 ...etc with the same shares.

I know I can net use */delete to kill the existing maps and remap with net use w: finsvr2.

But since these guys all have different shares drives mapped I can't use a standard batch for engineers and finanace. If it were only that simple.

What i need is a a way to enumerate the maps on each workstation and replace the old server name with the new. And remap the drives.

thanks

 

The easiest fix I can think of won't require messing with the maps on the user's PC at all.

You now have ServerA1 and will be replacing that with ServerA2 so that ServerA1 will no longer exist. If you put in a DNS entry to create an Alias so that any call to ServerA1 will be redirected (silently, quickly) to ServerA2 then the current drive mappings will continue to work. \\ServerA1\share$ will simply open \\ServerA2\Share$

DNS How To.

 

If you are using WINS (perhaps you have Win98 or NT4 workstations) you will also need to create a WINS mapping too (dummy server name to IP address).

I have to say - I agree with Newt's first comment. Your best option is to bite the bullet and unify your mappings. If you preserve this mess it will only get more complicated next time you need to make a change.

However, as we all do the "wrong" option fairly regularly , I'd recommend that you look at using a VBScript rather than a batch file if you can't rationalise now. The VBScipt will give you a lot more flexibility with rules along the lines of "if the mapping is like this, change it to this ". Also use the user profile to distribute the batch file rather than the Z: drive. That way you may be able to create a single central script to do what you want. Don't forget to document the script. You need to be able to manage it in a year's time!!!!