Start & Stop all OpsMgr Services on all SCOM Management Servers in a mass with Powershell

Description : This Powershell Script is basically intended to stop and start OpsMgr related services (“cshost”, “healthservice”, “omsdk”) on all SCOM Management Servers in a mass. This script can be used to stop and start other windows services too. You basically need to enter the server and service name into the related arrays. The Script…


Part 12 : SCOM 2012 R2 HealthService Event Reference / PoolManager

PoolManager EventID=15000Severity=Informational Message=The pool member has initialized %n%nManagement Group: %1 %nManagement Group ID: %2 %nPool Name: %3 %nPool ID: %4 %nPool Version: %5 %nNumber of Pool Members: %6 %nNumber of Observer Only Pool Members: %7 %nNumber of Members Added: %8 %nNumber of Members Removed: %9 %nNumber of Instances: %10 %nNumber of Instances Added: %11 %nNumber…


Part 11 : SCOM 2012 R2 HealthService Event Reference / JobManager

JobManager EventID=9000Severity=Error Message=The task status was changed to Failed on restart and was unable to be resumed because the System Center Management service was shut down EventID=9001Severity=Warning Message=The task is not active, and the task status was not correctly updated There is no way to determine if the task has run EventID=9002Severity=Error Message=The task is…


Part 10 : SCOM 2012 R2 HealthService Event Reference / DataPublisherManager

DataPublisherManager EventID=8000Severity=Warning Message=A subscriber data source in management group %1 has posted items to the workflow, but has not received a response in %5 minutes Data will be queued to disk until a response has been received This indicates a performance or functional problem with the workflow%n Workflow Id : %2%n Instance : %3%n Instance…


Part 9 : SCOM 2012 R2 HealthService Event Reference / DiscoveryManager

DiscoveryManager EventID=10000Severity=Warning Message=A scheduled discovery task was not started because the previous task for that discovery was still executing %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group name: %1 EventID=10001Severity=Warning Message=An error occurred starting a discovery task %nError Code: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group name: %2 EventID=10002 Severity=Warning Message=Unable to write…


Part 8 : SCOM 2012 R2 HealthService Event Reference / SecureStorageManager

SecureStorageManager EventID=7000Severity=Error Message=The Health Service could not log on the RunAs account %1%2 for management group %5 The error is %3(%4) This will prevent the health service from monitoring or performing actions using this RunAs account EventID=7001Severity=Warning Message=The password for RunAs account %1%2 for management group %5 is expiring on %3 If the password is…


Part 7 : SCOM 2012 R2 HealthService Event Reference / HealthManager

HealthManager EventID=5101Severity=Error Message=Get the snapshot of current health states for selected instance failed with error: %7 %n%nInstance ID: %6 %nManagement Group ID: %5 EventID=5102Severity=Error Message=Get the state of the monitor failed with error: %8 %n%nMonitor ID: %7 %nInstance ID: %6 %nManagement Group ID: %5 EventID=5200Severity=Warning Message=One of the state change notification rules failed to process…


Part 6 : SCOM 2012 R2 HealthService Event Reference / ExecutionManager

ExecutionManager EventID=4000Severity=Error Message=A monitoring host is unresponsive or has crashed. The status code for the host failure was %1 EventID=4001Severity=Error Message=ESE failure trying to remove module state. The status code for the failure was %1 Source : Part 6 : SCOM 2012 R2 HealthService Event Reference / ExecutionManager  Cengiz KUSKAYA


Part 5 : SCOM 2012 R2 HealthService Event Reference / ConfigurationManager

ConfigurationManager EventID=1100Severity=Error Message=Property reference with id:”%5″ in workflow “%4”, running for instance “%3″ with id:”%2” cannot be resolved Workflow will not be loaded Management group “%1” EventID=1101Severity=Error Message=Host reference in workflow “%4”, running for instance “%3″ with id:”%2” cannot be resolved Workflow will not be loaded Management group “%1” EventID=1102Severity=Error Message=Rule/Monitor “%4” running for instance…


Part 4 : SCOM 2012 R2 HealthService Event Reference / ConnectorManager

ConnectorManager EventID=2000Severity=Error Message=The Management Group %1 failed to start The error message is %2(%3) A previous message with more detail may have been logged EventID=2001Severity=Error Message=No Management Group could be started See previous errors for more specific details If no errors are present, verify the machine has sufficient memory and has at least one Management…