In this article we will consider how to configure clients of the WSUS server using Active Directory GPO (Group Policies).
AD Group Policies allow the administrator to automatically assign computers to different WSUS groups, saving him the trouble of manually moving the computers between groups in the WSUS console and support these groups up-to-date.
This tool downloads all the patches as per your selection and stores in a folder, which will contain an executable to update any PC () offline.
Not only that before updating it also detects that what already had been updated and more of it, the tool downloads updates in incremental ways, so that every time the folder will keep on growing to catch up the new updates.
In one of the previous articles we have described the installation of a WSUS server on Windows Server 2012 in detail.
The next step – configure Windows clients to use a deployed WSUS server.
What’s next in my post is nothing special that most of smart admins might not been knowing about, but I thought to make a step by step guide over WSUS from the resources already available over internet.
Offline updates solution: Autopatcher: When you talk about updating few PCs just built up and installed, then the best tool that strikes me is Autopatcher.
The Create Automatic Deployment Rule Wizard starts.
Windows Server Update Services (WSUS) is one of the best solution for your all such worries.
If you are running a setup of at least 50 PCs then you sure must be knowing about WSUS already and if you not or thought that its too hard to implement then its about time to take note of it.
Finally, in part three, I’ll go over WSUS 2012, reporting, and Power Shell.
Don’t forget that Group Policy settings can take up to 90 minutes to apply.