This blog series is co-written by:
Adam Dzyacky, Product Manager at Cireson
Dujon Walsham, Director at Walsham Solutions Ltd.
This blog series will show you how to implement process improvement/automation, reinforce the value of centralized toolsets, and demonstrate the near infinite configuration possibilities of Microsoft System Center Service Manager (SCSM) and Microsoft System Center Operations Manager (SCOM).
In part one, we looked at the pieces you need to structure processes for SCOM administration, including the Cireson Service Manager Portal, Advanced Request Offering, PowerShell Activity, Cireson Asset Management and Dujon’s SCOM Module.
In Part 2, we defined our process.
Then we set up new SCSM monitoring requests (for all SCOM levels of expertise) in Part 3.
…and now to wrap up things up with Part 4.
New Monitor Override
by Dujon Walsham
This is a slightly different request: the PowerShell Module has been ever so slightly altered so that we can now create a Request Offering that lets us create SCOM Monitoring Overrides. The result is an efficient process workflow that continues to standardize and template our SCOM administration:
1. Go to your Cireson Service Manager portal
2. Select the New SCOM Monitoring Requests
3. Select New Monitoring Request
4. From the dropdown list, select New Override. You should now see a series of options appear.
5. Example: we will select Monitor, and now we see a list of all of the Monitors that we had imported using our Cireson Asset Import connector. We’ll search for and select the ping monitor.
6. Now when we select our Monitor, we get another list of options that allow us to select which parameter we want to Override. In this case, we will choose the Interval Seconds, which is how often the Monitor runs.
7. Next we’ll select the machines that we want to use to Override the monitor. This list of machines comes from the SCOM Agents CI, which was populated by the Cireson Asset Import Connector.
8. Finally, hit Save to submit the request!
9. You’ll see the request listed in the Service Portal and the Service Manager console.
10. Once completed, check the location: you should see your created MPX fragment.
11. Create a Management Pack project in your Visual Studios and import the MPX file. You should see your XML structured like the example below. Then all you need to do is build the solution, and your management pack will be ready to import into SCOM.
Conclusion
We covered a LOT in this series.
- We touched on SQL, PowerShell and some Management Pack XML
- We streamlined SCOM Administration requests
- We automated the creation of Management Pack Fragments for SCOM
- But best of all, we templated and standardized the administration of SCOM Monitoring through Service Manager!
Whether you’re controlling SCOM or any other application in your environment, process improvement through the lens of Service Manager gives rise to an infinite list of possibilities that are controlled entirely by you.
Any process. Anywhere. Anytime!
Questions? We’re ready for them. Ask away.
Interested in learning more process improvement/automation techniques? Come to Innovate 2021, virtually, on May 26.
