New laptop not getting logon script

[somedea]

We just bought 4 new laptops, all imaged the same way. 3 are working fine; one doesn't get the logon script. Checked the user, he gets logon script at another computer, just not at the new one.
Group memberships look correct, same as other computers. Any ideas as to why the logon script (located in dc\netlogon share) isn't running on this one computer?

 

[acl03]

Have you tried having another user log into that laptop and see if they get the script to run?

Thanks,
Andrew

Hard work often pays off over time, but procrastination pays off right now!

 

[somedea]

Yes, no logon script

 

[acl03]

Do other policy items in the same GPO as the logon script get applied?

Thanks,
Andrew

Hard work often pays off over time, but procrastination pays off right now!

 

[somedea]

It's a separate Group policy for the logon script, so there are no other items

 

[acl03]

Try running gpresult from the laptop in question, this should tell you if the GPO is applying.

Are you sure the logon script is not running? Perhaps it is running, but its functions are failing on that laptop? 89Why not add a MsgBox to the script temporarily, this should tell you whether or not the script is running for sure.

If the GPO is being applied and the script is not, it could be due to the "feature" of Windows XP (I assume you are using XP) doing "fast logons", or whatever it is called. It logs you on with cached credntials to get the desktop up fast, then brings down all GPO items (except logon scripts) when the network is ready.

To test for this, disable the "fast logon" feature by enabling this Group Policy item:

Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon

Thanks,
Andrew

Hard work often pays off over time, but procrastination pays off right now!

 

[acl03]

Here is the first part of the explain text for that policy I mentioned:

Determines whether Windows XP waits for the network during computer startup and user logon. By default, Windows XP does not wait for the network to be fully initialized at startup and logon. Existing users are logged on using cached credentials, which results in shorter logon times. Group Policy is applied in the background once the network becomes available.

Thanks,
Andrew

Hard work often pays off over time, but procrastination pays off right now!

 

[acl03]

The problem is, logon scripts cannot be applied in the background, they can only be applied at...well....logon.

Thanks,
Andrew

Hard work often pays off over time, but procrastination pays off right now!

 

[somedea]

Andrew,
Thanks for all your suggestions. The script runs visibly on all machines. It maps some network drives and I use it for a few other purposes from time to time.
We don't see the script run, and the network drives are not mapped......that's how I discovered the problem.
I had done a gpresult before, saw no errors, but now I'm seeing that the logon script policy has not been run, shown with this explanation:
User - Logon Script Policy
Filtering: Not Applied (Unknown reason)

any ideas on where to look for why it's not been applied?

 

[acl03]

Hmmm...try removing the machine from the domain and re-joining.

Is the computer in the same OU as the ones that do get the policy?

Thanks,
Andrew

Hard work often pays off over time, but procrastination pays off right now!