Friday , July 20 2018

Policies you should never configure on Windows 10 with WSUS

When you have windows 10 in your environment and machines are configured with Windows Server Update Services. You should never configure Branch readiness level or tried to delay or defer feature  upgrades or quality updates using group policy.

If you do that . The moment any one of these policies are configured, even if these are set to be “disabled”, a new behavior known as Dual Scan is invoked in the Windows Update agent. where windows will try to update from Online servers directly and from wsus. and you can see random clients getting feature upgrades.

image

Random clients will start getting feature upgrades in a windows environment like below. Causing inconsistent versions in the environment. when you have various clients computers using legacy applications. you never want to roll out something which you never tested.

image

Once you set these Policies to “Not Configured”

Windows Updates Registry – When any of the policies configured.

image

When all the policies set to Not Configured. Requesting the Windows 10 clients to talk to Speak to wsus only for upgrades and updates.

image

 

Reference link –

https://cloudblogs.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Exchange Server MVP , Publisher of CareExchange.in
Supporting/Deploying/Designing Microsoft Exchange for some years.
Extensive experience on Microsoft Technologies.

Check Also

Configuring Avamar Backup with Exchange 2016

In my Case its a 4 Member DAG . Lets see how to Configure Avamar ...

Leave a Reply

Your email address will not be published.