Avatar of deshaw
deshawFlag for India asked on

Does a Group Policy change need reboot for sure

Hi,

I just modified below policy and it doesn't get into effect until we reboot the machine. Does this mean that any changes to Computer Configuration needs a reboot? or is there a doc which clearly indicates which policy change needs reboot and which doesn't.

Computer configuration -> Windows Settings -> Local Policies -> User Rights Assignments -> Log on as a service

We do have "Computer Configuration -> Admin tools -> System -> Logon -> Always wait for the network at computer startup and logon" enabled.

Thanks
Operating Systems

Avatar of undefined
Last Comment
alexmclv

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
alexmclv

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
deshaw

Hi,

When i run gpupdate /force, it prompts for reboot and logoff and if i say no then it won't apply the policy that i mentioned in my initial post.

Thanks
alexmclv

deshaw,
You are required to reboot because "gpupdate /force" will attempt to refresh all the Group Policy settings (whether you have changed them or not). If you leave the "force" switch out and run "gpupdate" by itself, then the policy will simply refresh the settings you changed; it shouldn't ask you to restart.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23