Actually I was looking for some other things in SCOM 2012 R2 as I suddenly noticed some interesting naming convention of the SCOM services… Until SCOM 2012 Sp1 the Windows services on the management server were named like this… In SCOM 2012 R2 the Windows services on the management server are named like this…
I experienced in a relatively small environment that the Discovery Wizard in SCOM 2012 is running forever. I rejected some pending agents which were discovered properly but stayed in a “Installation in progress” state. After I rejected these agents and wanted to re-discover these servers the Discovery Wizard kept runnig forever.
Today I needed a solution which I could trigger a runbook using Powershell only. I found a very flexible and extendable solution on Codeplex.