SCSM componant should apply new Windows Cummulative Update

For this Service Manager 2022 UR2 environment, Windows Server and SQL Server security/cumulative updates can be applied as standard OS/SQL maintenance, provided that supported versions and prerequisites for SCSM are respected and the rollout is staged.

A safe, controlled approach is:

1. Verify platform support and prerequisites
   • Confirm that all SCSM roles (management servers, DW, portal, SQL hosts) run a supported Windows Server version (2019/2022/2025 are supported for all SCSM roles).
   • Confirm that the SQL Server version and CU level remain within SCSM support after patching. For Service Manager, SQL Server 2019 CU8+, SQL Server 2022, and SQL Server 2025 (from SCSM 2025 UR1) are supported for the operational and DW databases. See the SQL support matrix and system requirements to ensure the final target version is supported.
   • Ensure SQL Servers are configured to allow updates as required by Service Manager setup (check sp_configure 'allow updates' is 0 before and after maintenance if any setup/upgrade is run later).
2. Plan order of patching and maintenance windows
   Use SCCM to stage updates in waves, with maintenance windows per server group:
   • Wave 1: Self-Service Portal servers (stateless, easiest to roll back by removing from load balancer if used).
   • Wave 2: SCSM Management Servers (one at a time so at least one remains online).
   • Wave 3: Data Warehouse Management Server.
   • Wave 4: SQL cluster nodes hosting the SCSM operational and DW databases (follow SQL clustering best practices and patch one node at a time with failover).
3. Windows Server cumulative updates via SCCM
   For each wave:
   • Place the server in maintenance mode in SCOM (if monitored) and announce SCSM downtime if needed.
   • Use SCCM to deploy the Windows cumulative update to the target collection with a defined maintenance window.
   • Reboot when required and verify:
     • SCSM services start (System Center Data Access, System Center Management, SDK, Workflow, etc.).
     • Portal site is reachable after portal server reboots.
     • Event logs show no SCSM or SQL connectivity errors.
4. SQL Server security/CU updates on the cluster
   • Confirm the target SQL 2022 CU/security update is supported for SCSM (SQL 2022 is supported; keep within supported ODBC/MSOLEDBSQL ranges as documented).
   • Patch one SQL node at a time:
     1. Fail SCSM databases to node B.
     2. Apply the SQL CU/security update on node A using SCCM or manual installer.
     3. Reboot node A if required and verify SQL services and cluster health.
     4. Fail SCSM databases back to node A (if desired) and repeat for node B.
   • After patching, validate:
     • SCSM console can connect and open work items.
     • DW jobs run successfully.
5. Data Warehouse specific consideration
   • Because the environment is on SCSM 2022 UR2, ensure that any future SCSM update rollups applied to the DW management server follow the documented workaround if the DW was upgraded from 2019 (copy build_scdm_db.sql and build_scdw_db.sql into C:\Program Files\Microsoft System Center\Service Manager\DW before re-running the UR installer). This is not required for regular Windows/SQL patching but is important for future SCSM URs.
6. Post‑patch validation
   After all servers are patched:
   • Run through key SCSM scenarios: create/resolve incidents, run reports, verify portal submissions, and confirm DW cube processing.
   • Monitor for a full DW ETL cycle to ensure no SQL or SSRS issues.
7. Ongoing SQL security posture
   • Keep SQL instances on the latest supported CU/GDR for the installed major version to address vulnerabilities. This is explicitly recommended for mitigating SQL elevation-of-privilege issues.

This approach lets SCCM deliver Windows and SQL updates while staying within the supported SCSM/SQL/Windows matrix and minimizing risk through phased rollout and validation.

References:

• Update Rollup 2 for System Center 2022 Service Manager
• System requirements for System Center Service Manager
• SQL Server requirements for System Center - Service Manager
• Update Rollup 2 for System Center 2022
• inc microsoft sql server elevation of privilege vulnerability - Microsoft Q&A