Unable to add failover cluster to Windows Admin Center

 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.

"Task failed Error: The remote certificate is invalid according to the validation procedure." in regard to Veeam Backup & Replication

"Task failed Error: The remote certificate is invalid according to the validation procedure." in regard to Veeam Backup & Replication

This usually happens after an upgrade of the vCenter Server. The backups will fail with the error above. Here is a quick and dirty fix for it. YMMV.

1) Open the Veeam B & R Console.

2) Select Backup Infrastructure.

3) Select Managed Servers.

4) Select the vCenter Server that is used to backup your Cluster/Farm.

5) In the "Edit VMware Server" screen click on credentials. (You should not have to change anything
    here).

6) Click next.

7) You will get an error about the certificate and be asked if you want to continue anyway.

8) Continue the process and let it  go through the "Detecting Server Type" and save the server
     configuration.

9) Go to your Backup Jobs and under "Virtual Machines to Backup" select each entry and click       remove. Make a note of any exclusions etc. and add them back in exactly as they were before.

10) After you have added them back in go down and click "Recalculate".
       You should see the size of the backup is calculated correctly. It may have said "N/A" before.

11) Re-run the backup job by selecting "Retry" or "Start".


This should clear the error and your backup job should run now as before. I hope this helps someone else with the problem. If not, maybe it will put you on the right track.

How to Fix “content was blocked because it was not signed by a valid security certificate” on Internet Explorer.

How to Fix “content was blocked because it was not signed by a valid security certificate” on Internet Explorer

11)      Navigate to the page with the error.

22)     Tell the browser to proceed to the web site even if there is a warning.

33)     When you see this: , click on the red X and select “Install Certificate”

44)     Select “Local Machine” and click Next.

55)     Select “Place Certificates in the following store”.

66)     Click Browse and check “Show Physical Stores”:

77)     Scroll up to where it says “Trusted People” and select it, then click OK.

88)      Click next when your screen looks like this:

99)     Click Finish on this screen:

110)   You should see a screen that says the import was successful:

111)   Click “OK” and close the screen where it shows the certificate information by clicking the Red X (if it is still open).

112)   Close Internet Explorer if it is still open and go to the web site again. Click where is says to continue.

This should resolve this issue. If you have another site that gives the same error, this should work for it as well.