Windows Server Patching - Chaithanyaa7/VMware GitHub Wiki

Windows Patching :

Once Microsoft release the patches on 10th of Every month / 2nd Tuesday

Those patches will be downloaded and tested by patch validation team to check whether this patch will impact our infra or Application

If that team confirms to install patches we will download them and copy to " Shavlik " - Patching tool Ivanti ( 12.2.3)

Then We will create the Change Record ( CR) and get approved and perform Test server patching

Draft -> Approval -> Implementation -> Close , Failed

Test Servers ( Shavlik )

Shavlik will automate the Patch Copy Deployment and Reboot process

10th Patch 11AM copy 1PM Install 2 PM Reboot

3PM Shavlik - Validations ( Application - Test login is working )

Then We will create the Change Record ( CR ) and get approved and perform Dev server patching ( Test Server application validation result )

Development Servers

Shavlik will automate the Patch Copy Deployment and Reboot process

17th Patch 11AM copy 1PM Install 2 PM Reboot

3 PM Shavlik - Validations ( Application - Dev login is working )

Close the CR as successful.

Then We will create the Change Record ( CR) get approved and perform Production server patching ( Test and Dev Validations )

Productions :

Before Staring install patches on Prod Servers we will take snapshots for all Servers

Shavlik will automate the Patch Copy Deployment and Reboot process

24th Patch 11AM copy 1PM Install 2 PM Reboot

3PM Shavlik - Validations ( Application - Prod login is working )

Close the CR as successful.