Logon script won't always run

[Chris]

My logon script is run from a GPO. On some computers it will not run.
On those computers where it won't run, it won't run for any user at
all (but it will work for those same users on other machines). If I
take that computer out of the domain and delete the computer account
in AD, then rejoin the domain, it will usually work (I say usually
because sometimes I have to repeat the delete and rejoin).

Once the logon script works for a computer, it always works. However,
if I rename the computer it might not work (or it might).

Some brand new computer accounts added to the domain don't work.

Does anyone have any idea what is going here? Any tips on things to
check?

Thanks,
Chris

 

[Cary Shultz [MVP]]

-----Original Message-----
My logon script is run from a GPO. On some computers it will not run.
On those computers where it won't run, it won't run for any user at
all (but it will work for those same users on other machines). If I
take that computer out of the domain and delete the computer account
in AD, then rejoin the domain, it will usually work (I say usually
because sometimes I have to repeat the delete and rejoin).

Once the logon script works for a computer, it always works. However,
if I rename the computer it might not work (or it might).

Some brand new computer accounts added to the domain don't work.

Does anyone have any idea what is going here? Any tips on things to
check?

Thanks,
Chris
.

Chris,

I would first take a look at DNS. Make sure that the
computer accounts ( assuming, naturally, that you are
talking about all WIN2000/WINXP Pro systems - which would
have to be the case if you are using a GPO logon script )
are showing up in the FLZ on your DNS Server ( and it
might not be a bad idea to create a RLZ - where all of
the computers would have a PTR record ).

Have you run any of the GPO troubleshooting tools ( like
GPOTool and/or GPRESULTS )? This might be a good second
step.

One of our clients had a wierd problem with the logon
script ( first a .bat, then a .cmd and finally a .vbs via
GPO ) would sometimes not work. Simply logging off and
then back on usually fixed the trick. In this case it
was a case of a bad switch. We came to realize this by a
bunch of Network Errors in the output logs when we
enabled logging.

Also, since I am here - have you properly set up AD Sites
and Services where you create the subnet and associate it
with a Site for each and every one of your existing
subnets? Secondly, I would suggest that you install the
Support Tools on all of your WIN2000 Servers. The
Support Tools are located in two places: on the WIN2000
Server CD ( in the Support \ Tools folder ) and on the
WIN2000 Service Pack CD ( in the Support \ Tools
folder ). I would suggest installing from the Service
Pack CD if possible.

HTH,

Cary