Hi,
I've delpoyed a new SCOM 2012 Production and Preproduction Mgmt group, but am struggling to resolve some alerts which are probably key to getting a stable core platform.
The 3 main issues, which may or may not be related are to do with:
1. Run As Account does not exist on the target system or does not have enough permissions
2. Powershell script failed to run
3. operations Manager failed to start a process
I HAVE tried toubleshooting this myself and have read numerous posts but am not getting anywhere. Just to clarify i HAVE implemented the RunAs config as posted by Kevin Holman - I am also using Ver 6.4.1.0 of SQL MP. Our SQL dba has confimed access should work for Local system but just to be sure he has also set access for the SQL RunAs account which I have defined and pushed out in PreProd only - the RunAs account errors still come in regardless of the distribution of the account and 3 associated profiles.
Further info I have come across suggests that the autoclose option is a potential thing to check - I have checked and this is NOT the cause in my case. I've also read post suggesting that the agent resources may be overwhelmed and generate this alert - and could the possibly explain/link the other script failures. Ive also come across posts flagging continuing issues with the stolen server memory script being buggy since the previous version but still seems to persist in this lastest MP?
Basically I've followed all the troubleshooting - our SQL dba is convince the RunAs config permissions should NOT be generating alerts - the fact that it does and the majority of the Powershell script failures are SQL scripts - either timeouts and or relate to Stolen Server memory script is causing doubts of the monitoring info SCOM is giving esp around SQL
Any advice on trying to reslove the root causes of the 3 alerts would be much appreciated. Just to clarify, I have created and distributed RunAs Accounts/Profiles. I have alro tried increasing timeouts on some of the failing SQL collection rules/monitors.
Cheers