Upgraded the operating system on our configuration manager server from 2019 to 2022 and the remote management points are now showing critical with 0mb.

The Windows Server 2019 to Windows Server 2022 in-place upgrade is supported for Configuration Manager site systems. However, the Critical / 0 MB state usually means the site server can no longer retrieve storage or status information from the remote site system. Since clients also cannot use those management points, this is not only a stale console status issue.

The two installed updates do not appear directly related:

• KB37942646 updates the Cloud Management Gateway VM scale-set image.
• KB38232642 secures Configuration Manager console-extension imports.

I recommend checking the following on one affected remote management point.

1. Test the management point endpoints

From both the site server and an affected client, browse to:

http://<MP-FQDN>/sms_mp/.sms_aut?mplist
http://<MP-FQDN>/sms_mp/.sms_aut?mpcert

Use HTTPS instead if the management point is configured for HTTPS.

Record the exact response, such as HTTP 401, 403, 500, 500.19, 503, timeout, or a valid XML response. Also review the IIS logs under:

C:\inetpub\logs\LogFiles

If the result is HTTP 500.19, check whether the WSUS XPress compression schema is registered in IIS. Microsoft documents that an incompatible suscomp.dll registration can stop management points from responding.

Check the management point logs

On the affected management point, review:

MPSetup.log
MPMSI.log
MPControl.log
CcmIsapi.log

On the site server, review:

SiteComp.log
SiteSystemStatusSummarizer.log

Do not rely only on a successful role installation in MPSetup.log. MPControl.log should show successful management-point availability and HTTP/HTTPS checks. Configuration Manager logs are the primary source for identifying component and communication failures.

3. Verify remote site-system connectivity

From the site server, confirm that you can access:

\\<RemoteMP>\admin$

Also verify:

• The site server computer account is still a local administrator on each remote management point.
• RPC, WMI, SMB, and the configured HTTP/HTTPS ports are allowed.
• Windows Firewall profiles or security baselines were not changed by the OS upgrade.
• DNS resolves the management-point FQDN to the correct address.
• No duplicate or stale DNS records exist.
• The SMS_EXECUTIVE, IIS, and Windows Management Instrumentation services are running.

Failure to access the remote server through administrative shares, WMI, or RPC would explain the reported 0 MB status, although the exact failure should be confirmed in SiteSystemStatusSummarizer.log or SiteComp.log.

4. Verify IIS and management-point prerequisites

Confirm that the required IIS, BITS, .NET Framework, and IIS 6 Management Compatibility components are still installed. The prerequisite check specifically requires BITS, IIS common components, and IIS 6 WMI compatibility for management points.

Also check:

• The SMS Management Point Pool application pool is started.
• The Configuration Manager virtual directories exist in IIS.
• IIS bindings match the HTTP or HTTPS mode configured in Configuration Manager.
• The server certificate is valid and correctly bound if HTTPS is used.
• There are no corresponding errors in the Application and System event logs.

5. Restart status evaluation after resolving connectivity

After correcting the underlying IIS, firewall, WMI, or permission issue:

iisreset

Then restart the SMS_EXECUTIVE service on the site server and monitor the logs. Allow the Site System Status Summarizer time to refresh before resetting the status manually in the console.

If the problem continues, please provide:

• The relevant error sections from MPControl.log
• SiteComp.log and SiteSystemStatusSummarizer.log entries for one affected MP
• The HTTP status returned by both test URLs
• Whether the remote MPs were also upgraded to Windows Server 2022
• Whether the MPs use HTTP, enhanced HTTP, or HTTPS
• Any IIS errors and the associated IIS substatus code

Please remove server names, domain names, certificates, credentials, tokens, connection strings, and other sensitive information before posting the logs.