This is a little example MP for some things that are possible with SCOM. It also serves as a good example MP on how to write classes, discoveries, and most importantly many task examples for command line, VBscript, and PowerShell.
I didn’t write all these – a bunch of ideas came from Jimmy Harper, Matt Taylor, and Tim McFadden and their MP’s. This was more to combine lots of useful administration in one place.
First – useful discovered properties:
The “real” agent version
The UR level of the agent
Any Management Groups that the agent belongs to. This is nice to see for old management groups that get left behind.
A check if PowerShell is installed and what version. This is important because PowerShell 2.0 is required on all agents if you want to move to SCOM 2016.
OS Version and Name
Primary and Failover management servers. I am getting this straight from the agents config XML file, sometimes agents might not be configured as you think – this is from the authoritative source…. what’s in that specific agents config.
Lastly, the default Agent Action account. Helpful to find any agents where someone installed incorrectly.
Next up – the tasks:
One of the problems with tasks, is that they are scoped to a specific class. Some cool tasks are attached to Windows Computer, some to HealthService, some to specific app classes. Or – people write tasks and scope to System.Entity. This places the task in ALL views. That’s handy, but if everyone did that we’d have an unusable console for tasks.
Computer Management – duh.
Create Test Event – this task creates event 100 with source TEST in the app event log, and there is a rule in the MP to generate an info alert. This will let you test end to end agent function, and notifications.
Execute any PowerShell – this task accepts one parameter – “ScriptBody” which allows you to pass any powershell statements and they will execute locally on the agent and return output:
Execute any Service Restart – this will take a servicename as a parameter and restart the service on any agent on demand. You should NOT use this for the Healthservice – there is a special task for that:
Execute any Software from Share – this task will accept an executable or command line including an e4xecutable, and a share path which contains the software, and it will run it locally on the agent. This is useful to install missing UR updates, or any other software you want deployed. This will require that “Domain Computers” have read access to the files on the share.
Export Event Log – this task will export any local event log and save the export to a share. It will require that the “Domain Computers” have write access to the share.
HealthService – Flush – This task will stop the agent service, delete the health service store, cache, and config, and start the service back up, provoking a complete refresh of the agents config, management packs, and ESE database store.
HealthService – Restart – This is a special task which will reliably bounce the HealthService on agents using an “out of band” script process. Many scripts to bounce the agent service fail because when the service stops, the script to start it back up is destroyed from memory.
Management Group – ADD and Management Group – REMOVE – these are script based tasks to add or remove a management group from an agent
Ping – (Console Task) - Duh
Remote Desktop – (Console Task) - Duh
Do you have other useful agent management tasks that you think should be in a pack like this? Or discovered properties that are useful as well? I welcome your feedback.
188.8.131.52 - Initial Release
184.108.40.206 - Updated with additional proerties and dual versions for safer tasks.
220.127.116.11 - Corrected minor bug in script names in export event log task
18.104.22.168 - Updated to support SCOM 2012R2 UR13 and SCOM 2016 UR3 in update rollup discovery
22.214.171.124 - Updated OS Version discovery to PowerShell to better handle WS2016 and Windows 10