RunAs Successful Logon Check Monitor

  • ID:  Microsoft.SystemCenter.HealthServiceRunAsAccounts.SuccessfulLogonCheck.Unit
  • Description:  This monitor checks if a Run As account can successfully log on with the configured username and password.
  • Target:  Health Service
  • Enabled:  Yes

Operational States

Name State Description
Account(s) Failed To Log On Error  
Accounts Successfully Logged On Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Account(s) Failed To Log On (Error) RunAs Successful Logon Check Failed Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The Health Service could not log on the specified RunAs account. This will prevent the health service from monitoring or performing actions using this RunAs account

Below is a summary of the default configuration of this monitor:

  • Red state: Transition to red state if the health service could not log on the specified RunAs account (event 7000)

  • Green state: Transition to green state if the health service successfully logged on all RunAs accounts (7024) or if the connector manager is successfully started for the management group (event 2002)

Causes

The red state can indicate the following may be happening on the agent:

The Health Service could not log on the specified RunAs account. This will prevent the health service from monitoring or performing actions using this RunAs account.

  • The password entered for the RunAs Account may be incorrect

  • The account or its password may have expired

Resolutions

You can perform the following steps to resolve the problem or to gather data prior to seeking assistance from Microsoft product support:

The password entered for the RunAs Account may be incorrect. Re-enter the password by

Open the Operations Console

Go to the Administration space

Select the Run As Account node on the left pane

Find the specified RunAs Account and open its properties

Select the Account tab and re-enter the correct password

  • Extend the account (or update its password) in Active Directory (for domain accounts) or on the local computer (for local accounts)

  • Capture all 7### events, save the Operations Manager event log on the agent computer and call Microsoft product support. During the support call, mention the most recent 7### events and any error codes (e.g. event 7022) inside the event and ask if the Operations Manager event log is needed.

External References
This monitor does not contain any external references.

See Also for System Center Library Management Pack


Downloads for System Center Library Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED