Setting up the EMC SI Run As profiles

Setting up the ESI SI Monitoring Account

For the EMC SI Monitoring Account Run As profile, create and set up the Run As profile for each SCOM agent that needs to connect to each ESI Service.

To set up the EMC SI Monitoring Account Run As profile for each SCOM agent that is using Windows Authentication to connect to each ESI Service:

  1. Create a Windows Run As Account for the Windows account that is used in the Monitoring Role for the ESI Service.

  2. In the EMC SI Monitoring Account, assign the Windows Run As Account to the related SCOM agent that will connect to the ESI Service.

 

Setting up the EMC SI Service Monitoring Account

Set up an EMC SI Service (ESI Service) Monitoring Account Run As profile to monitor the EMC SI Windows Service.

If your SCOM environment uses a Default Action Account that is a local administrator, then the action account has the necessary settings. However, if your SCOM environment uses a low privilege account as the Default Action Account, you may need to use a special account to monitor the service. If you do, then work with a SCOM administrator to create the Run As account. You may also need to create a Windows account to monitor the service.

The SCOM account that monitors the ESI Service must have the Allow log on locally enabled, be able to read the Application Event log, and use WMI (Windows Management Instrumentation) to query the status of the service.

 

Related links

 

 Setting up optional management pack overrides

 ESI overview

 Confirming connection between SCOM agents and ESI Service

 Home window

 Setting up the SCOM agent registry

 

 Setting up ESI Service discovery overrides