Tom,
That kind of response is best to write and then delete, not send :-)
Remember what you are paying for help from the list...
That being said, I think you can do what you want with a Kixtart script. The
information on manually mapped (as opposed to logon-script mapped) drives is
in the registry under the HKCU\Network key. There are keys under there
corresponding to the letter of each mapped drive. For each mapped drive,
there will be several values. One of these values is called RemotePath and
it is the UNC name of the mapped share.
One idea would be to go through the various drive letters (using IF EXISTKEY
to make sure the letter is mapped) and read the RemotePath value into a
temporary variable with the READVALUE command. You can then parse the
temporary variable, replacing the old server name with the new server name
(using SUBSTR and concatenation). Finally, put the update temporary variable
back into the RemotePath value with the WRITEVALUE command. Repeat through
the possible drive letters.
Note that the user will have to reboot/relogon (or you can do it for them
with the Kixtart SHUTDOWN command) to have the changes take effect.
Hope this helps.
Malcolm Reitz
IT Program Management
KBR Americas Region
-----Original Message-----
From: Tom Grabowski [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 3:20 PM
To: NT System Admin Issues
Subject: RE: Changing Mappings after server re-name
You have all been a great help.
Yes I know what net use * /delete does. And it is exactly what I don't want
to do.
We have users manually mapped because that is the way it thank you for your
thought full insight on logon scripts, hmmm, but I thought that was what my
initial request stated; "Is there a way through 2000 logon scripts or, 3rd
party software, that upon logon the users drive mappings can be reviewed and
through the use of variables accomplish something like this;" and lastly
thank you for the "Just use net use /delete n:" I will go to each
workstation find out their mapped drives to the old server and create
individual logon scripts for each different development group or department.
Trying to eliminate the sneaker net through "Logon Scripts" Thanks anyway
for the assists. If I find a way to do what I want I will post it, maybe
what we have here is a failure to communicate.
-----Original Message-----
From: Tom Grabowski [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 9:59 AM
To: NT System Admin Issues
Subject: Changing Mappings after server re-name
Does anyone know if it is possible to re-map existing drives through a log
on script after changing a server name? This is the situation we have; We
are 'upgrading', format, install fresh, and restore information, one of our
servers from NT4 to 2000 and in the process we are renaming the server from
APPS_SERVER to APPS2, to keep in line with Internet DNS naming standards. I
know that there will be numerous people with mapped drives to this server
such as "Prog on 'Apps_Server' (P:)". Is there a way through 2000 logon
scripts or, 3rd party software, that upon logon the users drive mappings can
be reviewed and through the use of variables accomplish something like this;
if %drive_leter% = 'Apps_Server' then net delete 'Apps_Server' and Net Use
'Apps2', to whatever drive letter the directory was originally mapped. We
need to use a variable for the drive letter because there are numerous
shared directories that are mapped to numerous different Drive Letters, most
done manually by department or individual developers.
Thanks in advance for any help.
Tom Grabowski
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
