Skip to content

Commit

Permalink
Update Rule “do-you-use-group-policy-to-manage-your-windows-update-po…
Browse files Browse the repository at this point in the history
…licy/rule” (#6185)

* Update Rule “do-you-use-group-policy-to-manage-your-windows-update-policy/rule”

* Update rule.md

---------

Co-authored-by: Tiago Araújo [SSW] <[email protected]>
  • Loading branch information
kikibianc and tiagov8 authored Jul 31, 2023
1 parent 6b5f5b4 commit 14de565
Showing 1 changed file with 29 additions and 52 deletions.
Original file line number Diff line number Diff line change
@@ -1,41 +1,34 @@
---
type: rule
archivedreason:
title: Do you use Group Policy to manage your Windows Update Policy?
guid: 19452101-3232-446e-9932-2e8486b410d4
uri: do-you-use-group-policy-to-manage-your-windows-update-policy
created: 2011-03-21T00:27:18.0000000Z
authors:
- title: Matthew Hodgkins
url: https://ssw.com.au/people/matthew-hodgkins
- title: Adam Cogan
url: https://ssw.com.au/people/adam-cogan
related: []
- title: Matthew Hodgkins
url: https://ssw.com.au/people/matthew-hodgkins
- title: Adam Cogan
url: https://ssw.com.au/people/adam-cogan
related:
- do-you-disable-automatic-windows-update-installations
- do-you-turn-off-auto-update-on-your-servers
redirects: []

created: 2011-03-21T00:27:18.000Z
archivedreason: null
guid: 19452101-3232-446e-9932-2e8486b410d4
---

We all know it’s important to keep our servers updated. Unfortunately though, by default, Windows will automatically download and install all new Windows Updates on your servers. This will mean the servers will occasionally restart to install updates when you don’t want them too. You will also get annoying popups trying to get you to restart the computer.

<!--endintro-->

**Note:** This rule applied to both client PCs and servers.



**Note:** This rule is applied to both client PCs and servers.

It is also one more reason developers don’t like to join a company domain on their personal laptops!




::: bad
![Bad Example - Windows 10 shows a ‘Restart now’ – do not accidentally press it! Your production server and your users won't be happy!](Windows-Update-notification.png)
::: bad
![Figure: Bad example - Windows 10 shows a ‘Restart now’ – do not accidentally press it! Your production server and your users won't be happy!](Windows-Update-notification.png)
:::


::: bad
![Bad example – Remember this nasty one from Vista days?](updates-restart.jpg)
::: bad
![Figure: Bad example – Remember this nasty one from Vista days?](updates-restart.jpg)
:::

**Note:** Server patching is also achievable via SCCM and you get more control over restarting windows like this. WSUS can also be used in conjunction with group policies to handle restart times better.
Expand All @@ -44,48 +37,32 @@ The best ensure you are still downloading updates but not installing them automa

1. Create an Organization Unit (OU) in Active Directory, and put all your Production Servers in the OU

![Add all your Production Servers to the Production Server OU](updates-adou.jpg)
![Add all your Production Servers to the Production Server OU](updates-adou.jpg)

2. Create a new Group Policy object and link it to the Production Server OU

![Create a new Group Policy for your Production Servers](updates-gpo.jpg)
![Create a new Group Policy for your Production Servers](updates-gpo.jpg)

3. Edit the new Group Policy object and drill down to
**Computer Configuration** |
**Policies** |
**Windows Components** |
**Windows Update**
4. Edit the
**Configure Automatic Update Properties** item and
**enable** it
5. Set the
**Configure Automatic Updating** option to
**3 – Auto download and notify for install
3. Edit the new Group Policy object and drill down to
**Computer Configuration** | **Policies** | **Windows Components** | **Windows Update**

![Edit Configure Automatic Updates Properties and enable 'Auto download and notify for install](updates-editgp.jpg)
**
4. Edit
**Configure Automatic Update Properties** item and **enable** it

5. Set **Configure Automatic Updating** option to **3 – Auto download and notify for install**

After the new Group Policy propagates, you will notice the update setting is now locked on the servers in the Production Server OU.
![Edit Configure Automatic Updates Properties and enable 'Auto download and notify for install](updates-editgp.jpg)

After the new Group Policy propagates, you will notice the update setting is now locked on the servers in the Production Server OU.

::: good
![The Group Policy locks the Windows Update setting](updates-updatesforced.jpg)
::: good
![Figure: Good example - The Group Policy locks the Windows Update setting](updates-updatesforced.jpg)
:::



From now on your servers will be updated without unplanned reboots!


::: good
![Figure: Good example - AD shows the Group Policy setting “3 – Auto download and notify for install”. This policy is applied to the specified OU eg. Production Servers joined to this domain](Default domain policy1.png)
::: good
![Figure: Good example - AD shows the Group Policy setting “3 – Auto download and notify for install”. This policy is applied to the specified OU eg. Production Servers joined to this domain](Default domain policy1.png)
:::



### Related Rules


* [Do you enable automatic Windows Update Installations?](/do-you-disable-automatic-windows-update-installations) [for PCs]
* [Do you turn off auto-update on your servers?](/do-you-turn-off-auto-update-on-your-servers) [for Servers]
Check out "auto-update" rules for [PCs](/do-you-disable-automatic-windows-update-installations) and [Servers](/do-you-turn-off-auto-update-on-your-servers).

0 comments on commit 14de565

Please sign in to comment.