SQL Integration MP Discovers Duplicate Integration Services
The 2014 and 2016 SQL Integration packs have "Discover SQL Server 2014 DB Installation Source (seed)" discoveries that are targeted toward the "Windows Server" class. In environments where SSIS may be installed on SQL Clusters (and SCOM has the clustering MPs imported), this can lead to duplicate instances of the Integration services being discovered. Because clustered resource "servers" are also populated into the "Windows Server" class, they too discover SSIS instances. In one example here, one cluster that only has two base nodes had five different SSIS instances discovered, when only the base nodes should be discovered. I had to create groups populated with "Windows Server" objects with the "Is Virtual Node" property set to "True", and override the discoveries using these groups. I realize that the MP can't be written assuming the cluster MPs are present in the environment, but perhaps an Optional MP could be included that would be imported if you are using Windows cluster in your environment, that would great the groups automatically and override the discoveries to prevent clustered "Servers" from discovering as integration services.