Going from Server 2012r2 to 2019 and in-place upgrade

[TwistedHelixis]

Just planning ahead.

 

Current setup - 1 host with 2 VM's.

VM1 is DC, VM2 is data, SQL, Sims etc.

 

Q1. Next year our server warranty is up. If the primary school do get a new server will I be OK to install 2019 on the new sever and migrate the DC etc from 2012r2 or do I need to install 2016 first?

 

Q2. If they just extend the warranty will I be OK to do an in-place upgrade from 2012r2 to 2019? or do I need to install 2016 first?

 

Anyone completed an in-place upgrade for host and each vm?

[3s-gtech]

Q1 - you don't need to step through versions. Q2 - you shouldn't in-place upgrade DCs, other servers may work fine but results can vary. DCs should be fresh built then promoted. Again, you won't need to go through Server 2016 first.

[Fazza]

Migration is the proffered way of doing it and you should only upgrade if you have to - i.e. you dont have the room to create a new VM etc. This is especially true for DC's, however we had to do an upgrade (rather than a migration) of one of our DC's as when we did the migration it didnt seem to take all the DHCP settings across, it was as if one setting was hidden from view so we had no choice but to upgrade it.

[Tefters]

Awww the good old upgrade vs migration argument... Love this one...

 

Short answer - Migration always preferred

Long answer - In-Place upgrade can work fine at times if you don't have any of the following for migration: system resources, patience, time.

 

If you're a smart person and have the proper backup/restore processes in-place and tested + all your servers backed up the night before then go nuts and upgrade!

I upgraded 6+ servers from 2012r2 to 2016 last time around with little to no issue. Some examples I did - 2x DC's, SCCM, File Server, Cashless Catering, Management/App Servers and a few RDS roles.

Server I have tried and failed miserably - Skype4Business, Print server (but only due to Equitrac software) and a few app servers due to cr*ppy legacy software.

 

In terms of actual issues there were a few little niggles to sort here and there, funnily enough 1 being DHCP scopes when doing the DC's, SCCM I had to redo my PXE deployment point but its all on 1 server so pretty simple there and that was about it.

 

Will I be in-place upgrading this time around? Of-course... It's a lot less time and hassle... DC's will be first up as all I run on them is AD, DHCP and DNS, probably a task for w/c 17th.

Simple process - Upgrade DC first with no FSMO roles, do some tests/checks after and if all good move the FSMO roles and do the other server, if no good then in goes the backup from Veeam. God bless this virtual server world!

 

Warning though - I would not upgrade any Hyper-V hosts at present as there is a major bug where if you do your VM's will not function properly. Still awaiting a fix for this from Microsoft as its to do with the gen type of the VM vs the host.

Edited December 4, 2018 by Tefters

[3s-gtech]

I've upgraded one 2012 R2 Hyper-V host to 2016 as the host was playing up and I thought it would help. The issue was actually a failing UPS! Since then, one Windows update stopped any VMs from starting and had to be uninstalled. Bit weird. Along with SfB, in-place upgrading an Exchange server is beyond unsupported - I don't even think it'll work.

[Tefters]

I've upgraded one 2012 R2 Hyper-V host to 2016 as the host was playing up and I thought it would help. The issue was actually a failing UPS! Since then, one Windows update stopped any VMs from starting and had to be uninstalled. Bit weird. Along with SfB, in-place upgrading an Exchange server is beyond unsupported - I don't even think it'll work.

 

Upgrading Exchange and SfB are defo NO NO's! I did try to fix the issues for fun but gave up upon getting bored.

[TwistedHelixis]

Simple process - Upgrade DC first with no FSMO roles

 

I would be doing the in-place upgrade if they were keeping the old server so 'No FSMO roles' would not be possible as they only have one DC.

[Tefters]

I would be doing the in-place upgrade if they were keeping the old server so 'No FSMO roles' would not be possible as they only have one DC.

 

Yup forgot that bit, in which case make sure your backups are in good order from the night before and YEHA cowboy!

Worst case scenario it goes horribly wrong or lots of minor bugs which will take too long to fix so you just deploy backup and you lost a few hours. Best case scenario it works and your down the pub for an early pint.

 

There is no right or wrong way when it comes to upgrading/migrating + I enjoy having a play at the same time which again doesn't hurt if you have proper backups in place with easy restore.

[mdrabble]

Looking at updating my domain controllers - is it worth doing an in-place upgrade or would it be better do a fresh install and then transfer roles?

[Tefters]

I in-place upgraded 3 weeks ago with no issues.

2x DC’s both with DHCP and DNS on and 1 even had Remote Desktop Licensing Manager on.

 

As long as your backups are good then upgrade is fine.

 

Some things I did and warnings:

 

1. ADPrep from 2019 media (only needs doing once on one DC)

2. Move all FSMO roles to one server (simple powershell command).

3. Upgrade server without FSMO roles, when done fully patch.

4. Move FSMO roles to new server and upgrade other, rinse repeat and then set FSMO roles after all upgrades however you like (I usually leave all FSMO roles on one server)

5. Run Disk Cleanup to clean up old windows folder etc...

6. Upgrade domain level to 2019

7. Pat yourself on the back

 

I had to do nothing with DNS, DHCP or RDS Licensing Manager afterwards.

