
Graham Davies
Technical Product Manager – SCOM products
Technical Product Manager – SCOM products
We're excited to announce a new series of posts over the coming weeks covering how to use the Community PowerShell Management Pack to enhance your SCOM monitoring. The Community Management Pack brings PowerShell scripting wizards to SCOM authoring so you can plug your existing PowerShell scripts into SCOM with minimal complexity.
There will be examples of configuring monitors, rules (alert and performance), diagnostics and recoveries, and how to leverage "Cookdown" to improve performance and scalability of your PowerShell scripts.
Part 1 - Create a Monitor to remotely monitor a file share including using Run As Accounts.
Part 2 - Create a Performance Collection Rule to use the same data source as the monitor (taking advantage of "Cookdown" with SCOM authoring).
Part 3 - Add a diagnostic to the Monitor.
Part 4 - Add a recovery to the Monitor.
Stay tuned!
Let me know what you would like to see in future posts.
As we continue to invest in the SCOM Community, we'd love to hear your thoughts and feedback on what features or improvements you would like to see in future versions of the SCOM PowerShell Community Management Pack.
How can we expand or enhance current functionality to better meet your needs? How are you using the Management Pack today?
Your insights are invaluable in helping us ensure that the Management Pack remains a powerful tool to the SCOM Community.
What else would you like to see? Please post your feedback on Community Answers (or Direct Message me via Community Answers).