We have successfully installed SCOM 2022 environment in my lab, the issue is after the successful installation, the Management server is showing as Not Monitored State.

Shiva Ravichandran 41 Reputation points
2024-01-06T11:40:46.1466667+00:00

We have successfully installed SCOM 2022 environment in my lab, the issue is after the successful installation, the Management server is showing as Not Monitored and we got the error in the event viewer as “A monitoring host is unresponsive or has crashed, the status code for the host failure was 2164195371”. Event ID : 4000.

Kindly someone help here…

All the account were created and added to the admin group in AD, setup the DB and installed the SCOM 2022 setup in Windows 2022 server as suggested by Kevin Holman.MicrosoftTeams-image.png

System Center Operations Manager
System Center Operations Manager

A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.

Microsoft System Center | Other
0 comments No comments

2 answers

Sort by: Oldest
  1. XinGuo-MSFT 22,351 Reputation points
    2024-01-08T07:45:34.7966667+00:00

    Hi,

    Health Service : EventID 4000
    A monitoring host is unresponsive or has crashed. The status code for the host failure was 2164195371.

    Crashes in the MonitoringHost are related to the feature Hardware-enforced Stack Protection based on Intel’s Control-flow Enforcement Technology (CET).

    Did you try what Kevin mentioned? Disable “Hardware-enforced Stack Protection” for the MonitoringHost.exe process, via this PowerShell command:

    Set-ProcessMitigation -Name MonitoringHost.exe -Disable UserShadowStack
    Restart-Service -Name HealthService

    Was this answer helpful?

    1 person found this answer helpful.

  2. Marius Ene 345 Reputation points
    2024-02-01T00:49:16.5133333+00:00

    Make sure you have applied the latest updates and UR packs to SCOM. Also check that the Microsoft monitoring agent service is running on the Management Server. If it is, do a restart of this service. Marius ENE (https://mariusene.com/ )

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.