I appreciate the ideas...I've been there already. The deal is our users have scripts and processes that are tied to the drive-letter on their workstation. It's one of those things where everyone has developed something that worked and now it is something that is relied upon and important.

I am restricted to a few rules in this situation:

1) Move NFS shares to a new server
2) Consolidate them on the new server
3) Users mappings must retain the same drive letter so their 'stuff' still works.
4) Complicating things...there isn't a driveletter that I can commandeer for NFS due to the possibility of overwriting a critical mapping of some user.

If you can't tell...our users get a lot of weight in the decisions MIS makes! I can obviously go to each PC an re-map manually (please NO!). I might be able to come up with a batch script to send out to each user but due to #4 above, I'd have to find a way to have the user type in the letter of their current NFS mappings and make that input a variable (don't know how to do this). Last, I can use a scripting language that is OS agnostic like KiXtart or Perl since this has to take place on Win95, WinNT, and up. I have used KiXtart and prefer it, obviously.

Now then...my problem remains:

  • Enumerate mapped drives
  • See if any specific mappings exist
  • If so, record the drive letter as a variable
  • Use the Variable to delete the mapping and re-map.
Without WSH and WMI, I'm stuck with just KiXtart's abilities. Anyone got anymore helpful ideas based on these rules and what I have to work with? Renew my faith in this powerful product!