Forum Discussion
Cutover Timeout recommended settings
Hello I'm trying to migrate a server to Azure. I'm in the cutover phase, it has a default timeout of 2880 minutes, which is 48 hours. Personally I can't have a file server "offline" for 48 hours d...
Thanks, for the reply Ned
I'll check on the DNS registration. From what I see in AD right now, it is set for nonsecure and secure updates, so the devices that get suffix and ip information and cannot be domain joined should show up appropriately. This would be one of those boxes. I'll check on it though.
So for this particular project i won't be able to wait until the skip the networking feature is available.
What exactly happens in the cutover piece? I think I remember reading in the documentation that I could stop after transfer if I didn't want to actually assume the identity of the old file server on the new one. If all I have to do is shut down the old file server, and rename the new one manually and I'm done then I'll do that manually. If there are other steps that I'm missing out on with the cutover process can you share what happens?
NedPyle
Microsoft
MicrosoftWhat I'd recommend instead for Azure IaaS currently is:
1. Migrate to an on-prem VM
2. Use ASR to move that VM to Azure, and then turn off ASR for that VM so it's not continuously protected (i.e. lift and shift), so you don't pay for anything. https://azure.microsoft.com/en-us/services/azure-migrate/
But you'll need to figure out why DNS registration is broken, or manually register the DNS entries so that cutover can complete (it will if you do that; we've had one lab here with no DNS auto-registration allowed and that was my solution there).
Thanks for the help Ned.