Computer GPO not being applied to computers

I am having problems applying computer based GPO's to computers in my domain. I want to set the setting on all computers when they boot up to wait for network connections before allowing user to log on. I have done it through a reg key which works fine, but through the GPO I have set this, along with slow link detection, and allow the different GPO's to run over slow link if detected.

I am looking for suggestions on how to get my gpo to apply to my computers at their each startup.  I have my GPO listed under my top level domain not on an OU, I also have the filtering set to authenticated users/& Domain Computers.

Any suggestions would be great.


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You can try adding the startup script with the following command.

gpupdate /force

This will force to apply the GPO every time the computer reboot.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HRSBTechAuthor Commented:
I have run gpudate /force 100 times and no luck at all, I can put this in my computer logon scrip?

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Logon script only run when a user log on to a computer you have to add the script in the startup script in the "Computer Configuration ->Windows Settings -Scripts - Startup"
HRSBTechAuthor Commented:
I just created a script in the startup called update.bat this is what it looks like.
gpudate /force

Open in new window

Add this script to the startup script of GPO and link the GPO where computers located. check the result using rsop.msc
HRSBTechAuthor Commented:
I did this and the update.bat file is listed in the rsop.msc startup scrip. When I turn on the computers it should say waiting for network connections, and will force process all GPO's even if network is not completed setting up, it will wait and finisht he GPO's until they are done. All my settings are listed in the rsop.msc

We use deepfreeze here meaning when I restart the computer it goes back to the previous setup I have created for that computer, you can change whatever and restart it's back to normal. I have made many gpo's in the past that have worked this one doens't seemto be working.

Is there a way that I can run a reg key when the computer turns on. I have the registry settings I need for this to work as well.

How many GPO's are assigned to the OU you are implementing this policy on.  Is there a chance that there is another policy with priority that has conflicting settings?
bluntTonyHead of ICTCommented:
SO you have some software which reverts your PC back to it's original config before the GPO was applied? I think that's your problem.

Your trying to set a policy to force the machine to wait for the network and apply all policies, but on your first reboot that setting isn't applied, meaning that it isn't applying all policies on this reboot. Unfortunately, the setting you are actually trying to apply is one of those settings that cannot immediately refreshed in the background.

(I assume you mean : Computer Config | Admin Templates | System | Logon | "Always wait for the network at computer startup and logon")

For this setting to take it hold it can actually take a couple of reboots, because this setting could being applied in the background, and applied on the next refresh. The problem is that you're reverting the machine back to it's original config when you next reboot putting you back to square one (I hope that makes sense!)

This is also why I think GPUPDATE isn't working - because the policy can't be applied during a user session and has to wait for the next reboot (which effectively never happens).

If what I'm saying is correct, I'm afraid there is not a lot you can do about this. You could write a startup script to set the relevant reg key, but I don't think even this would necessarily force all GPOs to apply on that same startup cycle.

You can use vbscript to write a reg value write easily (

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.