SCOM: I screwed up the OpsMgr Health Service
Have you ever seen this in Microsfts System Center Operations Manager (SCOM)?
The OpsMgr Connector could not connect to MSOMHSvc\rms01.local
haha, I have.
Using a domain account is not supported and will not allow you to start the service. But it will register a second servicePrincipalName to the domain account. If this happens the agents will no longer be able to communicate with the server. Or at least until the duplicate servicePrincipalName is removed.
I found this out during the test phase when I changed the service login account during trouble shooting the health service. (The original problem with the health service was that it would keep failing and stopping. The resolution was never found, and that was with an open Microsoft call. We reinstalled the server and that resolved it. However the servicePrincipalName was still messed up in active directory.)
The following is what I have documented and used to fix this.
< !-smartads->
Read more