Posts

Showing posts from August, 2017

Installing new SSL certificate on SCOM 2012 R2

Installing new SSL certificate on SCOM 2012 R2 1- Create a setup information file for use with the CertReq command-line utility To create a setup information “RequestConfig.inf.” in order to utilize for cert requests [NewRequest] Subject="CN=<FQDN of computer you are creating the certificate, for example, the gateway server or management server.>" Exportable=TRUE KeyLength=2048 KeySpec=1 KeyUsage=0xf0 MachineKeySet=TRUE [EnhancedKeyUsageExtension] OID=1.3.6.1.5.5.7.3.1 OID=1.3.6.1.5.5.7.3.2 -------------------- Add additional OIDs here ------------------- An OID is a numeric value that identifies the application or service for which a certificate is used and is automatically attached to a certificate when it is created by a certificate authority (CA). For example, certificates used for client authentication use the OID 1.3.6.1.5.5.7.3.2. To view OIDs: Run | mmc add the certificates Snap-in| Personal |Certificates Sel...

Using Orchestrator to Place Servers in SCOM Maintenance Mode during SCCM patching Reboot

Image
This post is a follow up to my previous article "Automatically Placing Servers in Maintenance Mode with SCOM Rule during SCCM patching Reboot". This time I will share with you a simple SCORCH Runbook that will monitor a SCOM alert and place the server in Maintenance Mode if the SCCM process "CcmExec.exe " initiates a reboot. This will help reduce unnecessary SCOM alerts such as  Failed to Connect and Unexpected Shutdown etc... Figure 1 show the diagram or the  SCORCH runbook Figure 1 Let's start with the first activity: Monitor Alert. You want to configure this activity to monitor  New SCOM Alerts Name of Alert: Detects Server Reboot Description will contain:  CcmExec.exe  See Figure 2 below Figure 2 In the next activity, I am calling another runbook that will place the server in  Maintenance Mode.  Figure 3 shows a sample runbook I created for  Maintenanc Mode I will not go into...

SCOM 2012 Troubleshooting: re-mediate unhealthy Agent State

SCOM 2012 Troubleshooting: re-mediate unhealthy Agent State When encountering unhealthy (warning or critical) health agent state within your SCOM 2012  environment.  You need to  Flush Health Service State and Cache. This effectively stops the HealthService  (Microsoft Monitoring Agent) service Deletes the cache which sometimes can grow large and cause High IO issues and restart the service. In order to  to re-mediate this issue the issue, You can perform this manually or using PowerShell Table of Contents 1-Manually within the SCOM Console 2- Using PowerShell that loops through a list of computer names in C:\scripts\computers.txt 1-Manually within the SCOM Console Monitoring Expand to Agent Details Select the computers that are in Warning or Critical Agent State On the right hand under tasks Flush Health Service State and Cache 2- Using PowerShell that loops through a list of computer names in C:\scripts\computers.t...

Automatically Placing Servers in Maintenance Mode with SCOM during SCCM patching Reboot

Image
In this post, I will walk you through automatically placing Servers in Maintenance Mode   during SCCM patching Reboot  with a SCOM rule  I have done this with a  SCOM rule, SCOM subscription, and Orchestrator runbook. in here , I will only discuss the    SCOM rule. I will share the other methods in future postings. 1- Create a SCOM Alert based " Detects SCCM Reboot " in "Custom- Windows Server Monitoring " Management Pack  Authoring | Rules| New Rule Under Alert generating Rules Slect "NT Event Log"  Name the rule  For Target Select "Windows Computer " Next Select System for Log Name For Parameter See below This is based on  Event ID 1074 The process C:\Windows\CCM\CcmExec.exe (SERVERNAME) has initiated the restart of computer SERVERNAME on behalf of  user NT AUTHORITY\SYSTEM 2- Now Tie an action script to run acommad that will place Server in Maintenance mode ...