The Configuration Manager deployment targeting this server must be corrected: its CCM_UpdateCIAssignment policy contains eight Windows 10/11 updates and no Windows Server 2022 cumulative update, so revise the originating software update group or ADR and deploy the Server 2022 update to the correct server collection.
EnforcementEnabled=FALSE also means the displayed assignment is not currently enabled for enforcement; it does not make those client updates applicable to Server 2022.
1. Identify and remove the incorrect deployment
In the Configuration Manager console:
- Go to Monitoring → Deployments.
- Locate the software-update deployment targeting this device or its collection.
- Add or inspect the Deployment Unique ID and compare its assigned updates with the eight CIs shown in WMI.
- Open the deployment’s software update group under Software Library → Software Updates → Software Update Groups.
- Remove the Windows 10/11 updates from that server-specific group, or disable/delete the deployment if the entire assignment is wrong.
- Inspect the target collection membership. Remove the server from any workstation update collection unless membership is intentional.
Configuration Manager creates deployment assignment policy containing the updates in the software update group, then sends that machine policy to clients in the targeted collection.^1^ The client-side WMI output therefore shows which deployment policy reached this server; it is not evidence that Windows Server considers those packages applicable.
If an ADR created the deployment:
- Go to Software Library → Software Updates → Automatic Deployment Rules.
- Open the rule responsible for the July deployment.
- On Software Updates, change its criteria so the server ADR selects only the required Windows Server 2022 updates.
- On Deployment Settings/Deployment Package, verify it targets the intended server collection.
- Run the ADR manually and review the resulting update group before enabling its deployment.
An ADR evaluates its criteria, downloads matching updates, creates or updates a software update group, and creates the deployment assignment.^2^
2. Synchronize the Windows Server 2022 catalog
Perform this at the top-level site:
- Open Administration → Site Configuration → Sites.
- Select the central administration site or stand-alone primary site.
- Select Configure Site Components → Software Update Point.
- On Products, select Windows Server 2022.
- On Classifications, select the classifications used by your servicing process—normally at least Security Updates, Critical Updates, and Update Rollups where applicable.
- Close the properties.
- Go to Software Library → Software Updates → All Software Updates and select Synchronize Software Updates.
- After synchronization completes, search for the required Windows Server 2022 KB and confirm its metadata appears.
Configuration Manager retrieves only the update metadata matching the configured products and classifications. After selecting a newly required product, another synchronization is necessary.^3^
Do not select unnecessary products merely to troubleshoot this server. Clients evaluate synchronized metadata during scans, and excess products increase catalog size and can reduce scan performance.^4^
Seeing a Windows 10/11 title in the console alone does not always prove incorrect product selection because an update applicable to multiple synchronized products can display all associated products. In this case, however, those updates are present in the client’s assigned deployment, so both deployment contents and collection targeting require inspection.^3^
3. Create the corrected Server 2022 deployment
After synchronization:
- In All Software Updates, search for the applicable Windows Server 2022 cumulative update.
- Confirm it is not Expired or Superseded according to your deployment policy.
- Add it to a server-specific software update group.
- Download and distribute its content to the distribution point used by the server.
- Deploy that group to the Windows Server 2022 collection.
- Trigger these client actions from Control Panel → Configuration Manager → Actions:
- Machine Policy Retrieval & Evaluation Cycle
- Software Updates Scan Cycle
- Software Updates Deployment Evaluation Cycle
- Confirm the new update appears as Required or Available in Software Center, according to the deployment purpose.
At evaluation time, Configuration Manager requests another update scan to verify that each deployed update remains applicable before installation.^5^
4. Trace the boundary if Server 2022 updates remain absent
Because the assignment has already been inspected, do not reset SoftwareDistribution or the Configuration Manager client yet. Trace where the correct update disappears:
- Site server
-
wsyncmgr.log: synchronization and metadata import -
WCM.log: SUP products, classifications, and WSUS connection -
WSUSCtrl.log: WSUS health and database connectivity -
ruleengine.log: ADR selection, update-group creation, and deployment
-
- Client
-
PolicyAgent.logandPolicyEvaluator.log: receipt/evaluation of corrected policy -
UpdatesDeployment.log: deployment evaluation -
WUAHandler.logandScanAgent.log: applicability scan
-
Microsoft documents these server-side log purposes in the Configuration Manager log reference.^6^
Expected result: the old assignment is withdrawn after policy refresh, a new assignment contains the Windows Server 2022 CI, and the scan reports that update’s applicability. If wsyncmgr.log never imports the Server 2022 KB, the issue remains at SUP/WSUS synchronization; if it imports successfully but ruleengine.log excludes it, correct the ADR criteria; if the correct deployment exists server-side but is absent from client policy, correct collection membership or policy targeting.
References