Tag Archives: scom2012

Reading out PS NoteProperty’s

6 Nov



How do i read out the IsManagementServer property on the example below ??

$X= Get-SCOMClass -Name “Microsoft.SystemCenter.ManagementServer” | Get-SCOMMonitoringObject

The output is:

[Microsoft.SystemCenter.HealthService].AuthenticationName : SRV.stateview.nl

[Microsoft.SystemCenter.HealthService].MaximumQueueSize : 104857600

[Microsoft.SystemCenter.HealthService].MaximumSizeOfAllTransferredFiles : (null)

[Microsoft.SystemCenter.HealthService].RequestCompression : True

[Microsoft.SystemCenter.HealthService].CreateListener : True

[Microsoft.SystemCenter.HealthService].Port : 5723

[Microsoft.SystemCenter.HealthService].IsRHS : True

[Microsoft.SystemCenter.HealthService].IsManagementServer : True


Now I want to get the IsManagementServer value


But it Fails


But it Fails

How do I read it out ??


Running the command below..

$x | GM

pointed out it was a noteproperty


So since its using [] i have to use ” to make a string of it

So the correct syntax would be


Happy Scomming

Michel Kamp

How To fix the 500 Error using Favorite Reports in the SCOM web console.

22 May

First mention this is a non official solution.

The Problem

You have installed SCOM 2012 Sp1 UR2 and have implemented the scom webconsole and reporting service to be running under HTTPS mode. You have created using the native scom console a favorite report and now when you try to open this favorite report in the scom webconsole you get a error 500.




To see the real error we have to do some web.config changes. So open the web.config file on this location: C:\Program Files\System Center 2012\Operations Manager\WebConsole\MonitoringView

Now we enable the SCOM error logging


And to get it displayed on the user page we do


Now when you run the favorite report again we get in the webconsole  the real error


Okay looks like the reportviewer web component binary dll can’t be found. Hmm but wait wasn’t this a prereq at installation time. So I checked if the 2010 ReportViewer components where installed and yes it was and the dlls where also spotted in the assembly cache. It looks like the webconsole has problems finding the correct version of the Microsoft.ReportViewer.WebForms.dll in the assembly cache.

The Quick non Official Solution

Copy the missing dlls to the correct directory will force the web runtime to first look in this directory for the dlls and then go to the assembly cache. So that’s what i did.

Copy the Microsoft.ReportViewer.WebForms.dll file from the assembly cache to path : C:\Program Files\System Center 2012\Operations Manager\WebConsole\MonitoringView\bin

Come on give me some script to do that ! Okay open PowerShell as admin and run

Copy-Item c:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.WebForms\*\*.dll “C:\Program Files\System Center 2012\Operations Manager\WebConsole\MonitoringView\bin”

And now you try to run the favorite report again in the webconsole …


… and Yes its working!

The End.

For me this looks  like a bug and I will address this to Microsoft.

Happy Scomming!

Michel Kamp

Discovery’s at your demand , yes sir!

27 Apr


This time a short post. But I think this could be useful  for SCOM admins.

The challenge.

We all know that one of the big powers of SCOM is the self maintaining of the monitor targets. SCOM uses discovery’s for this that run at regular intervals. Lets say you install a new SQL database instance on a server that has already a SCOM agent on it. Normally you have to wait for 4 hours before the new database instance is discovered. Yes you can speed this up to restart the SCOM agent but now we have a better way.


First, all the credits go to the SCOM product team it self’s. It seems the feature was already build in but making it globally known was somehow left behind. There is a agent task called ‘Trigger On Demand Discovery’ that can help you out. But how to operate this task can be painful.

The solution

I have written a PowerShell script that does the hard work for you. Running this script and supplying the correct Discovery and target will result in a instantly run of that discovery. So now you don’t have to wait for the discovery interval of 4 hours to trigger.

How it works:

1) You fill in the $OMserver with the SCOM SDK server FQDN.

2) You fill in the $discoveryname with the display name of the discovery rule you want to trigger. Just copy and paste the displayname from your author pane in the scom console. See picture below.


3) You fill in the $targetdisplayname with the name of the main target where this discovery should run. You can find this name by looking at the target from the discovery rule you got from step 2.


And fill this in the inventory view.


The name “servicemanager.systemcenter.local” is the target display name to use.

btw. of course you can use PowerShell to do this for you…

Below the script:

It triggers the discovery task and then waits for the results and displays it. Be sure to look at the output results property because it only is okay when it contains :


The script.

## =======================================================
## Trigger SCOM discovery for a discovery rule and target
## ======================================================
## Michel Kamp

Import-Module operationsmanager
## OM sdk server
## discovery display name
$discoveryname=”Service Manager Management Server Properties Discovery”
## target display name

## —————————————————-
## —————————————————-
# connect to OM server
$credentials = get-Credential
new-ScommanagementGroupConnection -Computer $Omserver -Credential $credentials

# get task to execute
$task=get-scomtask -name Microsoft.SystemCenter.TriggerOnDemandDiscovery
# make override params
$discovery=get-scomdiscovery -DisplayName $discoveryname
$TargetInstanceId= (Get-SCOMClass -Id   $discovery.target.id  | Get-SCOMClassInstance | ?{$_.displayname -eq $TargetDisplayName}).ID.Tostring()
$instance=get-scomclass -name Microsoft.SystemCenter.ManagementServer | get-scomclassinstance | ?{$_.displayname -eq $Omserver}
# run the task
$task_run=start-scomtask -task $task -instance $instance -override $override

# wait for result
while ( (get-SCOMTask -Id $task_run.TaskId).Status -eq “Started” )
    write-Output “Waiting…”
    Sleep -Seconds 2
