Forgive me if this is already explained in the migration documentation, I just wanted to be sure before I start the project that I am ok with the workflow.
I have a physical 2012 Essentials Server that is currently running as the DC for a small network of 10 users. It runs two LOB applications as well as the Essentials role which is used for Office 365 integration and Remote Access through the RDP Gateway (or RWW).
I am replacing this physical server with a new machine running Server 2019 STD with the Hyper-V role that will host two VMs. One for the new DC using 2019 Standard (NOT Essentials) and this VM will also be the file/print server. The second virtual member server will be used for the LOB applications and also run AD Connect and later run RD Gateway.
If I create the two new VMs and domain join them to the Essentials AD, as the new DC is Standard and not Essentials when it takes over as the new primary DC will the previous 2012 Essentials server continue to run as a member server without needing to remove it from AD in 21 days?
The priority for the initial phase is to domain join the two new virtual servers and make the new 2nd member server take over the new LOB software.
When the LOB applications are operating on the new member server the primary DC role (and FSMO) can be moved to the other VM running 2019 std server, The old LOB application can continue to run on the 2012 server as a member server for reference purposes until it is deemed appropriate to retire and decommission in the meantime print services and data can be moved over.