logon script

  • Thread starter Thread starter dst
  • Start date Start date
D

dst

I created a logon script initially for all users and
implemented this. After things slowed down I had time to
creeate a differnet script for different groups>based on
needs. When I put the script in the SYSVOL/domain/scripts
folder, and add the new script name to the users profile
it does not take affect. (ex. original script mapping 10
drives, new script mapping 5 drives.) After putting the
new script name in it continues to map the drives of the
old script. What would cause this and what can I do to
resolve this???
 
dst said:
I created a logon script initially for all users and
implemented this. After things slowed down I had time to
creeate a differnet script for different groups>based on
needs. When I put the script in the SYSVOL/domain/scripts
folder, and add the new script name to the users profile
it does not take affect. (ex. original script mapping 10
drives, new script mapping 5 drives.) After putting the
new script name in it continues to map the drives of the
old script. What would cause this and what can I do to
resolve this???
Click to expand...

Since you "appear" to be on a domain, specify your login scripts through a
GPO link instead of the user profiles. This will prevent issues involving
cached roaming profiles.

There are numerous benefits to defining scripts through a GPO. An OU can
have a GPO link and any group or user placed in the OU inherits the login
script if any. Your domain also has a GPO where a domain wide script may be
assigned. A GPO link can specify user or computer scripts at logon or
logoff. When a user or group changes department, no need to modify profile,
just drop user/group into new OU.

You can also use a script to remove any permanent maps you might have
assigned:

@echo off
IF EXIST W:\NUL NET USE W: /DELETE >NUL
etc...
 
Back
Top