Current Version: 10.19.10349.0 4/19/2020
Quick Download: https://gallery.technet.microsoft.com/SCOM-Agent-Management-b96680d5
This is a Management Pack that eases the administrative burdens in SCOM. It allows you to have a lot of handy discovered properties, and includes tasks that allow you to delegate administrative actions to your users. 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, Tim McFadden, Daniele Grandini, Raphael Burri, Brian Barrington, Patrick Donovan and their feedback + MP examples. This was more of an effort to combine lots of useful administration in one place.
This MP creates a folder in the console with some views for Agents and Servers. It includes a view for the custom agent class properties (SCOM Agents) along with custom class properties for Management servers and Gateways (SCOM Servers). It also includes views for Health Service and Health Service Watchers, for specific tasks that apply to those classes.
First – useful discovered properties:
The “real” Agent Version
The Update Rollup level of the agent
If Active Directory Integration is enabled or not for the agent assignment
Any Management Groups that the agent belongs to. This is nice to see for old management groups that get left behind.
Any Log Analytics (OMS) Workspaces the agent reports to.
Any Log Analytics (OMS) Proxy URL if configured.
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.
CLR .NET runtime version available to PowerShell
OS/CPU Architecture (AMD64 or x86)
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.
The default Agent Action account. Helpful to find any agents where someone installed incorrectly.
The agent install path.
If the APM services are installed with the agent, or if the Agent was installed with NOAPM.
If the agent uses a Certificate for Healthservice communication, along with Cert Expiration, Thumbprint, and Issuer.
The Agent IP Address
The Port connectivity availability status (Connection) of agents to an array of MS and GW servers to test for firewalls
Also I added server discovery of properties (Management Servers and Gateways):
Next up – the tasks:
SCOM Agent 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.
Agent – AD INT DISABLE (and ENABLE) – this task will enable or disable AD integration for agent assignment, and restart the agent.
Agent – DELETE – This allows your end users to DELETE agents from SCOM if they should no longer be monitored.
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.
HSLockDown – LIST Accounts, and HSLockDown – Add SYSTEM. These will list the accounts configured under HSLockdown and will also add Local System back if desired.
Management Group – ADD and Management Group – REMOVE – these are script based tasks to add or remove a management group from an agent
Log Analytics (OMS) Workspace – ADD and Log Analytics (OMS) Workspace – REMOVE – these are script based tasks to add or remove Azure LA workspaces and configure a proxy for direct internet or OMS Gateway. You can also choose your Azure Cloud Type – 0 (default) for Commercial Azure Cloud, or 1 for US Government Cloud.
Ping – (Console Task)
Remote Desktop – (Console Task)
SCOM HealthService Tasks:
This is a special task that will allow you to set agents back to “Remotely Manageable” instead of having to edit the SQL tables!
SCOM HealthService Watcher Tasks:
The “Agent – Delete” task is really cool. It allows an operator with access to the task to be able to clean up (DELETE) agents from the SCOM console – without having access to the Administrator role. This task will run on the management servers and delete agents (this is a Delete – not an uninstall) This is handy for cleaning up old agents that are not present anymore.
SCOM Server Tasks:
I have included “Agent – INSTALL” and “Agent – DELETE” tasks, targeting the management servers. These will allow you to push installAND delete SCOM agents from the Operators console. You simply need to Override the task and proved the computers FQDN:
In order for this task to work – it will attempt to push the agent as the SCOM Management Server Action account. You will need to grant that account administrative rights on your server in order to be able to use this.
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.
Warning: Some of these tasks can be considered “risky” to deliver to your Operators, like exposing the ability to execute any PowerShell, restart any service, and install any software from a share. If those are things you don’t ever want exposed in your SCOM environment – then delete those tasks from the MP, or do not expose them in your non-administrator scoped console access.
Download the MP here:
18.104.22.168 – Initial Release
22.214.171.124 – Updated with additional properties and dual versions for safer tasks.
126.96.36.199 – Corrected minor bug in script names in export event log task
188.8.131.52 – Updated to support SCOM 2012R2 UR13 and SCOM 2016 UR3 in update rollup discovery
184.108.40.206 – Updated OS Version discovery to PowerShell to better handle WS2016 and Windows 10
220.127.116.11 – Major Re-write to include Server Roles, add OMS workspaces, UR levels
18.104.22.168 – Renamed Views, Added Health Service Watcher View, Added Agent install and delete tasks, Added install path property
22.214.171.124 – Added AD Integration discovered property and tasks to enable/disable AD integration
126.96.36.199 – Added APM installed discovery to find agents that need NOAPM reinstall, Added Tasks for Agent Delete, and Set IsManualyInstalled to false, Added view for HealthService objects
188.8.131.52 – Added discovery for OMS proxy, Added tasks for OMS Workspace ADD and REMOVE, Minor bug fixes to Agent Properties powershell discovery.
184.108.40.206 – Bug fixes, Added properties for OMS, Added tasks for OMS, Changes to views based on customer requests
220.127.116.11 – Updated server properties discovery to properly detect UR level on Gateways
18.104.22.168 – Updated to support discovery of SCOM 2016 UR4
22.214.171.124 – Updated for SCOM 2012 R2 UR14
126.96.36.199 – Updated for SCOM 2016 UR5
188.8.131.52 – Updated for TLS 1.2 support
184.108.40.206 – Added OS/CPU Architecture property
220.127.116.11 – Added IP address and Port availability check
18.104.22.168 – Added support for SCOM UR6
22.214.171.124 – Fixed bugs for UR6 display, Added properties for certificates such as expiration, thumbprint, issuer
126.96.36.199 – Added tasks for HSLockdown, Added preliminary support for SCOM 2019
188.8.131.52 – Added support for SCOM 2019 RTM
184.108.40.206 – Added support for SCOM 2016 UR7
220.127.116.11 – Added support for SCOM 2016 UR8, and added support for US Government Cloud Type for onboarding Log Analytics direct agent configuration (OMS Workspace)
10.19.10311.0 – Added support for SCOM 2019 UR1
10.19.10311.2 – Added support for SCOM 2016 UR9
10.19.10349.0 – Added support for SCOM 2019 Post UR1 Hotfix. Fixed bug when a management server config file is huge and the script runs out of resources getting XML content.