Rule detecting that a given HealthService cannot use the RunAs Account. This could be the result of a corrupt action account or expired action account.
This rule is used internally by OpsMgr. Overrides to this rule will cause behavior that may not be what you expect.
This section is not applicable to this rule.
There is no resolution to perform for this rule since it does not generate state or alerts.
Target | Microsoft.SystemCenter.HealthServiceWatchersGroup |
Category | System |
Enabled | True |
Alert Generate | False |
Remotable | True |
Comment | HealthService Action Account configured |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.SystemCenter.HealthServiceWatcher.Composite.OnDemand.DataSource | Default |
WriteAction | WriteAction | Microsoft.SystemCenter.HealthServiceWatcher.SetActionAccountConfiguredStateAction.Error | Default |
<Rule ID="Microsoft.SystemCenter.HealthService.ActionAccountConfigured.OnDemand.Error" Comment="HealthService Action Account configured" Enabled="true" Target="SCLibrary!Microsoft.SystemCenter.HealthServiceWatchersGroup" ConfirmDelivery="true" Remotable="true" Priority="High" DiscardLevel="100">
<Category>System</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.SystemCenter.HealthServiceWatcher.Composite.OnDemand.DataSource">
<MonitorId>$MPElement[Name="Microsoft.SystemCenter.HealthService.ActionAccountConfigured"]$</MonitorId>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteAction" TypeID="Microsoft.SystemCenter.HealthServiceWatcher.SetActionAccountConfiguredStateAction.Error"/>
</WriteActions>
</Rule>