We did get this solved.
I believe I could have solved this without a ticket, but there were some very specific actions I had to take to get this working, and no way in the world I could have guessed it.
There also were 2 important details about the new vaults that I learned.
First, you cannot migrate "Azure Backup" to new vaults. You can only migrate "Azure Site Recovery" to new vaults.
Second, once you attempt to add a Site Recovery install on a VM to a vault, if it partially installs at all, it will add it in Azure in the background where you can't see it. The only place you can tell is when you choose to add a new ASR, the count of how many ASR's are already installed in the vault will go up. Mine showed there were 4 installed in the 'Add new ASR' screen, but only 1 was actually fully registered. This becomes important later in the install with the "Friendly name of the VM".
Steps to reuse my old ASR with a new vault using modern ASR.
- Uninstall all Azure Site Recovery software off of the old VM. This was around 10 or so apps.
- Rename Registry: HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Azure Site Recovery to something else
- Clean the previous http config from old deployment: Run on cmd/powershell as administrator: "netsh http delete sslcert ipport=0.0.0.0:443"
- Reboot
- Download and run the Powershell script from the new Azure Site Recovery vault, New ASR
- Reboot
- Start the configuration program on the desktop. You have to either disable the dumb Internet Explorer advance security junk, or just use Chrome. Even if you use IE, it screws up opening up new tabs when you authenticate. Chrome works better.
- During configuration, you must do the following:
- You must use a unique "Friendly name" of the ASR VM. You cannot use a name that has previously ever been used in Azure Site Recovery. This was my biggest hang up.
- You must also use the Exact same vCenter "Friendly name" as the working ASR. If you name it slightly different it will error out. This was my 2nd biggest hang up.
This all worked finally. The biggest issues were the "Friendly names" of the ASR VM (needs to unique) and vCenter (needs to be exactly the same), and clearing the sslcert.
Thanks to Microsoft Azure support team for all their help.