I setup a Server 2019 VM and migrated our old 2008R2 file server, to this server with the Storage migration services through Windows Admin Center.

It seems to work as designed and seems to be a great tool for admins.

However on our current production file server, the migration takes 7 days. Too long to perform it out of hours, and too long to downtime the server. The result is outdated files on the destination side. I haven't found a way with SMS to resolve the issues with latest files being left behind on the source machine.

I'm not sure if this is come up in future updates but it would be great/necessary in fact to re-sync changes after this process, or during cut over (however i suspect the rate of change would make during cut over too lengthy process). Incorporating a simple re-sync changes/update file sync, within, or at the end of the cut over would make this method 100% perfect.

- After installing and promoting to domain controller the network type in the Network & Sharing Center still shows Public when it should be Domain. This blocks many domain only functions from being possible. For example, remote desktop with or without the gateway is not possible unless you go into the firewall settings to allow public access to port 3389 and/or port 443. Setting the Network Location Awareness service to Automatic (Delayed Start) does not provide enough time for other services to start so the correct network type is used. What I had to do was set up a task in Task Scheduler with “net stop nlasvc /y” to execute at system startup with a 5 minute delay. When the NLA service is stopped it will restart automatically, showing the correct network type of “Domain” upon its restart.
- Wireless WAP/WAP2 Enterprise not working. Unable to communicate with RADIUS. Turns out, the built in firewall rules for ports 1812 and 1813 just flat out are not working. To fix, manually create an incoming rule for UDP ports 1812-1813.
- NPS refuses all connections for RD Gateway for remote desktop, wireless and VPN. This is because NPS accounting is unable to write to the log files at C:\Windows\System32\Logs. Even though the default permissions are correct, writing to the logs fails with “permission denied”. To work around this configure accounting to log to a text file on the local computer and remove the checkmark from “if logging fails discard connection attempts”.

Actually i can't enable replication if one disk is a physical disk, also if i don't plan to enable replication for the physical disk. I would prefer to enable replication without this physical disk, but for the other virtual disks.
It seem to be only an block in the Hyper-V Manager, so it would be great to move this check for blocking the replication after the user was able to select the disk to be replicated.
Only if here the physical disk is still enabled, block the replication with the corresponding error message:

"Replication can't be activated. Replication can't activated for VMs with direct attached disks."

Hello,

as it is quite comfortable for users to simply open a website, click on the desired printer and simply click connect to install it, I would like to ask if there are plans to update the Internet Printing Feature as it is only working with IE. And as we all know IE is going to be kicked sooner or later so that the feature becomes useless. I would love to see this function updated with Corporate Identity options, domain trust settings. Maybe even one website for all print servers in the company? Or maybe you can put it in the cloud as well?