CCLCLS
asked on
XP pro client pc is skipping "Applying Computer Settings" and "Applying Security Policy" on boot
I am running a wireless XP Pro, SP3 laptop. I run a 2003 server windows domain. Normally when I start a computer it runs "applying computer settings" then "applying security policy" then "running startup scripts"
This machine goes past the 1st 2 steps really fast (doesn't do it). and then correctly runs the startup scripts portion. I know it is connecting to the network since the startup scripts are run off a network share and then complete successfully. I am then also able to login to the domain. BUT if I make group policy changes on the domain controller, apply them, reboot the laptop, it doesn't apply the changes because it is skipping "applying computer settings" I can't determine why it is skipping that on startup.
This machine goes past the 1st 2 steps really fast (doesn't do it). and then correctly runs the startup scripts portion. I know it is connecting to the network since the startup scripts are run off a network share and then complete successfully. I am then also able to login to the domain. BUT if I make group policy changes on the domain controller, apply them, reboot the laptop, it doesn't apply the changes because it is skipping "applying computer settings" I can't determine why it is skipping that on startup.
ASKER
i'm not having any problems with the scripts. they are computer startup scripts not user scripts. my problem is group policy is not being applied on startup.
Try this, in the Group Policy navigate to Computer Configuration\Administrati
And set to enforce 'Always wait for the network at computer startup and logon'
And set to enforce 'Always wait for the network at computer startup and logon'
ASKER
this is already enabled for all computers
ASKER
seems to only be a problem when using the wireless connection. if i use wired cat5 it applies the GP. but i have specified the slow link detection.
I've had this issue in the past with wireless laptops, and for the life of me can't remember how I fixed it, other than using a wired connection.
It has something to do with the workstation not connecting to the network before logon, so it can't apply the Group Policy, and sometimes it'll even miss the logon scripts.
I wish I could remember how I fixed this. Maybe I didn't though....I could have just had the user's use a wired connection when in the office. Or possibly log off and then back on after their intial logon, to ensure the wireless network was detected and successfully connected.
It has something to do with the workstation not connecting to the network before logon, so it can't apply the Group Policy, and sometimes it'll even miss the logon scripts.
I wish I could remember how I fixed this. Maybe I didn't though....I could have just had the user's use a wired connection when in the office. Or possibly log off and then back on after their intial logon, to ensure the wireless network was detected and successfully connected.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If so, is this script assigned via Group Policy, or stated in the active directory user properties page in the logon script field?