SteveB_NI Posted May 21, 2019 Posted May 21, 2019 Currently I have 3 x servers running Server 2008R2. 2 have A/Directory, DNS, and DHCP roles, and 1 has WSUS & A/Virus role, and the 3rd is just used for print role. I have bought a new server complete with 2 SSDs (400GB each) and 4 HDDs (1 TB each). I plan to install Server 2019, and have several Virtual servers - maybe 3, replicating the current set up. Advice required for the following: 1. Would I be best recreating the network on the new server, whilst keeping the existing one working with no interruption... as in, create the network again from scratch. (I inherited this one so would be a learning curve) 2. If I were to integrate this one into our current environment, what would the idea plan of action be? At present none of my client workstations are Windows 10 so I'm thinking starting afresh may be the way forward and then take the summer to rebuild the workstations onto the new network... but I'm hoping for advice before doing this! Thanks for all your help!
k-strider Posted May 21, 2019 Posted May 21, 2019 If you have lots of Users and Computers then maybe migration would be more seamless from a users persective. if youre estate is small and your happy to reset everything up then it might be neater for you to start again.
k-strider Posted May 21, 2019 Posted May 21, 2019 (edited) if you go down the migration route... create the new Hyper-V server add it to the domain... add a new Virtual and Promote it to a DC with DNS.... Move the FSMO Roles to the new DC... move the DHCP role acoross you can backup and restore the DB quite easily change DNS to point to new server on anything thats static and as options in DHCP... demote the old DC.... then create new servers and move other stuff... Edit: going forward you probably want 2 DCs Edited May 21, 2019 by k-strider
SteveB_NI Posted May 21, 2019 Author Posted May 21, 2019 if you go down the migration route... create the new Hyper-V server add it to the domain... add a new Virtual and Promote it to a DC with DNS.... Move the FSMO Roles to the new DC... move the DHCP role acoross you can backup and restore the DB quite easily change DNS to point to new server on anything thats static and as options in DHCP... demote the old DC.... then create new servers and move other stuff... Edit: going forward you probably want 2 DCs Thanks - would it be ok to have this new server on Server 2019, and promote it to a DC alongside the others being Server 2008r2? Wont that cause any issues?
k-strider Posted May 21, 2019 Posted May 21, 2019 (edited) if you choose to migrate that means you will have 2 DCs in the domain... you add it as a second DC then it will replicate AD over so both are domain controlers... then once it has replicated across you can then move all the FSMO Roles over to the new 2019 DC then demote the old one yes 2008R2 and 2019 DCs can co-exist... once you have got rid of the 2008R2 you can raise the Forest and Domain Function level up to 2019 you cant have DCs lower OS version than the Domain or Forest level. ill try and find some guides... ive done it to often now over the years... its second nature... Edit i just did some googling and you will need to enable SMB 1.0 on the 2019 server to add it to a 2008R2 domain which seems a bit wiered as 2008R2 supports SMB 2 - but once your all migrated you definatley want to turn that back off on all of your servers and workstations.. you shouldnt need SMB1 anymore... https://serverfault.com/questions/955401/how-to-add-windows-2019-server-to-2008-r2-and-migrate-dc Edited May 21, 2019 by k-strider 1
k-strider Posted May 21, 2019 Posted May 21, 2019 This is for Server 2016 Core but the process will be very similar for 2019 https://www.ntweekly.com/2017/09/27/promote-windows-server-core-2016-domain-controller-using-powershell/ 1
k-strider Posted May 21, 2019 Posted May 21, 2019 Transfer FSMO Roles https://www.dtonias.com/transfer-fsmo-roles-domain-controller/ 1
k-strider Posted May 21, 2019 Posted May 21, 2019 export DHCP database https://support.microsoft.com/en-gb/help/281626/how-to-use-the-netsh-utility-to-export-and-import-dhcp-scopes 2
k-strider Posted May 21, 2019 Posted May 21, 2019 demote 2008R2 Decommission (Uninstall) a Windows 2008 R2 Domain Controller | TekBloq i forgot to mention make sure you make your 2019 a GC (Global Catalogue) when you promote it. i make all my DCs (i have 3) GCs 1
TJ-Diggers Posted May 21, 2019 Posted May 21, 2019 For the host I would use Hyper-V Server 2016 and install core edition as it is lighte! Alternatively wait for 2019 to be released.
Arthur Posted May 21, 2019 Posted May 21, 2019 Alternatively wait for 2019 to be released. Didn't Windows Server 2019 get released last year?
TJ-Diggers Posted May 21, 2019 Posted May 21, 2019 Didn't Windows Server 2019 get released last year? Yes it did but I am on about Windows Hyper-V Server 2019. This is its own OS and meant for Host. This is different to installing windows server 2019 and then installing the Hyper-V role
SteveB_NI Posted May 30, 2019 Author Posted May 30, 2019 if you choose to migrate that means you will have 2 DCs in the domain... you add it as a second DC then it will replicate AD over so both are domain controlers... then once it has replicated across you can then move all the FSMO Roles over to the new 2019 DC then demote the old one yes 2008R2 and 2019 DCs can co-exist... once you have got rid of the 2008R2 you can raise the Forest and Domain Function level up to 2019 you cant have DCs lower OS version than the Domain or Forest level. ill try and find some guides... ive done it to often now over the years... its second nature... Edit i just did some googling and you will need to enable SMB 1.0 on the 2019 server to add it to a 2008R2 domain which seems a bit wiered as 2008R2 supports SMB 2 - but once your all migrated you definatley want to turn that back off on all of your servers and workstations.. you shouldnt need SMB1 anymore... https://serverfault.com/questions/955401/how-to-add-windows-2019-server-to-2008-r2-and-migrate-dc Thank you very much @k-strider for the advice & helpful documentation. Will read into that and follow your advice!
kingoranks Posted June 12, 2019 Posted June 12, 2019 Hey Guys, just been reading this fab thread. I am looking at upgrading some server 2008 too. Thanks for all your contributions, I will shout if I need help
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now