The way I've seen it deployed is that you use KIXTART. here is an example of
something you might do. You would create a group "somentgroup" and assign
the people who should map this drive letter.
if ingroup ("someNTgroup")
? " Mapping Data Drive J:"
use j: /d
use j: \\server\sharename
if @error=0
? "Map successful."
else
? "Map failed."
endif
endif
you just have to keep mapping the drives as needed and they are all kept
centralized. the script runs when the user logs in. Its easy to add / change
/ delete because all you have to do is assign people to that group and they
will map the printer. If you dont want them to map it, just take them out of
the group. There are many options.
There are many good ideas in ASB's site
http://www.ultratech-llc.com/KB/Scripts/ take a look over there and look @
the great ideas.
hope this helps.
Will
-----Original Message-----
From: Tom Grabowski [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 4: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
**********************************************************************
"This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
e-mail originator.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses. However, please check
this e-mail for virus infection for which CDG Management LLC accepts no
responsibility"
**********************************************************************
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
**********************************************************************
"This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
e-mail originator.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses. However,
please check this e-mail for virus infection for which
CDG Management LLC accepts no responsibility"
**********************************************************************
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
**********************************************************************
"This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the e-mail originator.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses. However,
please check this e-mail for virus infection for which
CDG Management LLC accepts no responsibility"
**********************************************************************
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
