Bobcares

Updating Group Policy Settings on Windows Domain Computers

by | May 23, 2021

Updating Group Policy Settings on Windows Domain Computers is a good practice.

As part of our Server Management Services, we assist our customers with several GPO queries.

Today, let us see how to update Group Policy (GPO) settings on Windows computers in an Active Directory domain.

 

Updating Group Policy Settings on Windows Domain Computers

Moving ahead, let us have a look at how our Support Techs update Group Policy settings.

Change Group Policy Refresh Interval

Before we apply the new settings in a local or domain Group Policy (GPO)  to Windows clients, the Group Policy Client service must read the policies and make changes to the Windows settings. This process is a Group Policy Update.

GPO settings update when the computer boots and the user logs on. It refreshes automatically in the background every 90 minutes + a random time offset of 0–30 minutes.

We can change the GPO update interval via Computer Configuration -> Administrative Templates -> System -> Group Policy section of the GPO.

Then we enable the policy and set the time (in minutes) for the following options:

  • This setting allows you to customize how often Group Policy is applied to computers (0 to 44640 minutes). If we set 0 here, the policies will update every 7 seconds;
  • This is a random time added to the refresh interval to prevent all clients from requesting Group Policy at the same time (0 to 1440 minutes).

 

GPUpdate.exe Command to Force Refresh GPO Settings

Almost all administrators use the gpupdate /force command to update Group Policy settings on a computer.

The command forces the computer to read all GPOs from the domain controller and reapply all settings. Hence, when we use the force key, the client connects to the domain controller to retrieve the files for ALL policies targeting it.

A simple gpudate command without any parameters only applies new and changed GPO settings.

A successful update will show a message like this:

Updating policy...
Computer Policy update has completed successfully.
User Policy update has completed successfully.

We can update only the user’s GPO settings:

gpupdate /target:user

Or only the computer’s policy settings:

gpupdate /target:computer /force

However, if we cannot update some policies in the background, gpupdate can log off the current user:

gpupdate /target:user /logoff

Or restart a computer:

gpupdate /Boot

 

A Remote GPO Update from the Group Policy Management Console (GPMC)

In Windows Server 2012 and newer, we can update Group Policy settings on domain computers remotely using the GPMC.msc.

Then after any alter in settings, or creating and linking a new GPO, we need to right-click the Organizational Unit (OU) we want in the GPMC and select Group Policy Update in the context menu.

In a new window, we can see the number of computers with GPO. Confirm the force update of the policies by clicking Yes.

Then the GPO will remotely update on each computer in the OU one by one. Hence, we will get the result with the group policy update status on the computers.

This feature creates a task in the Task Scheduler with the GPUpdate.exe /force command for each logged-on user on the remote computer.

We see the message, ‘The remote procedure call was canceled. Error Code 8007071a’ if the computer is turned off or a firewall blocks access to it.

 

Invoke-GPUpdate: Force Remote Group Policy Update via PowerShell

In addition, we can call the remote GPO update on computers using the Invoke-GPUpdate PowerShell cmdlet.

For example, to remotely update user policy settings on a specific computer, we can run:

Invoke-GPUpdate -Computer "frparsrv12" -Target "User"

If we run this cmdlet without any parameters, it will update the GPO settings on the current computer.

Together with the Get-ADComputer cmdlet, we can update GPO on all computers in a specific OU:

Get-ADComputer –filter * -Searchbase "OU=Computes,OU=Mun,OU=DE,dc=woshub,dc=com" | foreach{ Invoke-GPUpdate –computer $_.name -force}

Or on all computers meeting the specific requirement:

Get-ADComputer -Filter {enabled -eq "true" -and OperatingSystem -Like '*Windows Server*' }| foreach{ Invoke-GPUpdate –computer $_.name –RandomDelayInMinutes 10 -force}

If we run the Invoke-GPUpdate cmdlet remotely or update GPO from the GPMC, we may find a console window with the running gpupdate command on a user desktop for a while.

[Finding it hard to figure? We’d be happy to assist]

 

Conclusion

In short, we saw how our Support Techs update Group Policy Settings on Windows Domain Computers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF