Local system did not work but we did discover that the issue was security related. The account was from another domain that should have been trusted but for some reason was not working. We setup another account that was in the same domain as the ESI Service server with admin rights and everything in ESI was discovered in SCOM.
As far as the heartbeat message goes, EMC Support said the issue is a bug in version 3. When I asked about the heartbeat error, they responded "...on the SCOM RMS server, open up the System Center Operations Manager console => Authoring tab => click on Monitors => find the "EMC SI Service Connection" monitor and disable it. You need not be concerned that this will cause the monitoring of the health state of the ESI Service to be disabled, as the storage systems and their physical and logical components states will continue to be monitored."
We had a similar issue with the healthservice monitoring.
What we ended up doing is forcing the 'EMC SI Service Monitoring Account' run-as profile in SCOM to use 'localsystem' instead of the default SCOM action account.
MitchW1
5 Posts
0
September 13th, 2013 12:00
Local system did not work but we did discover that the issue was security related. The account was from another domain that should have been trusted but for some reason was not working. We setup another account that was in the same domain as the ESI Service server with admin rights and everything in ESI was discovered in SCOM.
As far as the heartbeat message goes, EMC Support said the issue is a bug in version 3. When I asked about the heartbeat error, they responded "...on the SCOM RMS server, open up the System Center Operations Manager console => Authoring tab => click on Monitors => find the "EMC SI Service Connection" monitor and disable it. You need not be concerned that this will cause the monitoring of the health state of the ESI Service to be disabled, as the storage systems and their physical and logical components states will continue to be monitored."
jemimus
25 Posts
0
September 6th, 2013 03:00
We had a similar issue with the healthservice monitoring.
What we ended up doing is forcing the 'EMC SI Service Monitoring Account' run-as profile in SCOM to use 'localsystem' instead of the default SCOM action account.