Edit

Share via

Troubleshoot CredSSP

  • Article

Applies to: Azure Local, version 22H2

Important

Azure Stack HCI is now part of Azure Local. Product documentation renaming is in progress. However, older versions of Azure Stack HCI, for example 22H2 will continue to reference Azure Stack HCI and won't reflect the name change. Learn more.

Some Azure Stack HCI operations use Windows Remote Management (WinRM), which doesn't allow credential delegation by default. To allow delegation, the computer needs to have Credential Security Support Provider (CredSSP) enabled temporarily. CredSSP is a security support provider that allows a client to delegate credentials to a server for remote authentication.

Enabling CredSSP is a degraded security posture, and in most circumstances should be disabled after the task or operation is completed.

Some tasks that require CredSSP to be enabled include:

  • Create Cluster wizard workflow
  • Active Directory queries or updates
  • SQL Server queries or updates
  • Locating accounts or computers on a different domain or non-domain joined environment

Troubleshooting tips

If you experience issues with CredSSP, the following troubleshooting tips may help:

  • To use the Create Cluster wizard when running Windows Admin Center on a server instead of a PC, you must be a member of the Gateway administrators group on the Windows Admin Center server. For more information, see User access options with Windows Admin Center.

  • When running the Create Cluster wizard, CredSSP may report an issue if an Active Directory trust isn't established or is broken. This results when workgroup-based servers are used for cluster creation. In this case, try manually restarting each server in the cluster.

  • When running Windows Admin Center on a server, make sure the user account is a member of the Gateway administrators group.

  • We recommend running Windows Admin Center on a computer that is a member of the same domain as the managed servers.

  • To be able to enable or disable CredSSP on a server, make sure you belong to the Gateway administrators group on that computer. For more information, see the first two sections of Configure User Access Control and Permissions.

  • Restarting the WinRM service on the servers in the cluster might prompt you to re-establish the WinRM connection between each cluster server and Windows Admin Center.

    One way to do this is by going to each cluster server, and in Windows Admin Center on the Tools menu, select Services, select WinRM, select Restart, and then on the Restart Service prompt, select Yes.

Manual troubleshooting

If you receive the following WinRM error message, try using the manual verification steps in this section to resolve the error. Example error message:

Connecting to remote <sever name> failed with the following error message: The WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer because the computer is not trusted. The identity of the target computer can be verified if you configure the WSMAN service to use a valid certificate.

The manual verification steps in this section require you to configure the following computers:

  • The computer running Windows Admin Center
  • The server where you received the error message

To resolve the error, try the following remedy steps as needed:

Remedy 1:

  1. Restart the computer running Windows Admin Center and the server.

  2. Try running the Create Cluster wizard again.

    For details on running the wizard, see Create an Azure Stack HCI cluster using Windows Admin Center.

Remedy 2:

  1. On the computer running Windows Admin Center, open Windows PowerShell as an administrator and run the following commands:

    Disable-WsmanCredSSP -Role Client  

    Enable-WsmanCredSSP -Role Client -DelegateComputer <Server FQDN Name>

  2. Use the RDP feature to connect to the server, and then run the following PowerShell commands:

    Disable-WsmanCredSSP -Role Server  

    Enable-WsmanCredSSP -Role Server

  3. Try running the Create Cluster wizard again.

    For details on running the wizard, see Create an Azure Stack HCI cluster using Windows Admin Center.

Remedy 3:

  1. On the computer running Windows Admin Center, run the following PowerShell command to check the Service Principal Name (SPN):

    setspn -Q WSMAN/<Windows Admin Center Computer Name>

    The result should list the following output:

    WSMAN/<Windows Admin Center Computer Name>

    WSMAN/<Windows Admin Center Computer FQDN Name>

  2. If the results are not listed, run the following PowerShell commands to register the SPN:

    setspn -S WSMAN/<Windows Admin Center Computer Name> <Windows Admin Center Computer Name>  

    setspn -S WSMAN/<Windows Admin Center Computer Name> <Windows Admin Center Computer FQDN Name>

  3. Use the RDP feature to connect to the server, and then run the following PowerShell command to check the SPN:

    setspn -Q WSMAN/<Server Name>

    The result should list the following output:

    WSMAN/<Server Name>

    WSMAN/<Server FQDN Name>

  4. If the results are not listed, run the following PowerShell commands to register the SPN:

    setspn -S WSMAN/<Server Name> <Server Name>  

    setspn -S WSMAN/<Server FQDN Name> <Server Name>

  5. Try running the Create Cluster wizard again.

    For details on running the wizard, see Create an Azure Stack HCI cluster using Windows Admin Center.

Remedy 4:

If any of the previous remedy steps failed or did not complete, this might indicate a record conflict in Active Directory. You can use a different computer name to reset the record as a new record in Active Directory.

To reset the record in Active Directory, reinstall the Azure Stack HCI operating system with a new computer name.

Remedy 5:

If the error message you're seeing mentions NTLM then try the following:

  1. On the computer running Windows Admin Center (the one with the "client" CredSSP role), run the following command to see what policies are configured:

    Get-ChildItem hklm:\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation

  2. If AllowFreshCredentialsWithNTLMOnly is missing, run:

    New-Item hklm:\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentialsWhenNTLMOnly

    Then run:

    New-ItemProperty hklm:\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentialsWhenNTLMOnly -Name 1 -Value "wsman/<Server FQDN Name>" -Force

Next steps

For more information on CredSSP, see Credential Security Support Provider.