SCCM service corrupted after migrating VM with Azure Migrate to HCI cluster

Question

SCCM service corrupted after migrating VM with Azure Migrate to HCI cluster

DA-Bojan Njegovan 0

6 Mar 2025, 2:59 pm

Hi,

We have issue with SCCM server when we complete migration via Azure Migrate from old server to new HCI server solution.

We need assistance.

Kind regards

Ashok Gandhi Kotnana 4,310 Reputation points Microsoft External Staff

6 Mar 2025, 3:18 pm
Hi @DA-Bojan Njegovan ,

Please provide more information on this request.

Can you provide more details about the issue? What specific error message are you seeing?

On which operating system did the error occur? Is it on the SCCM server, clients, or another system?

When did the issue start? Did it happen immediately after migration, or was SCCM working for some time before the error appeared?

Has the Test failover has not been validated properly before doing the final migration

Thankyou
DA-Bojan Njegovan 0 Reputation points

7 Mar 2025, 9:12 am

Hi Ashok,

The SCCM was working fine before migration to the HCI cluster.

We followed all steps from documentation, and migration was completed successfully, no issue with migration to HCI cluster.

After the migration SCCM was corrupted, and our development team cannot recover it. They can only rebuild new SCCM service from scratch.

SCCM Management Point (mpcontrol.log) component is throwing error code 500 (Internal Server Error).

IIS is in perfect condition.

We try to rebuild Management Point and rebuilding went smooth and with no error, but error is still present.

SCCM client cannot communicate with SCCM site because MP is broken.
Ashok Gandhi Kotnana 4,310 Reputation points Microsoft External Staff

7 Mar 2025, 9:32 am

Hi @DA-Bojan Njegovan

The HTTP 500.19 error can arise from several factors, such as problems with IIS or misconfigurations in the Management Point setup.

One possible cause is a conflict stemming from a previous installation of the WSUS server role on the Management Point computer, which might interfere with the XPress compression schema. If this applies to your environment, inspect the applicationHost.config file for the XPress compression schema and remove it if needed, following the recommended troubleshooting steps for HTTP Error 500.19.

It’s also important to review the IIS logs for any additional issues that could be disrupting communication between the Management Point and SCCM clients.

If the Management Point rebuild was completed successfully but the error continues, double-check the configuration settings and confirm that all required services are functioning as expected.

Refer below links which talks more about the error message:

https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/setup-migrate-backup-recovery/management-points-stop-responding

https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/client-management/cmg-communication-error#resolution-3

Let me know if you need further clarification or assistance!

Hope this information helps you!
DA-Bojan Njegovan 0 Reputation points

7 Mar 2025, 12:53 pm

Hi,

We try already removing XPress compression schema, but it wasn't working either.
Madugula Jahnavi 5 Reputation points Microsoft External Staff

7 Mar 2025, 4:05 pm

DA-Bojan Njegovan, Thanks for confirming that you have tried removing the XPress compression schema which did not resolve the issue. Have you tried reviewing the IIS logs once for any specific errors related to SCCM and also event viewer application logs for any error related information!
DA-Bojan Njegovan 0 Reputation points

10 Mar 2025, 7:50 am

Hi, we had only HTTP error 500, as mentioned first time.
Madugula Jahnavi 5 Reputation points Microsoft External Staff

10 Mar 2025, 4:46 pm

DA-Bojan Njegovan, Ok. Can you check are there any repeated value entries in ApplicationHost.config and try just deleting the entries to make it work without any conflicts!