Windows Admin Center Storage Migration should be able to use domain accounts
The cutover portion of the storage migration appears to use local accounts. We follow the CIS baselines and network access/remote login with local accounts is disabled. It would be nice to be able to use a domain account that has local admin rights to do the cutover.
Final point; the cutover had changed the destination computer name, but the add to domain had failed. I manually added the destination computer to the domain (while the cutover was stalled at 77% - joining the computer to the domain) and restarted it. Then the cutover procedure woke up , and restarted the destination computer again before announcing it had 'succeeded'.
At the point I discovered the cutover stalled, I connected to the destination VM; at that point the hostname was still the 'destination server name'. After getting logs, I retarted the destination VM; at that point the hostname had changed to the 'source server name' (i.e. the new VM was now the name of the original server - as expected. All share points were active. I can conclude the final failure with the unable to update password had something to do with the final restart.
Trying the cutover onto a Server 2019 CORE server (from a Windows 2008 R2 Enterprise server) of a simple file share directory (a large one at 275GB), the cutover failed at the point of (I assume) renaming the destination computer and adding it to the domain
The SMS Proxy Admin log had the following trailing entry:
User Name: media2019\MsftSmsStorMigratSvc
Error Message: Unable to update the password. The value provided as the current password is incorrect
Guidance: Confirm that the Netlogon service on the computer is reachable through RPC and that the credentials provided are correct.
I tried to use the 'feedback' operation, but it didn't work on my server computer using chrome when it tried the url "feedback-hub://?referrer=windowsAdminCenter&tabID=2&contextId=997"
Thank you very much for your feedback. You are correct, unfortunately that is not something we currently support but we will take it under advisement for future feature improvements.