Archive | June, 2015

Backstage ticket to OMS: Setting up the debug environment

26 Jun

Hi since OMS (Microsoft Operations Management Suite) is a new product on the market it is always a challenge to see how the internals are working. So I was planning to take you on an OMS backstage trip.
I will post a couple of blog post explaining how OMS works and how I figured it out.

This first post will be all about how to setup your debug environment, with this you can see what data is transferred and is a good starting point of see what’s going on. Since OMS uses HTTPS we have to do some more than a normal http trace.

Here we go. I assume you are not a real rookie DEVOPS so I won’t explain every step in detail. 😉

  1. Setup your OMS connection on your SCOM management group and enable the log collection.
  2. Watch if you see any events in the OMS event dashboard. If this is true then you can continue. If not first fix this.
  3. Install fiddler on your management server (for debugging I always use only 1 MS , so I know where it runs)
    1. Configure fidller proxy to 8888


    2. Enable https decription



    3. Copy the DO_NOT_TRUST_FiddlerRoot cert from user ssl to computer ssl store:



    1. Copy the DO_NOT_TRUST_FiddlerRoot root cert to the computer trusted ca



    1. Set OMS insight to proxy hjttp://localhost:8888



    1. Watch the sessions. Now if you see a session like below “PostDataItems” you click on it (1).

      Now you press on the inspectors (2) and headers (3). A message asking you to decode (yellow part) will popup (4) . And you do this.



    After the decode step you get the message request body , open the XML tab (1) and you see the request body send (2)



    And now you can continue to see what is transferred and received. In this case the data that is transferred to OMS is in the DataItem element.


    So far part 1. In the next part I will show you how to read data back from OMS


    Happy SCOMMING

    Michel Kamp