Unregister and Delete MODERNIZED ASR DR appliance

Hi Julian - Can you look at the instructions again for where you registered your replication appliance on-prem here: https://video2.skills-academy.com/en-us/azure/site-recovery/deploy-vmware-azure-replication-appliance-modernized

You will need to log on to that and look at unregistering it from your ASR.

Following up to see if this has been implemented? We are facing the same issues as well about unregistering a source machine that was used by an old appliance, that was deleted on-premises and redeployed using same name and IP address. <RcmError xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RcmContract">^M
<ActivityId>03d971b2-41e1-4d93-b98e-031f20d0e6f6</ActivityId>^M
<ComponentErrorCode i:nil="true" />^M
<ComponentErrorMessage i:nil="true" />^M
<ComponentErrorPossibleCauses i:nil="true" />^M
<ComponentErrorRecommendedAction i:nil="true" />^M
<ComponentErrorSeverity i:nil="true" />^M
<ComponentId i:nil="true" />^M
<ConsumerId i:nil="true" />^M
<ErrorCode>MachineWithSameBiosIdAndFqdnAlreadyExists</ErrorCode>^M
<ErrorSeverity>Error</ErrorSeverity>^M
<IsComponentReportedError>false</IsComponentReportedError>^M
<Message>Installation of mobility agent failed as prerequisites are not met.</Message>^M
<PossibleCauses>The operation failed due to an internal error.</PossibleCauses>^M
<RecommendedAction>Retry the operation. If the issue persists, contact support. Learn more (https://aka.ms/BIOSID_conflict).</RecommendedAction>^M.</RecommendedAction>^M"https://aka.ms/biosid_conflict).%3c/recommendedaction%3e%5em")
<ErrorCategory>ClientError</ErrorCategory>^M
<IsRetryableError>false</IsRetryableError>^M
<MessageParameters xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" />^M
<ComponentErrorMessageParameters xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" />^M This is the error we get when we try to replicate a machine that once failed when we tried replicate using old the appliance that was deleted and redeployed. It keeps saying fqdn already exist, but we don't know what is running the check since the appliance was already deleted.