I just ran into this and figured I would offer up a solution.
After migration from VMWare vSphere to Hyper-V we encountered an issue where we were unable to connect to a Windows Failover Cluster using Windows Admin Center. After banging my head against a wall for a long while and only seeing sparse information on this I thought I would add this to the old blog here. With everything moving to Microsoft Azure and the many dotted lines between the on-premises datacenters back to Azure, management of those on-premises resources and Azure resources have changed. Windows Admin Center, Powershell, and the Azure CLI all being leveraged to manage things along with many others.
Symptoms:
Whenever you attempt to add a cluster object to Windows Admin Center you receive and error stating "cannot determine the content type of the HTTP response from the destination computer". Additionally when attempting to use the powershell command "enter-pssession -name <ClusterName>" you receive the error that PSRemoting is not enabled etc. However, when attempting this same operation on each individual server within the cluster you ARE able to connect with a remote powershell session and also manage the individual server within the Windows Admin Center. Also, the old tried and true Failover Cluster Manager mmc snap-in works with no issues. However managing the entire cluster as a whole is much more beneficial.
Cause:
This was caused by the cluster objects in Active Directory being modified so that the delegation tab of the object was set to "Trust this computer for delegation to an service (Kerberos only)"
Solution:
In order to correct this, the cluster object must be modified to "Do not trust this computer for delegation".
Once this was done and replication took place I was able to add the cluster object into Windows Admin Center and had no issues with managing the cluster as a whole. Hopefully this helps someone out there that might have had the same issue.
No comments:
Post a Comment