This is the situation i faced because of lack of pro-activeness.
I was doing this migration via River-Meadow tool from on-prem (VMWare) to Azure. Lets not get into why i was using RM and not ASR thats a totally different discussion here , we will be only talking about the issue i faced and how we fixed it.
So here is the Architecture :-
- On-prem and Azure connected via Site-2-Site VPN
- On-prem AD extended to Azure VM
Now RM replicate or do the image based conning , means VM are replicating to the Azure with same name and already domain joined, only outside name and IP is changing (from Azure Vnet)
So i have started my migration after establishing the above mentioned points and as soon as VM replicated to Azure and started running before i could change the name and remove it from the domain , Source machine got removed from domain automatically worst part is this we couldn't know until customer opened the ticket stating migrating machines are getting out of the domain.
After digging little deep we come to the conclusion its happening because its image based migration and new VM with same and domain joined when gets the new IP from azure vnet , AD register the new VM and releases the old VM.
Resolution :
During Image based migration where AD is extended, we need to make sure either use the NSG which would break the traffic to the AD of new VM or remove the DNS from Vnet and apply on NIC once you changed the name and re-joing to the domain.
I was doing this migration via River-Meadow tool from on-prem (VMWare) to Azure. Lets not get into why i was using RM and not ASR thats a totally different discussion here , we will be only talking about the issue i faced and how we fixed it.
So here is the Architecture :-
- On-prem and Azure connected via Site-2-Site VPN
- On-prem AD extended to Azure VM
Now RM replicate or do the image based conning , means VM are replicating to the Azure with same name and already domain joined, only outside name and IP is changing (from Azure Vnet)
So i have started my migration after establishing the above mentioned points and as soon as VM replicated to Azure and started running before i could change the name and remove it from the domain , Source machine got removed from domain automatically worst part is this we couldn't know until customer opened the ticket stating migrating machines are getting out of the domain.
After digging little deep we come to the conclusion its happening because its image based migration and new VM with same and domain joined when gets the new IP from azure vnet , AD register the new VM and releases the old VM.
Resolution :
During Image based migration where AD is extended, we need to make sure either use the NSG which would break the traffic to the AD of new VM or remove the DNS from Vnet and apply on NIC once you changed the name and re-joing to the domain.
The information you've shared on Azure Migration has really pleased me. It's a fascinating article, both for me and for others. Thank you for bringing such interesting topics to our attention.
ReplyDelete