ConfigurationManager
The System Center Management Configuration service is an external service to the HealthService. This service is responsible for pulling the latest configuration from the database at the request of the ConfigurationManager feature. ConfigurationManager uses a cookie that represents a delta hash between any types of configuration that might change, such as management packs, relationships, run-as profiles and accounts, and so on. This helps ConfigurationManager to request changes (updates) for the configuration from just the System Center Management Configuration instead of always requesting the full configuration.
The configuration is in the form of an XML file that is located under \Health Service State\Connector Configuration Cache\ \OpsMgrConnector.Config.xml, where is the name of the Operations Manager Management Group (there can be multiple in multi-homed environments). This XML file holds information about the local HealthService, such as its name, parent HealthService (if any), a list of fail-over HealthServices (if any), list of Resource Pools it is part of (if any), the list of management packs, the list of instances it manages locally (for example, logical disk instances it discovers locally), and a blob that contains an encrypted hash that holds information related to the user accounts it needs to load locally to run different workflows.
After ConfigurationManager processes the XML, it requests any new management packs. These are also available in XML format in the \Health Service State\Management Packs folder. Either on startup or on configuration update, ConfigurationManager loads all workflows from all management packs, like discovery rules, monitors, and every other workflow that should run locally depending on their target classes and what instances of these classes are locally managed by this HealthService. After loading the workflows, ConfigurationManager passes them to PersistenceManager, which writes the workflows to the local ESE database and passes them to ExecutionManager, which starts running the workflows and notifies HealthManager of any monitors that it needs to manage.
EventID=1100
Severity=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=1101
Severity=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=1102
Severity=Error Message=Rule/Monitor “%4” running for instance “%3″ with id:”%2” cannot be initialized and will not be loaded Management group “%1”
EventID=1103
Severity=Warning Message=Summary: %2 rule(s)/monitor(s) failed and got unloaded, %3 of them reached the failure limit that prevents automatic reload Management group “%1” This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s)
EventID=1104
Severity=Error Message=RunAs profile in workflow “%4”, running for instance “%3″ with id:”%2” cannot be resolved Workflow will not be loaded Management group “%1”
EventID=1105
Severity=Error Message=Type mismatch for RunAs profile in workflow “%4”, running for instance “%3″ with id:”%2” Workflow will not be loaded Management group “%1”
EventID=1106
Severity=Error Message=Cannot access plain text RunAs profile in workflow “%4”, running for instance “%3″ with id:”%2” Workflow will not be loaded Management group “%1”
EventID=1108
Severity=Error Message=An Account specified in the Run As Profile “%7” cannot be resolved Specifically, the account is used in the Secure Reference Override “%6” %n%nThis condition may have occurred because the Account is not configured to be distributed to this computer To resolve this problem, you need to open the Run As Profile specified below, locate the Account entry as specified by its SSID, and either choose to distribute the Account to this computer if appropriate, or change the setting in the Profile so that the target object does not use the specified Account %n%nManagement Group: %1 %nRun As Profile: %7 %nSecureReferenceOverride name: %6 %nSecureReferenceOverride ID: %4 %nObject name: %3 %nObject ID: %2 %nAccount SSID: %5
EventID=1109
Severity=Informational Message=All credential references resolved successfully %n%n %n%nManagement Group: %1
EventID=1200
Severity=Informational Message=New Management Pack(s) requested Management group “%1″, configuration id:”%2″
EventID=1201
Severity=Informational Message=New Management Pack with id:”%1″, version:”%2″ received
EventID=1202
Severity=Warning Message=New Management Pack with id:”%1″, version:”%2″ conflicts with cached Management Pack Condition indicates wrong server configuration
EventID=1203
Severity=Warning Message=Management Pack with id:”%1″, version:”%2” has been changed locally Management Pack cache file will be deleted and re-requested from server
EventID=1204
Severity=Informational Message=Management Pack with id:”%1″, version:”%2″ is no longer used by HealthService and will be deleted from cache
EventID=1205
Severity=Informational Message=Configuration reload request received Configuration for management group “%1” will be reloaded
EventID=1206
Severity=Error Message=Rule/Monitor “%2”, running for instance “%3″ with id:”%4” failed, got unloaded and reached the failure limit that prevents automatic reload Management group “%1”
EventID=1207
Severity=Warning Message=Rule/Monitor “%4” running for remote instance “%3″ with id:”%2” will be disabled as it is not remotable Management group “%1″
EventID=1208
Severity=Warning Message=Ignoring file %1 as it is not a Management Pack EventID=1209 Severity=Error Message=Management Pack with id:”%1″, version:”%2” has been requested “%3” times Management group “%4”
EventID=1210
Severity=Informational Message=New configuration became active Management group “%1″, configuration id:”%2”
EventID=1215
Severity=Informational Message=Suspending monitoring for instance “%3″ with id:”%2” as the instance maintenance mode is ON Management group “%1”
EventID=1216
Severity=Informational Message=Resuming monitoring for instance “%3″ with id:”%2” as the instance maintenance mode is OFF Management group “%1”
EventID=1217
Severity=Informational Message=The Microsoft Monitoring Agent running on computer “%1″ is suspended for the following reason:%n”%2”
EventID=1220
Severity=Error Message=Received configuration cannot be processed Management group “%1” The error is %2(%3)
EventID=1221
Severity=Informational Message=Received configuration successfully processed after failure(s) Management group “%1”
EventID=1230
Severity=Error Message=New configuration cannot be loaded, the error is %2(%3) Management group “%1”
EventID=1231
Severity=Informational Message=New configuration successfully loaded after failure(s) Management group “%1”
EventID=1232
Severity=Warning Message=Could not resolve override “%2” for workflow “%3” because the forbidden “$RunAs” token was found in the override value Management group “%1”