You are browsing the archive for KB.

Avatar of alkin

by alkin

Fix duplicate relationships for agents to server in Ops DB

9:34 am in Uncategorized by alkin

Sometimes it can happen that agents are ending up with multiple primary management server relationships. Of course you can only have one primary server relationship! In the rare occasions that you end up with multiple primary relationships you can now repair the issue by running the new “Fix duplicate relationships for agents to server in Ops DB” task manually


or there is a recovery on this monitor (disabled by default) that you can turn on so that the issue will be fixed automatically:




You will need the latest OpsMgr 2007 R2 management pack that you can find here

Alexandre Verkinderen

Avatar of alkin

by alkin

New KB for OpsMgr Management servers or assigned agents unexpectedly appear as unavailable in the Operations Manager console in Windows Server 2003 or Windows Server 2008

7:25 pm in Uncategorized by alkin

Microsoft just released a new hotfix to deal with ghost agents or agent that are grayed out for an unknown reason. Sometimes it can happen that an agent unexpectedly appear as unavailable without any real reason. We call this ghost agents

The workaround was to delete the health service state directory on the computer (root management server, management server, or agent) that is affected. That way the database will be rebuild.

But Microsoft has now identified this problem as this issue occurs because the database that is used by the health state is corrupted. This database corruption is caused by an issue in the storage engine of the jet database that is hosted on Windows. This is a problem in the Microsoft products and not in OpsMgr. So you need to apply the hotfix to fix the storage engine.

You can download the KB here 

Notice that this hotfix applies to Windows Server 2008 but not Windows Server 2008 R2.

Hope this helps,

Alexandre Verkinderen

Avatar of alkin

by alkin

Cumulative Update 2 for OpsMgr installation

12:28 pm in Uncategorized by alkin

High Level overview steps:

1. Root Management Server

2. Manual update of the Operations Manager database together with the included stored procedure file that is discussed later

3. Manual import of the Management Pack library that is discussed later

4. Secondary Management Servers

5. Gateway Servers

6. Deploy the agent update to the agents that used a discovery-based installation

7. Operations console role computers
Note Select the Run Server Update option from the Software Update dialog box.

8. Web Console server role computers

9. Audit Collection Services role computers

10. Apply the agent update to manually installed agents

Note To run this file on a computer that is running Windows Server 2008, you must use an elevated command prompt. An elevated command prompt is a command prompt that was started by using the Run as Administrator option. If you do not run this Windows-based installer file under an elevated command prompt, the System Center Operations Manager 2007 Software Update splash screen does not allow for the installation of the hotfix.

Download the corresponding CU2.MSI file and launch it:


The only thing you can do here is to accept the license agreement. Don’t forget to read it….



This is the installation folder where the files will be stored that we will need for the manual operations that must be performed after you update the RMS





It’s going to start and stop the opsmgr services. Don’t worry about it




Also don’t panic if you see event ID’s 29104. That’s normal during the upgrade process.


It can take a while but finally my RMS is updated


Just like with the CU1 I chose to not restart the server automatically. When you click no you allow the hotfix installation to finish all his post-processes. Check if the file versions has been updated and only then reboot the server.


I can see that the files have been updated


Manual operations that must be performed after you update the Root Management Server

Note You do not have to repeat the DiscoveryEntitySProcs.SQL installation if you have previously installed Cumulative Update 1 for System Center Operations Manager 2007 R2.

As in my environment I already applied the CU 1 I can skip this step.

Import updated management packs

This updated management pack is located in the ManagementPacks folder of the package installation.

Now you need to upgrade the other opsmgr components as well. I don’t have other MS servers in my lab environment so I’m going to skip this step.

Remember to upgrade one MS server at a time.


Last step is to approve the pending agents



Manually installed agents should be upgraded manually. Or you can easily create a SCCM package and deploy that.

If you have not already done so, create a new view that shows the agent patch list as described on Kevin Holmans blog:

That’s it!

Pretty easy upgrade

Alexandre Verkinderen

Avatar of alkin

by alkin

Community Day Session: Setting up & Configuring SQL Server to support your SCCM & SCOM environment

2:41 pm in Uncategorized by alkin

Kim Oppalfens and I did a session at community day together:

Setting up & Configuring SQL Server to support your SCCM & SCOM environment

System Center Configuration Manager and Operations Manager both need SQL Server. In this session we will show you what the best practices are for having a smooth running SQL server for our System Center environment. Having a good initial setup and configuration is not the only important thing, doing regular health checks on your SQL server is even more important. In this session we will discuss just about anything you need to know about setting up SQL from the SCOM or SCCM admin perspective. In this session you will learn how to work with the SQL team and set up your scom or sccm to talk with their standard SQL setup. This includes setups with remote sql servers, sql server services running as domain users, and named instances. Additionally we will talk about some SQL related configuration topics, like network libraries, firewall configuration, SQL collations, database recovery models and authentication modes.

At the end of this session you will know everything you need to know about SQL setup to support your scom or sccm environment.

Speaker: Kim Oppalfens & Alexandre Verkinderen


Slide Deck: 


CommunityDay 2009

CommunityDay 2009

CommunityDay 2009

See you next year!

Alexandre Verkinderen

Avatar of alkin

by alkin

Opsmgr Data Warehouse failed to enumerate database components to be deployed

9:04 am in Uncategorized by alkin

Today I ran into this issue:



Data Warehouse failed to enumerate database components to be deployed. Failed to enumerate Data Warehouse components for deployment. The operation will be retried. Exception ‘SqlException': Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component Instance name: Instance ID: {AC6FACD9-


Issue:This error appears immediately after a management pack is imported. The installaion of the reports in the MP is failing.

Resolution:Run exec sp_updatestats on the OperationsManagerDW db (the data warehouse).


When running the exec sp_updatestats doesn’t help follow these steps:


Download and extract the following hotfix:



Run the SQL query Managementpackinstall.sp.sql



And directly after running the query I got the following event:



Everything is fine now and I have green management server:




Hope this help,

Alexandre Verkinderen

Visit Us On TwitterVisit Us On Linkedin