This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 77%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Hi,
We have a SCOM2012 server and want to migrate to SCOM2016/2019. I will need to get an inventory of the monitored items and then verify which devices are monitored by SCOM for up/down purposes and/or then see which servers are being monitored for services and which templates are applied.
The goal is to reduce our SCOM footprint and ensure that our devices are monitored by our global monitoring tool and identify any gaps in our monitoring.
Does anyone have a TSQL script that will generate a report of monitored devices?
Thank you,
Raymond
Hi @raymond
The goal is to reduce our SCOM footprint and ensure that our devices are monitored by our global monitoring tool and identify any gaps in our monitoring.
Not sure what you want, could you post what you have tried or any issues you encountered.
Hello @LiHongMSFT-4306 I was looking to create a report of which servers are being monitored and of those servers which services are being monitored and also if a management pack is applied to a specific server. This will help adding the monitored devices onto our other monitoring tools for a side by side comparison.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
There is no such built in Report out of the box, you would need to create a custom SQL report to put together the information or extract it using PowerShell. The reason is of how SCOM is designed. Depending on what Management Pack you import, and depending on which class discoveries, monitors and rules are enabled that data might be different. As mentioned in my other post, have a look at MPViewer. And as others mentioned there is also the option to export what is the actual configuration on a particular class instance with the Export-SCOMEffectiveMonitoringConfiguration cmdlet.