[SCORCH] SCOM IP – “Failed to connect. Please verify your connection settings.”

Issue Definition After regsitering and deploying SCOM Integration Pack (IP) in Orchestrator, we need to configure a connection to specify link to your SCOM management server (Refer to Configure the connection). However, when you click on the Test Connection button, you might receive the error “Failed to connect. Pleae verify your connection settings.” …

[SCORCH] SCOM IP – “Failed to connect. Please verify your connection settings.” Read More »

[SCOM] SQL DB Engine Discovery Mechanism on Cluster

In summary For any SQL DB Engine on cluster to be discovered, firstly ensure the SQL Server Network Name is already discovered in “Agentless Managed”. If not, check if there is any orphaned resource in Windows Cluster. Details For SQL DB Engine on Cluster, the discovery is expected to run …

[SCOM] SQL DB Engine Discovery Mechanism on Cluster Read More »

Fail to connect to Orchestrator Web Service

Error Message The same error may occur after applying SCORCH 2016 UR4 and later versions. See Tips and Tricks for Applying SCORCH 2016 UR4 and Later Versions. Request Error The server encountered an error processing the request. The exception message is ‘An error occurred while executing the command definition. See …

Fail to connect to Orchestrator Web Service Read More »

SCOM Web Console – “Web Console Configuration Required”

When opening SCOM Web Console, you may get the notification “Web Console Configuration Required”. Normally you can click the Configure button (with SCOM Admin permission) and run the executable and refresh the browser window and you should see a web console login page next. But you have run SilverlightClientConfiguration.exe but the problem still persists, you …

SCOM Web Console – “Web Console Configuration Required” Read More »

SCORCH Web Service API

Web Service URLs Web Service URL (no change for 2016): http://sco01:81/orchestrator2012/orchestrator.svc/ Web Console URL: http://sco01:82/ Get runbooks: http://server01.contoso.com:81/Orchestrator2012/Orchestrator.svc/Runbooks Access Orchestrator Runbooks via Web Service Get a Runbook PowerShell $secpasswd = ConvertTo-SecureString “Password01!” -AsPlainText -Force $mycreds = New-Object System.Management.Automation.PSCredential(“contoso\Administrator”, $secpasswd) $OrchURI = “http://SCO01:81/Orchestrator2012/Orchestrator.svc/Runbooks?`$filter=Name eq ‘Test'” $ResponseObject = invoke-webrequest -Uri $OrchURI -method …

SCORCH Web Service API Read More »

Troubleshooting Gateway or Workgroup Communication Issue in SCOM

If you have deployed SCOM Gateway in your environment, or SCOM agent on a workgroup machine, but they can’t communicate with management server, you can refer to the following steps for troubleshooting. Based on my experience, these troubleshooting steps can help resolve >50% of Gateway/Workgroup communication issues. Troubleshooting Steps Make …

Troubleshooting Gateway or Workgroup Communication Issue in SCOM Read More »

Changes of user relationship in AD can’t be correctly synchronized to SCSM

Issue Description The relationship of users might be not correctly updated if related users were once re-named in AD or have duplicate records in DB. Cause 1 – Known Issue: a renamed user in AD will be treated as a new object in SCSM Symptom There are multiple records for …

Changes of user relationship in AD can’t be correctly synchronized to SCSM Read More »

Tips and Tricks for Applying SCORCH 2016 UR4 and Later Versions

Note: The issues mentioned below may occur after you install Orchestrator 2016 UR4, or install later versions directly without installing UR4 first. Issue 1 After upgrading Orchestrator to 2016 UR4 or 1801, you may get the following error message: “Could Not Connect To The Specified Database Server” or “The Server …

Tips and Tricks for Applying SCORCH 2016 UR4 and Later Versions Read More »