Monthly Archives: February 2013
I am a strong believer in not using AD integration any more. I think the management of the agents long term and in a DR situation is easier with a little planing. Durring an upgrade to SCOM SP1 I ran into an … Continue reading
Since my original post on issues with the SCCM agent and WMF 3.0. We have only uninstalled the WMF 3.0 update on systems that created major issues or have documented compatibility issues. I have found the WMI queries don’t report SQL Server data correctly. … Continue reading
In this blog post I will show you how to clean up the registry if you get the following error. 22:26:25]: Always: :Operations Manager Agent is also installed on the machine. Since we are upgrading Server we will remove Agent … Continue reading
In this blog post I am going to cover the new command line property I found for installing the SCOM agent via command line with the SCOM SP1 Agent. The following TechNet article covers the documented switches for installing MOMagent.msi … Continue reading
If you are upgrading SCOM 2012 to SP1 I strongly suggest reviewing this post from the SCOM Engineering Blog http://blogs.technet.com/b/momteam/archive/2013/01/16/patience-is-a-virtue-with-the-system-center-2012-operations-manager-sp1-installation.aspx most importantly check that your SQL settings are correct before starting. another important note if the Management Server upgrade fails it … Continue reading
If you have deployed System Center Advisor to your SCOM Management Servers, you need to remove it before upgrading SCOM 2012 to SCOM 2012 SP1.
In preparing for the upgrade to SP1 for SCOM I decided to finally put in some alerting and simi-auto resolution to the settings for Veeam KB1036 that needs the SCOM agent reconfigured after every patch to the SCOM agent. Issue: … Continue reading