I've just started an SCOM 2012 R2 deployment to monitor a multi-tenant SCVMM deployment I just did and I'm running into no end of problems. In an effort to avoid cascading error issues, I figured I'd try and resolve the warnings (in the Monitoring -> Windows Computers view). However, after four days I have made ZERO progress, and gotten very frustrated.
Using the Health Explorer for the three systems with warnings, it appears the root problem is the "Run As account" cannot logon locally. Unfortunately, I have had minimal luck in identifying the account. I thought I had, but have not been able to repeat the steps to identify the account. One of the three systems is a domain controller, and the other two are pretty much "normal" WS2012R2 deployments. The other 30+ systems report no issues (Healthy/success/etc.)
The account I saw identified in one time I was able to see an account name I added to the GPO to "Allow log on locally" (using GPMC) without any success.
So I'm wondering if I'm just being incredibly thick, or if it really is this difficult to figure out what is really going on using the Operations Manager Console.
One issue I've had is there does not seem to be any way to have SCOM refresh *everything* from the current state of affairs. In many cases the suggestion is to "delete" what ever and then wait several days for SCOM to flush the information. With all the problems I'm having and trying to resolve by trying different things, it may be next century before I get everything working if I have to continually wait long periods of time.
I've tried many of the recommendations made on various sites (Microsoft and others) without success.
Might anyone be able to point me in the right direction?
Thanks in advance.
- Mark