This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 71%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Hi! I was a bit careless, and managed to delete my Recovery Service Vault without unregistering my Hyper-V hosts first. Now, when I try to register the Hyper-V host to a new vault, I get an error saying that the server is already registered to a vault (but, I know the vault is deleted, so how can they say it is already registered?)
I found a PowerShell script here https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-manage-registration-and-protection#unregister-a-connected-configuration-server, and ran that on the host. But it still says that the host is registered to a vault.
Can anyone help me with this?
Should be able to follow along with the three steps here.
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-manage-registration-and-protection
--please don't forget to Accept as answer if the reply is helpful--
This is the link I have in my question. The problem is that my Recovery Vault is deleted, so I cannot do these steps (Unregister a Hyper-V host in a Hyper-V Site), because they are not there. And I ran the Powershell-script in the steps, on my host, but it still says "Is registered with a vault". I just cannot understand how it can be registered with a vault if the vault is deleted... If you mean any other steps in the same page, please tell me which "chapter" I should look at. I am new to this :)
@Dave Patrick - I did this yesterday (from the link you sent, and I shared). But got the same response. I also ran this powershell script: https://github.com/Huachao/azure-content/blob/master/articles/site-recovery/site-recovery-manage-registration-and-protection.md (I think it is the same) today, and then it worked. So I dont know, maybe I just had to wait a day, or maybe this other script is different. Anyway, I am helped now. Thanks!
Glad to hear problem is sorted. You're welcome