Server 2012 Foundation migration

Question

I am planning a server migration from 2012 Foundation to 2019 Standard. The client currently only uses AD/DNS and file services on the 2012 server. My current plan (still forming) is to make the new server a member server and migrate the ~1TB of files (user data, home folders, etc.) to the new server, and get all programs and users going to the new server data-wise, first. Then I plan on updating AD on the 2012 server so I can make the new server an AD/DNS server, moving FSMO roles, checking everything 22 times, and finally demoting the 2012 server (if that's even possible with Foundation). Does 2012 Foundation have one of those 'gentle reminder' functions where it will start rebooting every few days when another AD server is introduced or is that just if FSMO roles are moved? If yes, does anyone know the exact timing of these 'gentle reminders'? Can I even transfer roles or will I need to just turn off the old server and seize the roles once I'm sure everything is good? Does the above plan sound good?

Answer 1

You can refer here to some possible compliance issues.
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-foundation/jj679892(v=ws.11)?redirectedfrom=MSDN#licensing-compliance-error-messages

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

Okay. So it looks like it will shutdown 10 days after the first check and every three days after that.

Answer 3

A better option may be to install hyper-v role (as only role) on host, then stand up two virtual machine gests. One for active directory domain services, and other for file services. For the domain controller the two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

You could start a new thread here to focus on the storage migration.
https://learn.microsoft.com/en-us/answers/topics/windows-server-storage.html

--please don't forget to Accept as answer if the reply is helpful--

Answer 4

Resources won't be an issue is this small environment. Hyper-V, ESX, XenCenter, etc. aren't necessary. A standalone AD/DNS/file server (with good backups and a small secondary AD server) are all that is needed. I will be going through BPAs, and running dcdiags, and other steps to ensure domain health before I start, of course.

My specific reason for doing the file portion first is because of issues that (may) come up with servers that are supposed to be the primary (or only) AD in the forest/domain. SBS comes to mind here. Older versions would actually reboot at standard intervals.

I'll narrow down my questions. This is a single domain forest.

Does Server 2012 Foundation do anything 'weird' (rebooting, for instance) when another AD server is introduced to the forest/domain?
Does Server 2012 Foundation do anything 'weird' (rebooting, for instance) when another AD server is promoted to be master of all the domain roles (schema, domain, RIP, PDC, infra)?
Can Server 2012 Foundation's AD actually be demoted to a just a member server? (if no I'll have to just sieze the roles)