GPO (computer policy) not working after reboot.

Dear Sir,

I had created some Group policy (Computer Policy) for Windows 7. Is that suppose the computer policy will deployed once the workstations are restarted. I had found that some workstations not apply the new computer policy until I manually type gpupdate /force in command prompt and then restart once again.

Please advise and correct me if I am wrong. Thank you.

With regards,
Wataw
WatawAsked:
Who is Participating?
 
Hello ThereConnect With a Mentor System AdministratorCommented:
To apply your GPO:
GPO Computer Configuration
- wait up to 120 mins
OR gpupdate/force + reboot
OR just reboot

GPO User configuration
- wait up to 120 mins
OR gpupdate/force + log off and log in
OR log off and log in at least twice
0
 
Olgierd UngehojerConnect With a Mentor Senior Network AdministratorCommented:
When computer is running GP is update every 90 minutes with random offset  0- 30 min. Group Policy for the computer is always updated when the system starts.
0
 
WatawAuthor Commented:
Dear Olegierd,

Thanks for your reply. Our network had around 150 workstations, but only 10 of them new group policy (computer policy that install SSL cert) need to do it in front of the computer. Before reboot, I type gpresult /R . I see the GPO is applied on the list.  Then I reboot but no luck. Type gpupdate /force and then reboot. Then it works. Please advise what's happening?

Thank you.

With regards,
Wataw
0
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

 
Ashok DewanFreelancerCommented:
Reboot works only for local group policies

For domain:-
But if you have set new group policies for a PC then you have to run gpupdate /force on doman controller and then restart remote systems which are in domain OR wait for 120 mins as mentioned above.
When you make a change to a group policy, you may need to wait two hours (90 minutes plus a 30 minute offset) before you see any changes on the client computers. Even then, some changes will not take effect until after a reboot of the computer.
0
 
Ashvin AshokConnect With a Mentor Team Manager - ITCommented:
Check the DNS from the client machine. There are possibilities for the workstation to have DNS issue which can cause GP replication issues.

Try entering the DNS address manually in the client workstation and try rebooting the client machine. Hopefully the computer configuration policies should be applied.

After reboot, save a RSOP report and verify the same.
0
 
Hello ThereSystem AdministratorCommented:
Make sure that GPO is linked to the correct OU and an OU contains all objects + that GPO is not enforced, no Block inheritance is set or no security filtering or WMI filtering is applied.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.