not running login script

[Tim]

I am getting reports that my login script is not
consistantly running everytime a user logs in. I have set
the group policy to run before allowing use of the
desktop and the problem still occurs.

My script maps drives & various printers. Active Dir is
responsible for the "z:" home drive setup in the
properties of the user and sometimes even that does not
appear for the user.

Any Ideas? Maybe it is a Group Policy thing?
Cheers!

 

[Herb Martin]

I am getting reports that my login script is not
consistantly running everytime a user logs in. I have set
the group policy to run before allowing use of the
desktop and the problem still occurs.

My script maps drives & various printers. Active Dir is
responsible for the "z:" home drive setup in the
properties of the user and sometimes even that does not
appear for the user.

Most likely a replication thing.

Assuming you are using GPOs to assign the Logon scripts to
Win2000, XP, or Win2003 machines....

DCDiag each DC and determine if this gives any WARNING,
ERROR, or FAIL messages (send output to a file.)

If you have SysVol failing to replicate (the scripts) to all DCs
there is (part of) your problem.

Also double check: Are these clients using a pre-Win2000 OS,
since those don't get GPOs but must use the older user property
logon scripts.

If you still have BDCs operating in the domain they do NOT
automatically replicate SCRIPTS -- you must set up a "file
replication bridge" (fancy name for a batch file) and make
sure they all get the scripts (something like NT replication
service.)

Oh, and how do you know the scripts aren't running? You
might want to right the scripts to log (at least 'start' and 'finish')
to a central location.

 

[Tim]

I have 3 DCs able to run the script replicated in the
sysvol directory. In the script i have echo'd some
variables (username, computername, logonserver etc..) to
log an entry to a logfile. However this log file is only
on one of the dc's not in the sysvol. I have just added a
line to the end of the batch so i can see that is starts
and runs the whole batch file in the log entry. This
should narrow down whether it is a GP problem or it is
just not running the whole script.

Will this work or should i have this logfile in the
sysvol directory also?

 

[Herb Martin]

I have 3 DCs able to run the script replicated in the
sysvol directory. In the script i have echo'd some
variables (username, computername, logonserver etc..) to
log an entry to a logfile. However this log file is only
on one of the dc's not in the sysvol. I have just added a
line to the end of the batch so i can see that is starts
and runs the whole batch file in the log entry. This
should narrow down whether it is a GP problem or it is
just not running the whole script.

Will this work or should i have this logfile in the
sysvol directory also?

If it isn't in the SysVol directories it will NOT get replicated
(unless you arrange that personally/manually.)

The easiest way to get it in the "right' place is to create the
script through the GPO Editor tool -- even if you have to
take the current script and paste it into the "new one."