Azure Migrate discovery issues, unable to remove discovered servers and unable to add server 2016 cluster

Question

Hi,

We are setting up Azure Migrate and are currently stuck on the discovery part.

I managed to input the wrong cluster under discovery source and I can't find any way to delete this resource on the appliance the delete option is not available. The status has been in Discovery initated for a couple of hours and the servers turn up in the portal for this cluster (see pic below row #2). In Azure Portal i can't find a way to stop the discovery of the VMs on this cluster which i believe might be the first step.

In addition I tried to add the correct cluster which is Win Server 2016 and validation fails with "The given key was not present in the dictionary"

I found this thread https://learn.microsoft.com/en-us/answers/questions/1624995/the-given-key-was-not-present-in-dictionary and has set the envelope size (Set-Item -Path WSMan:\localhost\MaxEnvelopeSizeKb -Value 8192) on all hosts as well as on the appliance but I am stuck with the same error so I am unable to add this cluster. The account used is Domain admin and has full access to the cluster.

Answer 1

I managed to sort this, the cluster had some storage issues and one node was down in the cluster. Unsure exactly what did the trick but I evicted the node that was down and then validation was fine for the cluster. However I was not able to start discovery as the button was greyed out. restarted appliance to no avail and ended up deploying a new appliance which worked as intended for the discovery part.

Answer 2

I managed "The given key was not present in the dictionary" by adding an unresolvable hyper-v host to the appliance' hosts file.

We noticed that we can't connect to the hyper-v host via mstsc using the NetBIOS Name from the appliance.

Oliver.