Category: SCOM 2016

1 commentsPowershellSCOM 2012SCOM 2016SCOM 2019Certificatescross platformimportlinuxscxcertconfig.exeunixxplat

Easily Configure SCOM Cross-Platform Management Server Certificates

One of the more annoying tasks when configuring monitoring for nix/xplat agents is exporting management server certificates, then importing those certificates on all other members of the designated cross-platform resource pool. When you deploy a nix agent, the agent will automatically trust only the management server which performed the certificate signing procedure during the agent ….  Read More

0 commentsSCOM 2016

SCOM Export-SCOMKnowledge Report

Export-SCOMKnowledge Available here: SCOMHelper PowerShell Module This function will get all rule and monitor knowledge article content and output the information to separate files (Rules.html and Monitors.html) in the output folder path specified. In the example above the variable will be assigned a collection of all management pack objects with “.AD.” in the name.That subset/collection of ….  Read More

1 commentsPowershellSCOM 2012SCOM 2016SCOM 2019Configuration ReportEffective ConfigurationpowershellSCOM Configurationscomhelper

SCOM Effective Monitoring Configuration Report

Export-SCOMEffectiveMonitoringConfigurationReport Available here: SCOMHelper PowerShell Module Report contains these columns: AlertPriorityAlertSeverityClassIdClassNameDescriptionEnabledEntityIdEntityNameGeneratesAlertIndexOverriddenOverridesParametersPathWorkflowDisplayNameWorkflowIdWorkflowMPNameWorkflowNameWorkflowType*Note: “Overrides” column does not include customizations settings for the standard overrideable parameters: AlertPriority, AlertSeverity, Enabled. However, the values shown in these columns are the actual effective values and are accurate. Example 1: Single Windows Computer – CSV Will create a complete/full report CSV file ….  Read More

0 commentsSCOM 2016Protected Users Security Groupscom installation

Protected Users Security Group – SCOM Installation

This will be a short post. Hopefully this will save others some headache. Summary: The user account performing the SCOM 2019 installation was a member of the Protected Users Security Group. This caused installation failure/blockage during the SCOM 2019 Reporting component at the mgmt server screen. Scenario:User account is local admin on mgmt server, SQL ….  Read More