Some further information this seems to be limited to the following types of objects:
- ASP.NET Application
- IIS WAS Service Application Pool
- IIS WWW Service Site
Any help on how to prevent these from resetting would be much appreciated
Seem to have figured this out with a lot of research and testing.
This isn't really a fix for the original issue which is that the server name is not appended to the object name which seems to be a limitation in the IIS management pack.
I then found a way to get the objects to be applied to dynamic custom group and create new symptoms and alert definitions in order to have the alerts indicated the problem server, these are detailed below:
Dynamic custom groups:
this was simple and just required me to apply the relationship| descendant of criteria which allowed the dynamic group to include all the relevant services.
For this i created a new symptom for each service and a new alert definition based on the "Virtual machine" object.
refer to this post for me detail which was very helpful: EP Ops Windows service monitoring
I hope this is helpful for someone in the future