Problem Definition

The auto discovery request of the Dell PowerEdge servers to Dell Lifecycle Controller Integration (DLCI) version 3.3 for Microsoft System Center Configuration Manager (Configuration Manager) with Dell Provisioning Server (DPS) that is installed on Windows Server 2016 might fail. The failure is prompted with the No credential returned error message.

Root Cause

The auto discovery request failure occurs when the Dell PowerEdge servers’ sends an auto discovery handshake request to DPS installed on Windows Server 2016 over TLS 1.2. The TLS 1.2 handshake request by the Dell PowerEdge servers’ is rejected by Windows Server 2016 in this scenario. Although the handshake request is sent with the auto-negotiate flag, Windows Server 2016 returns an application error instead of a TLS error alert as in the earlier Windows versions such as, Windows 2012 R2. Hence, DPS cannot renegotiate with TLS 1.1.

Note: This behavioral change is observed in Windows Server 2016.

Solution

To perform auto discovery with DLCI version 3.3 for Configuration Manager with DPS, following are the two workarounds:

  • Performing auto discovery by installing DLCI with DPS on Windows Server 2016

To ensure successful TLS 1.1 renegotiation, set "SSLAlwaysNegoClientCert" to "true" by updating the SSLBindings of DPS.

See https://msdn.microsoft.com/en-us/library/ms525641(v=vs.90).aspx in Microsoft product documentation for more information about SSLAlwaysNegoClientCert.

See https://msdn.microsoft.com/en-us/library/ms689452(v=vs.90).aspx in Microsoft product documentation for more information about SSLBinding Class [IIS 7 and higher].

  • Performing auto discovery by installing DPS on a remote system other than Windows Server 2016

See the Dell Lifecycle Controller Integration Version 3.3 for Microsoft System Center Configuration Manager Installation Guide at Dell.com/support/home for more information about installing DPS and the supported OS configurations.