Do I need 2 separate appliances, one for assessment, and one for migration? I was trying to re-use the assessment appliance as migration appliance, but I got some IIS errors when installing the ASR Unified Setup. My scenario is Physical Server -> Azure VM.
@@AzureAcademy Hey Dean, I sorted it out. I was simulating Physical Server -> Azure VM using Azure VM as Physical Server. That was an agent-based migration, so I need 2 separated server, one is Win 2022 as the assessment server, one is Win 2016 as the migration server.
hello and thanks for the video... How can I do a demonstration for migration of physical serer ? which envrionment should I have? a free access to Azure will be sufficient? and what about customer environment whcih tool can I use for virtualisation and physical serer creation?
yes I think a free Azure Account can do this. You would need a physical server...or a VM that you can pretend is physical 🙂 Then use the physical tools. Once analysis is done you can show the reports and plan the migration...then complete it in your demo
@@AzureAcademy Thanks for your answer, useful... and what about dependency analysis, should I do it? and should I choose agentless DA or agent-based Dependency Analysis?? Thanks
It depends how you want to migrate. If you move everything at the same time dependencies don’t matter…because EVERYTHING is moving. But if you only do a partial migration or move 1 app at a time then dependencies are critical…make sense?
Hello @Dean, Thanks for this wonderful video. I have a question. One of the companies have physical servers, a DC, SQL server and a file server on prem. Can they use the method you described to move their DC and file server to Azure?? If yes, do they need S2S connection to on premises and the DC will be the exact copy of the onprem including Active Directory. Your assistance will be greatly appreciated. Thanks for your time. Regards,
If you have more then 1 DC you should set up a new one in Azure and use DC replication. YES this would require S2S VPN or some other hybrid connectivity
When on prem, Inside the OS we generally configure static IP addresses…however Azure works on DHCP and static reservations, so inside the OS your VMs should ALL be DHCP. Then your ip gets assigned based on the subnet, and you can specific a static reservation in Azure, NOT in the VM. Make sense?
The DNS records on the domain controller may or may not show the ip update, it depends on how things are setup. 1. Is there a VPN or Express Route connecting on prem to Azure? (Azure Migrate doesn’t need one to move your VMs) 2. Is there a DC in the cloud joined to the same domain 3. Do you allow that Cloud DC to update DNS records
Hello it was a great information and the way you teach is awesome Just need to ask one question what steps to be followed to migrate on-prem DC to cloud
2 paths you could follow. 1st if this is your ONLY DC I would migrate it like any other server 2nd if you have 2 or more DCs or you want to keep your DC on prem I would build a new vm in the cloud, promote it to be a DC as a member server, set it up as a new AD Site with a dedicated subnet and give it a few days for AD replication to sync everything. Then you can leave them Obote running or move the FSMO roles to the new DC and power off the old one Make sense?
@azureacademy software inventory not happening throwing 10005 error for ubuntu servers... No issues for red hat. What will be the troubleshooting steps
