WSUS Server Patching Rollout Policy

This is our WSUS timeline for rollout of MS updates each month. The rollout will consist of two phases,
will happen on the timeline below to the computers listed below. The same process will happen each
month. OSI must reference this document each time to gather the computer names for Phases 1 and 2.
These computer names may/will change from time to time if new server is added to the environment
and will be the responsibility of David/Manir and Scott/Peter (or their backups) for approval or any
comments before patching schedule. Dates are not needed to describe the rollouts because Patch
Tuesday is always the second Tuesday of each month. From now on PT will be used to say Patch
Tuesday.

Phase 1 – The updates will be released, by OSI Team, to Phase 1 Servers after PT. For example, February
the date is 02-15-2020, March will be 03-07-2020 and so on. Before releasing patches to servers OSI
Team will send a notification email to Oasis IT team for confirmation/Approval/ for any comments.
Validation of these computers will be with respective Teams.

Validations:
 Check for critical services on the servers
 Check for Canary svc-rdpsoft login and its related services.
 Email respective Teams like Application team for application servers and DB Team for DB related
servers to check their services/tasks on the servers. Also help the teams accordingly if needed.

Released on weekend after Validation by Respective Send completion Notification email to

PT Teams (Windows, Oasis IT team and Proceed to Phase 2 as
Application, DB etc) per schedule.

Phase 2 – The updates will be released, by OSI Team, to Phase 2 Servers on first week of coming month
of before PT of next month. For example, February the date is 02-15-202 (Weekend) Phase1 patches
were published and Phase 2 will be on March will be 03-14-2020 and so on AND Validation of Phase 1 is
complete. Before releasing patches to servers OSI Team will send a notification email to Oasis IT team
for confirmation/Approval/ for any comments. Validation of these computers will be with respective
Teams.

Validations:
 Check for critical services on the servers
 Check for Canary svc-rdpsoft login and its related services.
 Email respective Teams like Application team for application servers and DB Team for DB related
servers to check their services/tasks on the servers. Also help the teams accordingly if needed.
 Use rimsmessaging credentials for WEB and VM-Keymeds machines patching and
validation.
Released EOD Friday after Validation by Respective Proceed to Phase 1 patches for next
Approval Teams (Windows, month.
Application, DB etc)