![]() ![]() ![]() ![]() Helpful to find any agents where someone installed incorrectly. 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…. NET runtime version available to PowerShell This is important because PowerShell 2.0 is required on all agents if you want to move to SCOM 2016.ĬLR. This is nice to see for old management groups that get left behind.Īny Log Analytics ( OMS) Workspaces the agent reports to.Īny Log Analytics ( OMS) Proxy URL if configured.Ī check if PowerShell is installed and what version. If Active Directory Integration is enabled or not for the agent assignmentĪny Management Groups that the agent belongs to. It also includes views for Health Service and Health Service Watchers, for specific tasks that apply to those classes. It includes a view for the custom agent class properties (SCOM Agents) along with custom class properties for Management servers and Gateways (SCOM Servers). This MP creates a folder in the console with some views for Agents and Servers. This was more of an effort to combine lots of useful administration in one place. 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. 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. It allows you to have a lot of handy discovered properties, and includes tasks that allow you to delegate administrative actions to your users. This is a Management Pack that eases the administrative burdens in SCOM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |