Automating OpsMgr Part 18: Second Update to the OpsMgrExtended Module (v1.2)

Introduction

This is the 18th instalment of the Automating OpsMgr series. Previously on this series:

• Automating OpsMgr Part 1: Introducing OpsMgrExtended PowerShell / SMA Module
• Automating OpsMgr Part 2: SMA Runbook for Creating ConfigMgr Log Collection Rules
• Automating OpsMgr Part 3: New Management Pack Runbook via SMA and Azure Automation
• Automating OpsMgr Part 4:Creating New Empty Groups
• Automating OpsMgr Part 5: Adding Computers to Computer Groups
• Automating OpsMgr Part 6: Adding Monitoring Objects to Instance Groups
• Automating OpsMgr Part 7: Updated OpsMgrExtended Module
• Automating OpsMgr Part 8: Adding Management Pack References
• Automating OpsMgr Part 9: Updating Group Discoveries
• Automating OpsMgr Part 10: Deleting Groups
• Automating OpsMgr Part 11: Configuring Group Health Rollup
• Automating OpsMgr Part 12: Creating Performance Collection Rules
• Automating OpsMgr Part 13: Creating 2-State Performance Monitors
• Automating OpsMgr Part 14: Creating Event Collection Rules
• Automating OpsMgr Part 15: Creating 2-State Event Monitors
• Automating OpsMgr Part 16: Creating Windows Service Monitors
• Automating OpsMgr Part 17: Creating Windows Service Management Pack Template Instance

Before I diving into the topic of creating generic rules using the New-OMRule function from the OpsMgrExtended module, I have updated this module again. It is now on version 1.2.

I was working on another project and I needed to use the New-OMRule function to create rules and I realised this function did not support specifying optional RunAs accounts for member modules. As I needed to create rules that use a RunAs account in the data source module, I had to update this function to accommodate it.

Additionally, as I mentioned in the previous post (Part 17), there is a bug in the New-WindowsServiceTemplateInstance function, where the description field is not populated. I have also fixed it in this release.

What’s New?

So, in summary, here’s what’s changed:

• Updated OM-Rule function to allow specifying optional RunAs profile for each member module.
• Fixed the issue in New-WindowsServiceTemplateInstance function where the description field is not populated.

Where to Download V1.2?

I have updated the original link, so you can download this updated version from:

• PowerShell Gallery
• GitHub

Conclusion

Now that I’ve updated and enhanced the New-OMRule function I will demonstrate how to create rules using this function as planned in the next module.