upgrade process

3 Topics

Question about product key after windows inplace upgrade
Good morning, I have a windows server 2012R2 Standard license: WINDOWS SERVER 2012R2STDROK2CPU / 2VM LENOVO with related product key System is ok and active, all goes fine. I am now attempting to do an inplace upgrade to Windows 2019 server Standard, as the license should also be valid for this product. The inplace upgrade process goes fine but at the end Windows 2019 server is not activated. If I try to activate it, the PRODUCT KEY (of WIN SRV2012R2) is considered invalid: I also tried with this command: DISM /online /Set-Edition:ServerStandard /ProduckKey:XXXXXXXXX /AcceptEula but I catch an error: ERROR: 87 (invalid product key). What I'm missing? Is not possibile to do an inplace upgrade from 2012R2 to 2019 with ROK license? Thank you...
giuseppe_milani_it
Apr 15, 2022 Place Windows Server for IT Pro
4.3KViews
0likes
1Comment
Upgrading 2012 R2 to 2019 Domain Controller / DFRS / DNS / DHCP
Hi All, Looking for some advice been a while since I have had to do an upgrade of the domain controllers but I just want to get people advice on the plan I have put in place to do this: Current setup is as follows: Domain Controller Operating System Functional Level FRS / DFRS Other Functions ROLE DC1 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP PDC / RID POOL MANAGER DC2 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP DC3 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP SCHEMA MASTER / DOMAIN NAMING MASTER DC4 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP INFRASTRUCTURE MASTER The aim is to upgrade all servers to 2019 and upgrade their functional level to 2016R2 and also if possible or easier keep the existing IP's and Names. Things I need to try and avoid if possible: - No downtime (or minimal) - No impact on live services if possible i.e clients etc - In place upgrading So In terms of the high level plan it was as follows: - Upgrade/Migrate to DFRS on all existing DC's - Create 4 new servers running 2019 i.e DCNEW1, DCNEW2, DCNEW3, DCNEW4 install Active directory and add as a DC Member - Migrate the FSMO Roles to the corresponding new server i.e DC1 > DCNEW1 DC2 > DCNEW2 etc etc - Migrate DHCP / DNS to an other server - Demote the old DC's from AD - Rename / Re-IP the new DC's to the old DC's name and IP address. (I believe I will need to demote the new DCs i.e DCNEW1 and move the FSMO Roles to another server, rename and re-ip the DC to DC1 give it the same ip address, add it as a DC member and then move the FSMO roles back onto it and then repeat this process for each other DC) Some questions i have: Do I really need to upgrade to DFRS 1st ?? or can this be avoided? In a very high level plan, does this sound about right? or am I overthinking or missing anything. Is there a much slicker way to achieve my goal? In order to move a DHCP server I recall just exporting the DHCP scopes exporting/importing using "netsh dhcp server export C:\dhcp.txt all" If I want to move DNS is there anything else i need to consider other than installing the DNS Role? How would anyone else approach this? Help appreciated! Thanks
Solved
Samuel_Caunt
Oct 25, 2021 Place Windows Server for IT Pro
12KViews
1like
4Comments
Upgrading from Windows Server 2016 to 2019
Is Windows Server 2019 considered a safe upgrade from Windows Server 2016? Is it like installing a new build in Windows 10 (e.g. going from 1703 to 1709)? or is it more substantial than that? traditionally we haven't done in-place upgrades of Server OS, but wondered if 2019 is different, and more like a build upgrade than an OS upgrade? And is there instructions for doing an upgrade of 2016 to 2019?
jrauman
Sep 15, 2018 Place Windows Server Insiders
11KViews
2likes
5Comments