Archive for SCOM – Installation

How to test a remote connection to SQL Instance

It is very easy

1. Create a simple txt file and change the extention to .udl
2. Double-click on the file and up pops a SQL connectivity window to allow testing of remote SQL connections

SCOM 2012 R2 – Web Console installation on Server 2008 R2 – Server Error

I got a issue yesterday when I have to install the web console on Windows Server 2008 R2. After some research I found a solution.

My error message at the web page:

The Solution:

Thanks to Kevin Holman I found a solution for this issue. So please visit below blog and say thanks.

Run below command:

On Server 2008 R2 – run the following in an elevated CMD:  C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -i -enable

On Server 2012 – run the following in an elevated CMD:  C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -r

For more info please go Link


Installing Operations Manager by Using the Command Line

One of my collegue forward this very usefull link from MS. Where all of the option are listed.

One of the option I have look is the ‘/AcceptEndUserLicenseAgreement’, because    deployment has failed. Because the /AcceptEndUserLicenseAgreement was not set to 1.

Read more

OpsMgr 2007 R2 – Re-install Reporing Service

If you ever have to move or re-install Reporting Service, then you will find some very usefull link here.

Read more

SolarWinds Management Pack for System Center Operations Manager 2012

Very nice blog regarding SolarWinds integration to OpsMgrt 2012


Read more

Error “The gateway name already exists as a computer instance.”

I ran into a situation where I could not get a gateway server to approve via the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe. It was erroring out saying that “The gateway name already exists as a computer instance.”.
I am getting Event ID 20000 on the Management Server and Event IDs 20070 and 21016 on the gateway.
You will need to remove the computer name from the Agent Manged list. The supported method of doing this is to delete from the admin console(Administration > Device Manager > Agent Managed). But in some case you can’t find it in the console. If it is the case you need go the database for Ops Mgr, find the tabel called dbo.MT_Computer and open it. Find PrincipalName where it match and delete the row

Event 5206 – Warning In memory container

I saw this error after that we have add 50 more vmware host for monitoring on the nworks server.
If get below message in event viewer.
Event Type: Warning
Event Source: HealthService
Event Category: Health Service
Event ID: 5206
Date: 7/22/2009
Time: 9:41:18 AM
User: N/A
Computer: I00354
In memory container (single list System.Health.AlertUpdateData) had to drop data because it reached max limit. Possible data loss.
For more information, see Help and Support Center at
I did some research and found that the default for this container is 1024. This can be configured through the following DWORD value:
HKLM\System\CurrentControlSet\Services\HealthService\Parameters:”State Queue Items”
I recommended that you set this to 2048 and if the errors continue to recur then try doubling it again. There my be some other underlying issues that cause this queue to fill up so this my need to be troubleshot further if errors continue after this value has been raised significantly.
  • For the following registry key, create a new DWORD named State Queue Items, and then set the value as decimal 2048:


Nworks server using 100% CPU

If just have installed a new nworks Collector server. And after short you can monitoringhost.exe using 100% cpu. Then you need to check that Version Store Size for the Ops Mgr Agent has been configurated for Large Environments(more that 25 vmware host’s).
See how to in the MP_VMware_OM07_Admin_Guide_E4.5.pdf
See page 137-140.