Archive | January, 2012

Phone 7 SCOM console reached the 256 downloads

5 Jan

Begin 2011 I published the first and only Native SCOM console for the Phone 7 platform. However I never received any suggestions or problem reports I see the app is still downloaded and used.

See APP HUB download graph below.



Call out for anyone using this app ! Please let me know what you like or don’t like using this app !!

Download link for the SCOM console Phone 7:

Detailed configuration info :



Debugging SCOM web applications

5 Jan


Today I will share one of the greatest tools on earth with you !

It is named : FIDDLER

All the credits are going to the the author :

This tool will help you debug all sorts of HTTP(s) traffic. Maybe you think now “but what has this to do with SCOM ?”

The answer is : A lot when you are working with the SCOM web application monitoring. If you have setup/recorded a web application to monitor and are going to use the parameter extraction and insertion you are in the blind with debugging. You will never know if the parameter extraction was successful. Till now!

Of course you could try to do retry on error runs using the Run Test in the Web Application Editor by enabling all content collection and compare the output in the result windows. (pfff) Or do the bare level hardcore authoring stuff (where I am home at) by exporting the MP and use the Workflow simulator or the Workflow analyzer to get the trace, or real hardcore use the healthservice module tracing for it. But this is really time consuming and not necessary for the Web Applications because I know the Web application monitoring workflows are working okay but the Parameter extraction isn’t. And since this is a functional http response problem I use a simple HTTP trace program for it named FIDDLER.

So I will show you how to use FIDDLER to get the wanted web application debug trace in a couple of simple steps:

1. Download FIDDLER from  :

2. Install Fiddler on your developer box

3. Disable the firewall on our dev box (I m sure you have all ready done this Knipogende emoticon)

4. Configure the web proxy setting for FIDDLER

Go to Tools > Fiddler options



Enable the remote connections and notice the port number:



5. Restart Fiddler. Important step!

6. Now we are almost there….

7. Open in SCOM the recorded Web Application



8. Open the “Configure Settings” and enable the Web proxy , fill in the IP and port of your Dev box.



9. Now go you Dev box and start up Fiddler and enable the capturing


10. Just wait till the Web Application monitoring is triggered. And you will see …..



And this is it. Now you select the correct Http capture’s and investigate the POST / GET inspector to see if the parameter insertion was correct and you can investigate the request results to see if the parameter extraction was setup okay.



Some tips:

[1] If you don’t want to wait till the next wen check run. Just press the “Run Test” in the Web application editor.


[2] Be aware when using this on-instant run test all MPelement references (example a runas profile element) will not work. So you must replace it by default values.

Or you will be hit by this error:


[3] To minimize the capture output to only the proxy http data only select “All processes”


[4] Best way to look for the parameters is selecting the Webforms tab in the inspectors tab.




Hope this will help you too!


Happy SCOM’ing!

Michel Kamp