Posts Tagged ‘SCOM’

Mapping your network

July 30, 2012 Leave a comment


SCOM 2012 has improved its manner of managing the network assets by introducing new features like the network node vicinity dashboard which allows you to map your network.

It’s so beautiful. However, to have real time information on the bandwidth for example, you have to consult another dashboard; the network interface dashboard.

At a given time, you can’t obtain the full view on your network.

Let us see SpiceWorks; a free tool, how it can present better the map;

As you can see, you can have a small popup showing real time information on a given device or on a link. That’s wonderful!

In a monitoring tool, the information access is so important. SCOM is powerful and allows you to monitor everything but it has some drawbacks in presenting the necessary data.

That could be included in future improvements.

Categories: MS Technologies, SCOM Tags: , ,

SCOM Agent Installation Failure

July 30, 2012 2 comments


If you are encountering this error “Product: System Center Operations Manager 2012 Agent — Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).” when installing SCOM agent on a target machine, so obviously you have a problem in the registry.

This can occur when the agent is uninstalled previously improperly or another WMI based program has corrupted the registry.

To verify the issue, try to launch PerfMon and add a given performance counter.

The solution is to rebuild the performance counters. the complete procedure is described here.

However, try first to use a recovery tool like CCleaner to fix the issue. In my case that has worked efficiently.

NB: Don’t forget to backup your registry before any operation.

Finding SCOM Objects from IDs

July 28, 2012 Leave a comment


In many cases, you have to troubleshoot SCOM problems by consulting the alerts and the event viewer for deeper information.

However, the objects are referenced by their GUIDs.

So how to retrieve their names?

The first manner to do it is by PowerShell. You have just to execute the following command:

Get-SCOMMonitoringObject -Id The-Requested-Guid.

The second manner is executing the following sql request (let’s suppose that the name of the SCOM database is OperationsManager and you are searching for agents names):

SELECT [NetworkName]
FROM [OperationsManager].[CS].[Agent]
WHERE [AgentGuid]=’The Guid’

Finally, here you are an example by an image:


Error when installing Reporting Server feature for your SCOM 2012

July 28, 2012 Leave a comment


If you intend to install Reporting Server feature for your SCOM 2012, and have configured your reporting server, you will have big chances to be welcomed by this error:

Don’t worry. You have just to consult your event viewer to get the explanation or simply, put your cursor on the red icon!

What’s the matter? It’s the SQL Agent which is sleeping in My machine. That’s the default configuration when you install SQL Server. This service is so crucial because it runs the planified report jobs. So you have just to wake it up! And to avoid future problems, set the startup type to Automatic.

Categories: MS Technologies, SCOM Tags: ,

“The Health Service cannot verify the future validity of the RunAs account” Error in SCOM

July 24, 2012 20 comments


If you are encountering this error in warning state, please check the change state of the monitor generating this error in the Health Explorer to get more details like the following description:

Date and Time: 9/7/2013 3:15:00 PM
Log Name: Operations Manager
Source: HealthService
Event Number: 7016
Level: 1
Logging Computer: Computer.DNS-Suffix
User: N/A
The Health Service cannot verify the future validity of the RunAs account “DOMAIN\Account” for management group “YOUR-MG” due to an error retrieving information from Active Directory (for Domain Accounts) or the local security authority (for Local Accounts). The error is 0x8000500D(0x8000500D).

Event Data:

< DataItem type =” System.XmlData ” time =” 2012-07-22T09:47:41.3597333-07:00 ” sourceHealthServiceId =” 70509BD2-367F-A3D4-C20D-AC0BEB4234C7 ” >
< EventData >
< Data > “DOMAIN” </ Data >
< Data > “Account” </ Data >
< Data > 0x8000500D </ Data >
< Data > 0x8000500D </ Data >
< Data > “MG” </ Data >
</ EventData >
</ DataItem >

Unfortunately, in the Knowledge Base of the Monitor, there is an obvious missing cause : Checking the state of your account in Active Directory. In some cases, this error is generated when the “Password never expires” is not defined.

In my case, it occurred for the domain administrator account which was defined as the default Run As Account in SCOM (It isn’t a good practice in SCOM; I know!). As the default GPO defines a maximum duration of the password life (45 days by default), “Password never expires” is not checked. To avoid the password expiration headaches, I set the maximum age of passwords to unlimited. But I forgot to check “Password never expires” option. For this reason, I got this error.

So check your account status or try to change it using another account. After that, Reset the Health of the monitor to see if it is fixed.

Categories: MS Technologies, SCOM Tags:

Deploying the System Center Operations Manager 2007 Linux Agent fails with “The certificate Common Name (CN) does not match”

December 24, 2011 Leave a comment

I have recently tried to install automatically the SCOM agent on a Red Hat 5 Server.

I have encountered the  “The certificate Common Name (CN) does not match” error during the deployment. The other error was about the issuer of the certificate which was not recognized by the Linux server.

You have to know that during the installation of the agent a certificate is generated from your RMS (Root Management Server) which is the issuer for your server in such way that the RMS can trust the messages sent by the SCOM agent.

To have an idea about the content of this certificate, please type this command :

openssl x509 -noout -in /etc/opt/microsoft/scx/ssl/scx.pem -subject -issuer -dates

You will have two information about the subject (your hostname server) and the issuer (the RMS).

Please check your hostname by using the HOSTNAME command. If you want to change it in such way that you add the DNS suffix for example (in this case you can add your A record in your DNS zone), you have to apply this :

Finally, to resolve the problem please check the following steps:

  1. You have to verify that your Linux server is reachable from your RMS server. So you have either to add an entry into the host file or to create a GlobalNames zone in your DNS (if you are running at least a 2008  forest). The problem with this solution is that your certificate will include “.globalnames” suffix. In this case, you have to modify your hostname. The best solution is the host file when the IP addresses are static.
  2. You can correct the certificate content by running the following command :  /opt/microsoft/scx/bin/tools/scxsslconfig -f -v. In my case, that could not be executed. So I had simply to remove the content (the certificates and the keys) of the /etc/opt/microsoft/scx/ssl/ directory and run the agent installation process again.
  3. If you have the issuer error, you have to check the DNS addresses of your Linux server and try to resolve the name of the issuer by using the nslookup or simply the ping tool. If you have a DNS problem, you have just to add the correct entry in the hosts file (/etc/hosts)
Categories: MS Technologies, SCOM Tags: , ,