Patching Cadence & Updates

Teams Site Updates

Only owners can post to Teams channels; this has been restricted.
Power Automate is configured so anyone in the Teams site receives email notifications for channel posts, creating a subscription basis.

Reviewing the distro list from the last meeting to ensure the correct contacts are included for older integration projects.
Confirmation that Carrot manages everything under Dentsu infrastructure (Dentsu DentsuX, iProspect, Creative, DentsuMedia), as part of Eaton.
Support only is relevant here.
These are all the same regarding support.
Creative and media are covered, primarily based in the UK and EMEA.
No changes are required to the distro list.

Previous list contained unmanaged servers.
Contacts might have been incorrect or too high-level; Suresh was to find the correct contacts.
TCS (Tata Consultancy Services) manages communication for locally managed servers.
TCS informs them of what needs to be done and follows up.
TCS handles locally managed servers and communication, including those globally located (e.g., Poland, Spain).
The TCS contacts are already in the system, including batching contacts from TAG, DJs, and IMS.
Locally managed servers exist globally (e.g., in Poland, Spain).
These local teams are responsible for bi-weekly patching.

DML, present specifically in Germany, relies on Windows and Linux machines and is heavily dependent on Oracle databases.
Communications regarding patching (Linux, Windows, and databases) are coordinated globally for DML.
Testing is performed after patching.
The process is critical and requires coordinated communication among all involved parties.
Patching occurs over four weeks.
Windows servers are patched on one day within the four-week window.
Linux patches are aligned with database updates using Atriumix for service management.
OS, application, and database patching are coordinated.
TCS handles patching requirements, including communication and follow-ups.
DML receives communications regarding patches through TCS and change management processes.
Change requests are used to discuss dependencies and potential postponements.
Critical APIs and infrastructure are not patched in the first two weeks to avoid potential rollbacks.
Patching occurs in the third and fourth weeks, with predefined downtime for production, test, and staging servers.

The distro list is shared in a folder (a giant spreadsheet) and was included in the last email.
A new "current distro" tab will be added to the spreadsheet with email addresses, copied directly from the last email.
This will allow for easier review and updates by the team.

Set to proceed with patching on Tuesday.
A monthly call with TCS will be scheduled before the patching week to discuss additions, removals, exceptions, and other considerations.
This call will include Justine and will be arranged by the TCS team.