In Part 1 of this blog series we opened up Wbemtest and subscribed to advertisements being created that did not have “MassDeployment” in its comment field.
In this part we’ll look at what the subscription shows us when an advertisement is actually created.
Below is the screen you’ll seen when waiting for the event being triggered.
The screen will display the below when an advertisement is actually created.
As you can see an event has now been triggered, you can double click the __instanceCreationEvent=<no key> entry to open the event data.
If you check the “Hide system properties” checkbox than you’ll see the following screen.
The most interesting part is that each instancecreationevent has an embedded object called TargetInstance. This is a representation of the WMI object SMS_Advertisement that has just been created, and here comes the interesting part, if you double click on TargetInstance and click “View Embedded” than you can actually see all details of this newly created object. This single fact makes WMI eventing hugely interesting.
In my next posting I’ll explain how you can use WMI eventing from something slightly more flexible as Wbemtest.