Great script. Super time saver. Incredible.
This script has really save me a ton of time. Thank you, Thank you, Thank you! :-D
Can anyone give me the download link for this script.
I'm not really sure you want this script. A different monitor set created for each and every server endpoint? Great googly moogly. It's a remarkable feat of programming but it isn't the most efficient use of one's time I've ever seen, never mind the damage it does to the scroll bar in your Monitor Set edit list.... let alone the picker when you're going to apply the thing.
So, what do we do here at Resource One?
I have a procedure that gets run once per week. This procedure checks the "automatic" status of a number of key services: DNS. DHCP. IIS. And so on. Each one found to be in the "automatic" state gets a YES flag in a Custom Field created for this purpose. At that point it's a piece of cake to setup Views that can be used in Policy Management so that anything with a YES for, let's say, the "Serves DNS" custom field gets the DNS services monitor set.
It does mean adding all the services you care about to the checks in the procedure and you need custom fields for all of them. Your mileage may vary on this approach. We keep this sort of thing on a short leash, and also use things like an Exchange 2010 group-of-services monitor set applied via a view populated by a script that checks which (if any) version of Exchange is installed on a server. That way one check script applies one monitor set to keep watch on a bunch of services, and it's all done automatically via Policy Management.
And that's my couple of pennies' worth.