How to configure a WSUS standalone server

Case



You need to configure a Windows Server Update Services (WSUS) server to provide Windows updates to all servers in your on-premises infrastructure. There are various WSUS architecture options for high availability, however this article will focus on the simple scenario of how to configure a WSUS standalone server, which can cover the requirements of many infrastructures.



Solution



Carry out the steps below to the configure a WSUS standalone server.



- Setup the VM or physical machine where the WSUS server role will be installed and install all latest Windows updates.

- Install the WSUS server role in the Windows Server Manager with Windows Internal Database (WID), setup the required UNC path for WSUS storage with proper SMB and NTFS permissions, as per https://stefanos.cloud/kb/windows-server-update-services-wsus-share-permissions/.









- After rebooting the server, run the WSUS post-installation process when you launch the WSUS MMC console. Click Run to continue.





- Run the WSUS first time configuration wizard in Microsoft Management Console (MMC) for the initial synchronization, setup proxy and synchronization schedule and configure SSL for WSUS if needed, as per the following instructions: https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/2-configure-wsus.



















- Configure all other WSUS options in the above "Options" pane, as per your environment requirements.

- Configure WSUS SSL as per: https://docs.microsoft.com/en-us/previous-versions/orphan-topics/ws.11/dn343567(v=ws.11)?redirectedfrom=MSDN.

- Approve and Deploy Updates in WSUS as per: https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/3-approve-and-deploy-updates-in-wsus.

- Create computer groups, to organize WSUS targets in a logical fashion.

- Assign computers to groups for WSUS using GPO.

- Configure WSUS auto-approval rules.

- Configure Windows updates auto-install schedule via GPO as per the following instructions: https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/4-configure-group-policy-settings-for-automatic-updates.

If you encounter any issues in your WSUS environment during initial testing, consult the following articles for WSUS troubleshooting:



- https://stefanos.cloud/kb/how-to-resolve-wsus-and-windows-update-common-errors/

- https://stefanos.cloud/kb/how-to-resolve-wsus-connection-error/

- https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-issues-with-wsus-client-agents

- https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-wsus-connection-failures

- https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-wsus-import-sync-issues

- https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/manage/wsus-messages-and-troubleshooting-tips

- https://docs.microsoft.com/de-de/security-updates/windowsupdateservices/21669506

- https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/wsus-maintenance-guide

Also remember to check the following dependent components of the WSUS installation when performing troubleshooting:



- IIS manager and related files



- WSUS WID or SQL Server database

- Registry keys related to WSUS

- File share of the WSUS server and local Windows update cache on each WSUS target
https://stefanos.cloud/kb/how-to-configure-a-wsus-standalone-server/

Comments

Post a Comment

Popular posts from this blog

Acronis Cyber Protect 15 virtual machine backup not working when using shared mode virtual disks vhds

Image
Case When you apply and run an Acronis Cyber Protect backup against a virtual machine which is part of a guest cluster which makes use of virtual disk shared files of type .vhds (VHD Set), you run across the following error. Activity succeeded with warnings. Activity 'Preparing for backup of virtual machine' succeeded with the following warning 'Windows error: (0xC05CFF0A). The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. Or the error may state something along the lines of: "Failed to open virtual disk file '.vhds'. Unknown format of the virtual disk." The same error as above can occur in virtual machine backup of virtual machines which include a .vdhx shared disk. Solution The above error is by design when you are attempting a virtual machine backup to virtual machine which does not have an Acronis backup agent installed, as per https://kb.acronis.com/content/68573 . According to Acronis, as of July 2
Read more

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom
Read more