Azure Migrate Duplicate Source

Question

I created a project for Azure Migrate. I walked through the setup and got to the part of adding and validating sources. I had 6 servers that were all on the same network and joined to the same domain. Two of the 6 servers validated properly but the other 4 would not and they stated Access Denied. I hit Start Discovery with the 2 validated and the 4 in Validation Failed status. Now when I remove them and try to add them back I get this error message

"This source is a duplicate of another source added previously either with the same or a different friendly name of credentials."

There is only the one in the portal and I cannot find the other.
I have deleted the contents of the Resource Group in Azure, including all hidden items. I recreated a new project and started completely over but it still says that on the same 4 IPs but not the 2 that originally were successful. I have uninstalled the app, deleted the folders from ProgramData and Program Files, cleared my browser cache, and searched all of registry for the IP.

I created a new project, reinstalled everything on the appliance server, and every time I go to add those sources I still get the same result.

Here is the item from the ApplicationOnboarding-Portal-2020-11-24 log in the C:\ProgramData\Microsoft Azure\Logs\ConfigManager folder

{
"SessionId": "removed",
"RequestId": "3b1eeff5-a2cb-428d-b3ca-aaf488f7913b-2020-11-25 03:06:47Z-MA",
"FabricAdapter": "Physical",
"SubscriptionId": "removed",
"LogLevel": "Info",
"PreciseTimestamp": "2020-11-25 03:06:48Z",
"CallerInfo": "X:\bt\1061841\repo\src\ApplianceOnboarding\Logger\Logger.cs:97:LogOperationEnd",
"Message": {
"OperationStatus": "Ended ValidateTargets",
"StartTime": "2020-11-25 03:06:47Z",
"EndTime": "2020-11-25 03:06:48Z",
"Message": {
"targets": [
{
"id": "removed",
"friendlyName": "domainadmin",
"IPAddress": "10.10.7.200",
"port": "5985",
"status": 3,
"type": "Windows Server",
"details": {
"BiosGuid": "removed"
},
"children": [],
"errorDetails": {
"errorCode": 60045,
"errorCodeName": "PhysicalDuplicate",
"message": "This source is a duplicate of another source added previously either with the same or a different friendly name of credentials.",
"recommendation": "You need to delete this duplicate source added and revalidate the previouly added sources to proceed with their discovery."
}
}
],
"errorDetails": null,
"success": true,
"lockBlock": false,
"summary": null
}
}
}

So I have searched in the ProgramData, Program Files, C:\Windows\Temp, %userprofile%\AppData, Registry, and C:\temp. I have removed everything from Azure. Where is it storing the fact that I have already once tried to connect to that server?

Answer 1

Ok we have found the solution, although it is not a great one. I was wrong about my above assumption and it was not that MS was storing the BIOS GUID. It happened because this particular company has their servers in a datacenter that runs on VMware and that datacenter provider company provided the OS image. That OS Image that they provide was not Sysprepped and the person who built the servers did not change the SSID. Yay! So the servers actually had the same BIOS GUID on them and you can find that by typing this in powershell.

get-wmiobject Win32_ComputerSystemProduct | Select-Object -ExpandProperty UUID

So there you go folks. Sysprep your images please!!