# show task output
get-SCOMTaskResult -BatchID $task_run.BatchId

## —————————————————-
## end script
## —————————————————-

The End.

I already did some more investigation on this topic because I think when you can do it for a discovery you can also do it for every workflow that contains a timed interval trigger module. Can you imagine that you can now trigger every rule or monitor at your demand… so cool and so handy while debugging.  When I have it working I will of course share it with you “the community”.


Michel Kamp

SC 2012 SP1 UR2

12 Apr


Hi ,

It isn’t any new news , since I twitted also 2 days ago the UR2 release of System Center 2012 SP1 is released.  ( http://support.microsoft.com/kb/2802159 )

As I write now not all software download links are working jet. So don’t get frustrated as I did…

For Installation experience see here for again an excellent post from Kevin Holman:


O wait what’s missing ?:

If you read the release notes you will notice that it mentions patching the Gateways but if you look at the software downloads you won’t see any gateway patch.

I don’t know if the gateway patch is simply forgotten to publish but if you have a environment that uses a gateway you will be stuck for now… because your agents behind the gateway will not be patched using the pending actions in SCOM.

Or not…

The solution is however not far away.
1) Just copy the Agents msp binarys to the agent management directory on the GW servers.

Path : C:\Program Files\System Center Operations Manager\Gateway\AgentManagement


1) So copy file KB2826664-AMD64-Agent.msp to

C:\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64

2) copy file KB2826664-AMD64-Server.msp to

C:\Program Files\System Center Operations Manager\Gateway\AgentManagement\x86

And at last the KB2826664-ia64-Agent.msp file to the ia64 directory.

3) approve the pending actions in your scom console. And you will see the agents behind your GW will be patched.

The end

Hope Microsoft will clear this confusion soon. Because I can’t imagine that the GW it self’s doesn’t have any fixes…

Happy scomming


Aggrr missis SCOM sometimes you drive me nuts!

12 Mar

Here we are again. I am for sure you will remember a situation where you were sure everything was configured correctly and you even had restarted the server but still it doesn’t work…… NO ??

Okay so this time it was my turn…

The problem:

I was trying to discover a new network device. Network discovery won’t find my newly added network device. Why ? I checked everything and it isn’t connectivity or security. Normally when those issue apply you will see a pending failure discovery attempt. What could be wrong..


1) First I checked the discovery rule. The network devices are explicit specified.


I made sure the device was listed in the explicit discovery.


2) I started the discovery and checked the progress events.


Hey what’s that ! One device excluded ?? Strange this option can only be applied to recursive discovery’s….

So it must be something in the discovery rule….

The solution:

So this excluded event triggered my attention.

1) open the discovery rule.  And change the Discovery method to Recursive discovery


2) Now select the Exclude Filters tab


And what do we see here . The network device I was trying to discover.

3) Now remove this exclude filter entry and save the discovery template without RUNNING IT


4) Reopen the discovery rule and change the discovery mode back to ‘explicit’ and save it again.


5) now run the discovery.

6) and what do we see here … the device is discovered successfully !



It looks like this rule was initially created in recursive discovery mode. After a while the operator decided to remove a device from the discovered device inventory. If you do that a exclude filter entry is automatically created. At the end the operator decided to change the discovery mode back to explicit (don’t ask why) and that’s causing the problem I faced…

The end

Hope I saved you a lot of time almost hating misses SCOM ; – )


Michel Kamp MVP System Center Operations Manager

Hey SCOM Agent just install your self , please !

11 Feb


The last time I notice more and more SCOM 2012 Agent installation fails. Where the SCOM 2007 agent installs fine the SCOM 2012 agent has troubles.

There are plenty of guides on the web but none fixed my problem.

1. Problem:

During the SCOM 2012  agent install (push or manual) the install fails with error 25211 Failed to install performance counters. Error Code: -2147024809


2. Analyze

When looking at the deployment log (search for value 3) I noticed that the component failing was the APM module. Secondly it has something to do with registering performance counters. ; – )

3. Solution

When you look on the web you will find as a possible solution KB2554336. Following this article you are rebuilding your performance counters. At my case this rebuild was successful but the agent install still failed. So …

My analyze concluded the setup stopped at the APM module. So why ‘not’ install this module ? I know the server where I am going to install the agent never is going to use this module. How do we do this ? You can do this by supplying the parameter: NOAPM=1

1) On the failed sever open CMD as admin.

2) Copy the agent install files to this server.

3) start the install with :

msiexe /i momagent.msi NOAPM=1

You will notice the installation was successful!!

4. The end

Finally you can use the ops hack in scom db to set this agent from manual to pushed install so it will be patched also.

Happy Scomming,

Michel Kamp

Authoring SCOM Reports in VS 2010

14 Jan


Short post on how to get you dev environment ready for authoring scom reports.


You have installed SCOM 2012 on SQL 2008. You want to author a custom report using Visual studio 2010. When you open visual studio you will notice that NO BI project template is shown. Normally you selected this project template and selected the new report project to make your custom report. How now to continue ?


Grab a SQL 2012 ISO (YES 2012) and startup the setup.

1) Select installation:


2) New sql or add features


3) Select SQL features Install


4) Now the important step. Select the 3 options here. Most important is the “SQL Server Data Tools”. This features contains the VS BI project template.


5) Step though the install windows.

And now open Visual studio 2010 and create a new project. And what do we see ?

Yes the BI template Knipogende emoticon 



Now you can create the new SCOM reports. Notice also the NEW chart types !!!



Remember that if you use custom report code components you must copy the correct .dll assemble to the directory:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies

The End.

Happy Scomming

Michel Kamp