Also forest functional level doesn’t have an increase to 2019 so sits at 2016...

 

Windows 2019 currently has a custom page file bug however whereby you can’t have a custom page file on another drive other than C:. This was fixed in a patch and then broken again.

Doesn’t bother me that much as windows managed on C: is ok for now and I have enough disk space allocated then will put back to a custom drive like I usually do.

This bug may already be fixed, I haven’t checked since upgrading and patching.

 

Probably worth staying that I in-placed from 2016 to 2019 but can’t see how that would be different for 2012r2 to 2019.

Just note that in 2016 I believed they introduced split/load balanced DHCP scopes instead of doing the old way where you would allocated the whole subnet on both DHCP servers and then do exceptions on each server for half the subnet if that makes sense, or at least that’s how I use to do it pre-2016.

Edited January 24, 2019 by Tefters

[3s-gtech]

That came in with 2012.

[Tefters]

That came in with 2012.

 

Even easier than as should already be prepared!

I lose track of what features come in what versions nowadays...

[Tefters]

The Page File issue in 2019 has now been fixed:-

 

Microsoft support just let me know that the issue has been addressed in KB4476976. I installed it on my test server and can confirm that it is indeed fixed.

It's listed in the notes as:

Addresses an issue that occurs if you create a page file on a drive with FILE_PORTABLE_DEVICE characteristics. The “Windows created a temporary warning” message appears.

https://support.microsoft.com/en-ca/help/4476976/windows-10-update-kb4476976

[TwistedHelixis]

Warning though - I would not upgrade any Hyper-V hosts at present as there is a major bug where if you do your VM's will not function properly. Still awaiting a fix for this from Microsoft as its to do with the gen type of the VM vs the host.

 

Has this been fixed yet?

[Tefters]

Has this been fixed yet?

 

That I don’t know and can’t find any info on at the moment. I would go out on a limb here and say yes due to the amount of time passed since release and such a big bug.

 

If I can whip up a test server fast enough I will try.

[Arthur]

Has this been fixed yet?

Not fixed, but there is a workaround...

 

https://www.edugeek.net/showthread.php?t=203155

[TwistedHelixis]

Out of interest, is there a preferred order to update, host first and then virtual machines or the other way round. I can imagine benifits for both options.

 

Also if everything is upgraded is it possible to update the VM to the latest Gen, I think its 8 or 9 on 2019

[Tefters]

Out of interest, is there a preferred order to update, host first and then virtual machines or the other way round. I can imagine benifits for both options.

 

Also if everything is upgraded is it possible to update the VM to the latest Gen, I think its 8 or 9 on 2019

 

Personally I would do host first than guests. Reason being host requires the most downtime as all VM's have to be off unless in cluster of course.

Than I would update the Gen of the VM and wait for an overnight backup to kick in.

Finally finish off with each individual VM. Technically upgrading each VM would take longer however isn't an overall bigger downtime to users.

 

 

Technically it doesn't matter what order you follow.

[TwistedHelixis]

One last question:0)

 

Do you think a server with SQL + Sims will survive a migration from 2012r2 to 2019?

[Tefters]

One last question:0)

 

Do you think a server with SQL + Sims will survive a migration from 2012r2 to 2019?

 

Yup however I would do it in a multi-stage, first upgrade SQL following Capita method and tool and then upgrade the server.

Again as per my usual blurb, make sure your backups are good so if anything goes wrong you can just restore back with ease (god bless Veeam!).

[aac]

I would advise highly against this. Your SIMS SQL server will not be supported by Capita if running on Windows Server 2019. It would work though, I wish Capita would be quicker at supporting new server platforms because I would like to upgrade mine but see no point now until Capita officially support it. Our LA will not support any server running as either SIMS client or SIMS server because of this. I do however have a server running Windows Server 209 Standard with the SIMS client on it and it works perfectly fine...

[5nowman]

I would advise highly against this. Your SIMS SQL server will not be supported by Capita if running on Windows Server 2019. It would work though, I wish Capita would be quicker at supporting new server platforms because I would like to upgrade mine but see no point now until Capita officially support it. Our LA will not support any server running as either SIMS client or SIMS server because of this. I do however have a server running Windows Server 209 Standard with the SIMS client on it and it works perfectly fine...

 

This is the hurdle I am in too.

 

 

Wanted to boost ahead with Windows Server 2019... capita do not support it.

 

In my opinion it seems like they might not ever support it and carry on development with SIMS and FMS online.

Anyone heard anything recently?

[Tefters]

What Capita say they support and actually do are 2 different things, the same with other companies such as Equitrac print management etc...

 

If I waited for every application to be supported on new OS I would be waiting til the next OS rolls round.

[TwistedHelixis]

This is the issue I have at the primary school today. They are on 2012r2, don't have much money, and want to just jump to server 2019. I am now in the position of needing to install server 2016 on their only server and then do it all again when Crapita support 2019. It's not only the cost but the time that annoys me.

[Tefters]

This is the issue I have at the primary school today. They are on 2012r2, don't have much money, and want to just jump to server 2019. I am now in the position of needing to install server 2016 on their only server and then do it all again when Crapita support 2019. It's not only the cost but the time that annoys me.

I'd install 2019. Just my 2cents.