Using the same example scenario and the same infrastructure, we will now look at patching for servers rather than workstations. As a review, here are the requirements from the customer.
In this scenario, our customer will deploy patches to servers in a monthly cycle. This cycle will closely align with the Patch Tuesday concept.
Deployments will be created and sent to a pilot group of workstations a week after the patches are released by Microsoft.
Following the deployment of patches to a pilot group, the deployment will then be sent to the remainder of the workstations.
Portions of the process need to be automated to reduce administrative effort.
Only critical updates and security updates are required for Windows Server 2012 R2. No third-party or in-house updates are required.
The solution needs to be implemented using existing equipment.
The administrator should be able to report on patch compliance on either a monthly, quarterly, or yearly...