Wsus updating non domain computers speed dating younger people

This system is not connected to the domain most of the time (laptop).

In Microsoft knowledge-base they say that this is caused by WSUS (Windows Server Update Services).

wsus updating non domain computers-24wsus updating non domain computers-10wsus updating non domain computers-19

To understand what I’m talking about, think of a network of 300 PCs, maybe that network is already in your company; you deployed a WSUS server but clients still go to Microsoft for updates, and you want to point them to your WSUS Server.

Off course is an ugly job to do this manually for 300 clients, but this is where Group Policy comes in.

The reason why I still normally recommend that people using WSUS over SCCM is that the product overall is much easier to use and its just human nature for people to want to do the easier tool where possible…

However there are a couple of reason why I think SCCM should still be used over WSUS and they are: Below are a collecting of configuration recommendations and tips that help you get the most our of your WSUS infrastructure in your environment.

Restart the clients or force the policy on them in order to take effect; but if you are not in rush, just wait between 90-120 min for the policy to apply on clients.

I forced the policy (since I have only two clients) using gpupdate /force command.

These are in no particular order of importance and you might chose to implement only some of these setting depending on your environment.

Introduction Windows Server Update Services (WSUS) can be used to manage the deployment of the latest Microsoft Windows operating system updates.

When installing WSUS server, we need to choose “Full server installation including Administration Console” rather than “Administration Console only,” as shown in the picture below.

Tags: , ,