Getting This Error When Trying To Discover Numerous RHEL Systems

Brian Engel 1 Reputation point
2022-11-29T20:30:18.987+00:00

So I am in the middle of a SCOM 2012 R2 to SCOM 2019 side-by-side migration. I am currently discovering all of my RHEL systems in the 2019 environment. I have followed this document for multi-homing the RHEL agents - dual-home-scom-unix-linux-agents-and-migrate-part-1

I am guessing I missed some certs somewhere, though I can't figure out where, because I am getting Install and Manage on some of my systems instead of just manage. Anyhow the biggest error I am seeing and it's around 100 systems or so, is this one when I go to discover. It says an unknown error occurred, then this:

Unexpected DiscoveryResult.ErrorData type. Please file bug report.

ErrorData: Microsoft.SystemCenter.CrossPlatform.ClientLibrary.MPAbstractions.WSManUnknownErrorException

The SSL connection cannot be established. Verify that the service on the remote host is properly configured to listen for HTTPS requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https".

at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)

at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)

at Microsoft.SystemCenter.CrossPlatform.ClientActions.DefaultDiscovery.InvokeWorkflow(IManagedObject managementActionPoint, DiscoveryTargetEndpoint criteria, IInstallableAgents installableAgents)

If I stop the Omiserver on the target then the discovery works and shows Manage & Install. However then I get a new error on the install.

The SSL connection cannot be established. Verify that the service on the remote host is properly configured to listen for HTTPS requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https".

It installs the new agent but doesn't start it and put it into the new SCOM.

What's going on here?

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,442 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. XinGuo-MSFT 15,941 Reputation points
    2022-12-01T05:43:14.15+00:00

    Hi,

    For this issue, I recommend you try to enable Operations Manager Module Logging.

    https://learn.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/hh212862(v=sc.12)?redirectedfrom=MSDN

    There is a relevant thread you can reference:

    SCOM 2012 – Linux Discovery “Unspecified Failure”

    0 comments No comments