Forum Discussion
Cutover Timeout recommended settings
Yes, until we give you the option to skip networking that I mentioned before (coming in an update in a month or two), IaaS VM is not something SMS currently supports. Anything you do right now is hacking.
For the source computer though, that is something entirely unrelated and should be working fine here. Is the DNS server IP address(s) being assigned by DHCP or set statically? I need to understand exactly how to repro this. That it's not registering with DNS is the real issue here - did your customer disable automatic DNS registration?
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?
Thanks for the help Ned.
What 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).