asked on
Is it possible to prepare a 2019 Windows PDC completely prior to deployment within a network?
I am attempting to prepare a 2019 Microsoft Server, Standard, to deploy within our small school network. Even with EANS funds our school doesn't need to spend the additional monies to use Hyper-V. There are less than 50 clients and 25 devices connected to the pdc. I am working with two virtual servers, one is the 2019 server, and the other server is a copy of our PDC. Both virtual servers are housed within a Dell Poweredge 440 box. I want to migrate, copy, or move AD Schema, AD, DHCP, DNS. and FSMO roles from the old PDC onto the 2019 virtual server. The old pdc is running 2008R2 Server. I am using VMWare/VSphere version 6 to communicate with the servers. I can ping each server but there is no DNS resolution. I can't add the 2019 server into the domain until I deploy them within our actual network.
and make sure it is using DFS-r for replication of sysvol.
dfsrmig /getmigrationstate
https://docs.microsoft.com/en-us/windows-server/storage/dfs-replication/migrate-sysvol-to-dfsr
2019 will cause you trouble if you are still on ntfrs for sysvol.
you could precede the File server things .....
Not clear how you are trying to implement what you are considering, given I am unclear in trying to determine what is between the lines.
It sounds like you want to take the systemstate of the 2008 and restore it onto the 2019 to then drop the new 2019 as a replacement tot he prior 2008?
the 2008 needs to be adpreped with schema, forest, domain and rodc from the 2019 install disk.
Please be more specific, such as: the host cannot resolve the old DC's name with an NSLookup command.
Run IPConfig /all on the host and on each DC and look at what is set for DNS servers. Post that info and we should be able to help.
I agree with Works2011 about Hyper-V.
ASKER
ASKER
ASKER
ASKER
You could go through a 2012/16 as an intermediate to maintain two DCs while rerieing the 2003.
To migrate from ntfrs to dfsr to then join the 2019, .....
ASKER
not hypervisor will be contending for resources with anything that is running directly on the host.
are you trying to virtualize the servers you have now into the hyper-v?
you could do it using the sysinternals disk2vhdx
perhaps combining many things into a single question you will get answers that might not be cohesive to solve your issue.
lets break out your current environment:
What do you have now: two DCs one primary 2003 one secondary 2008.
you have a new host/hyper-v running 2019
What OS options do you have, you can preinstall VM with OS
Bring the host with Hyper-V on site, join the VMs as member servers, .....
etc.
ASKER
ASKER
ASKER
netdom query fsmo
to confirm that 2008 is the master role
you have to migrate the sysvold from ntfrs to DFS-R to make 2019 joining as a DC possible.
The NTFRS option was removed after 2016.
ASKER
You need to migrate the sysvol from NTFRS to DFSR.
are you looking for a way to JOin the 2019 to the domain and promote it to another DC in the environment OFFLINE?
or alternatively, do you have a way to setup a VPN between where the 2019 is and where the 2008 is?
join over a remote connection?
https://docs.microsoft.com/en-us/windows-server/remote/remote-access/directaccess/directaccess-offline-domain-join
I think it is not available for the 2008 as an option.
see here for more details
https://docs.microsoft.com/en-us/answers/questions/133448/ad-upgrade-from-2008r2-to-2019-or-move-to-new-serv.html
Does this operation work for you, or do you have something different ?
Why not? The IP parameters should (almost always) be set statically on servers.
ASKER
It seems a lot of effort doing in place upgrades, which may fail, rather than the recommended method of transferring the roles.
I would recommend transferring the roles, and then if additional DCs are required, you should have at least a minimum of two, just add another 2019 server and promote to a DC.
Or does the existing 2008R2 server being used as something else other than a DC ?
ASKER
But the fact they cannot communicate is an issue.
What is the host hypervisor os ?
ASKER
ASKER
ASKER
Besides the Dell 440 what do you have?
Unable to connect suggests a configuration issue on the network in the new hyper-V role. or the network connection is not there...
can you ping host from host?
ASKER
I believe Hyper-V is free in 2019 server, why not take advantage of this? (answer depends on the above answer).