Hi Kevin,
Sorry. I guess I was not clear on my post. What you described is totally fine for us. And I can see that the property value and am able to create dynamic group using the attribute. ---- But I do not understand why changing 'target type' under Discovered Inventory would still show all monitored servers instead of showing servers where the property value is 'true'. Seems like it is including the ones where the property value is false.
Thanks again for your input.
Fahim
24 Apr 2014 6:42 PM
24 Apr 2014 6:46 PM
@Fahim - I understand exactly what you are asking. Which is why I explained that this example is using an unfiltered registry discovery. Discovered inventory shows instances of a class. This discovery is unfiltered, so it will contain a class instance for each computer that runs the discovery, regardless of the property value. That is by design. If you WANT a filtered discovery - then I'd recommend changing it to a filtered discovery provider and adding the required filter expression, where value = true. However, if you are going THAT far - stop extending Windows Computer altogether, and just create your OWN class based on the Local Application class and use a filtered reg discovery provider. I have several examples of this.
How far can SCOM bend
9 Sep 2014 1:13 PM
Hi Kevin,
Apologies for getting greedy on this but is there a way to get the Service Level details from a SQL Server table instead of registry entry? This will allow us managing service levels in a flexible and dynamic way. SQL server with these details is in a management
VLAN so only SCOM can talk to it. Any ideas how this can be done ?
Thanks for a lot of help on all topics. They have been a life saver.
9 Sep 2014 3:30 PM
DSloyer2015
6 Jan 2015 7:20 PM
Firstly, Kevin this is a great example and I have used it in the past, very thoroughly explained.
However, I am trying to create dynamic groups and a scoped roles based on an array of registry values. There was a request for something similar back in 2009 and you stated you may update this guide to include that example.
In our environment, we publish data to the registry at build time that captures the maintenance windows, support owner of the server, SLA, and other other company specific data. I'm collecting this data with SCOM and I'd like to automatically create groups
and possibly a role based on each Support group name. Is this something you've run into before?
6 Jan 2015 7:24 PM
@ DSloyer2015 -
Why can you just use groups, if you are already discovering this registry data in SCOM, and use dynamic expressions?