Test Migration fails after replication.

Question

Test Migration fails after replication.

Patel, Ashish 1

Hi All,

I have done the discovery and I have done the replication as well. I can see 1 replicated VM which has no dependency on anyone and its shows in Protected state.

Now I have triggered the Test Migration and I am very happy that test migration has created the necessary resources like VM, NIC and DISK.

Problem comes when I do the RDP. it doesn't work !! I have created new NSG and I have attached to NIC then open the RDP port.

I have also applied the public IP to my VM but still I cant do RDP. Azure Bastion also fails.

Any idea why I cant RDP when machine is in the running state ? or any solution because this is really crazy stuff.

Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2021-08-02T17:07:58.26+00:00
@Patel, Ashish Sorry for the inconvenience this must have caused!

IMO, this is not an Azure Migrate issue. Instead, its an Azure VM platform related issue. You may try basic RDP troubleshooting steps should help resolve this issue.

If that doesn't help, try:

Changing VM size or

Create a new NIC with a public IP and associate it with the VM

If nothing works, the best would be file a support case to Azure technical support team for further investigation.

---------------------------------------------------------------------------------------------------------------

If the response helped, do "Accept Answer" and up-vote it.
Patel, Ashish 1 Reputation point

2021-08-02T18:00:55.093+00:00

I tried all that but still its not working,

On VM page under VM details it doesn't detect the OS and Agent details. They are all blank. Only detail it shows Windows OS

I will try one more time this long activity. if this doesn't work then I will mark end to Azure.....
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2021-08-02T18:43:20.127+00:00

@Patel, Ashish Try updating VM agent before performing the steps mentioned in the troubleshooting guide.