Yes, to both. You're welcome.
--please don't forget to Accept as answer if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hey all
I'm planning to promote a Windows 2019 DC (And another one shortly thereafter) in an isolated Forest that currently is Schema version 47 (Windows 2008R2)
There's only one other DC in this current setup, Windows 2008 R2, so there is currently no resilience.
Was hoping you could help me with some direction? Couple questions:
That is probably a silly question, but as I only have the 1 existing DC server in this isolated environment ive just inherited, I'm being extra cautious.
2. What files do I need in order to run ADPrep and DomainPrep? Do I need the entire 5GB ISO copied over or could I just copy over the ADPrep folder.....
The server is a few hundred miles away and on a fairly restricted network, so I need to plan this out.
I can probably map a drive with the files onto the server from a jump off location, but I just want to account for any issues I could have if I lost OS access. In that event I can get on via ILO but would ideally like the relevant ADPREP files to hand, no obvious reason other than having them there.
Any help appreciated folks
Coop
Yes, to both. You're welcome.
--please don't forget to Accept as answer if the reply is helpful--
Adprep has been a part of domain controller promotion for some time now so nothing extra needs to be done.
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.
--please don't forget to Accept as answer if the reply is helpful--