How to Remove Management Pack Dependencies
When you create an override and don’t save it to a custom Management Pack it will by default save to the Microsoft.SystemCenter.OperationsManager.DefaultUser.xml management pack. This will later on bite you in the ass when you want to remove the effected management pack. To avoid this of coarse you should always save changes to a custom management pack…..
< !-smartads->
ASP.net causes reporting services and prerequisite to fail
It appears that if IIS is installed before ASP then there are possible challenges with either the initial install of OpsMgr and/or the setup of reporting services. I have had two occasions where this has happened. In both cases I performed the exact same fix to resolve this.
Promoting MS to RMS : USE WITH CAUTION!!
If you haven’t had the pleasure of testing the promotion of a management server (MS) to be a root management server (RMS) and then back again in the event of a RMS failure then this is a must read.
After I implementing Microsoft’s System Center Operation’s Manager 2007 (SCOM) into our environment I wanted to test the disaster recovery process. Our design is using an RMS and one MS. The test was meant to be simple and I of course didn’t think to create another test environment for this. *what an idiot*
< !-smartads->
To prove that the steps provided by Microsoft worked I unplugged the RMS and prompted the MS server. Hey this worked like a charm. It was the next step that really got ugly, the next step of course was when I brought the RMS back on-line. Because that is the goal in the end right. To restore the original server. Somewhere I missed a step. And before you know it I was rebuilding the entire environment. I was fairly sure that I hadn’t really missed anything. But I screw up so often who really knows for sure? I then created that test environment that ignored the first time and tried it again. Hey what do you know I had the same results. Then for the third test I opened up a Microsoft support call and had them help me do it right, and again the same results. The Microsoft support tech confessed to me that in there training they only test the promotion . They didn’t actually try to go back to the original solid state.
After a couple of days he for-wards me an internal email from Microsoft that talks about the process and how to avoid this issue.
Read on to see the risk assessment and the detailed steps of how to demote and promote
WMI issues that prevent SCOM Agent install
During the initial install of the agents on the servers I ran across a hand full of failed agent installs. Nothing worked. Couldn’t push the install, and when I tried a manual install on the client it would fail halfway through with errors related to mof files.
< !-smartads->
Read more
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