Windows 10: Connecting to Windows server over Winrm with https from Linux System

Hi TeamWe have a scenario, where we need to connect to Windows server from a Linux Server Jenkins host is linux We want the connection to happen over https with WinRMFor which we have following in place:1. WinRM is configured with http 5985, https 5986 listeners.2. Https listener is configured with SSL with thumbprint of SSL certificate whose CN is domain name, listener configuration successful.3. WinRM Service is running.Connection from Linux server does not work when in my command I specify to use SSL transport for WinRM, its failing over SSL certificate issue.Currently, I haven't per

:)

 

SCOM 2012, 2016 and 1801 - WinRM basicauth when monitoring Linux

thanks! I moved the thread to
https://social.technet.microsoft.com/Forums/en-US/b9075eff-d133-459a-b4ae-27e3609e8ad0/scom-2012-2016-and-1801-winrm-basicauth-when-monitoring-linux?forum=operationsmanagergeneral

 

SCOM 2012, 2016 and 1801 - WinRM basicauth when monitoring Linux

Hi there,

I got the task to move all monitoring for Linux machines to SCOM 2012. According to Nicole (see SCOM 2012,
WSMan, and Unix/Linux Computer Discovery) it is prerequisite to enable Basic Authentication on the SCOM management server from where the Linux boxes are monitored. I checked with winrm get winrm/config/client and voila, it was disabled
by a GPO because of PCI DSS rule 8.1.4.1 Set 'Allow Basic authentication' to 'Disabled'.

Unspecified failure

Unexpected DiscoveryResult.ErrorData type. Please file bug report.

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

The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Verify the WinRM client configuration for all management servers in the resource pool and try the request again.

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)

Therefore I am in some kind of dilemma and want to know if and how this will be tackled in SCOM 2016 and SCOM 1801.

Please help!

Thanks

 

Windows Subsystem Linux

Hello,

We would like to know more about the issue you're experiencing with using
Windows Subsystem for Linux. Kindly answer the following questions:

• Are you developing a program, an app, or a software for Linux?
• Is your Window 10 PC connected to a domain?
• Are you managing a Windows Server PC?
• What troubleshooting steps have you tried so far?
• Can you tell us the Version and OS build of your Windows 10 device? You can find this information by clicking the
  Start button, type About your PC, and then press
  Enter.

We need the following information in order to determine if we need to refer your concern to the
TechNet forums or the Microsoft Developer Network (MSDN) forums.

For now, we suggest reviewing these support articles to find out if there's an issue with the installation of
Windows Subsystem for Linux:

• Install the Windows Subsystem for Linux
• Troubleshooting Windows Subsystem for Linux

We'll be waiting for your response.