In-place upgrade of 2012R2 IIS Server to 2019?

[AJWhite1970]

I know I should burn in $eternal_hell for even thinking this but has anyone in-place upgraded a W2K12R2 server with IIS and PHP directly to Server 2019 yet?

 

Really should do this the long way round but if it in-places without issues then I might just pull the trigger over Christmas...

 

Cheers

Andrew

[3s-gtech]

I've in-placed a couple of IIS servers without issue - last being 2008 R2 to 2012 R2. It's one of the least intimidating ones to do, I'd be pretty confident it'll work fine. Grab a snapshot/backup first and fire away.

[TwistedHelixis]

If you do this can you post back and let me know how it goes. I am considering doing this on all my servers (Host, DC + Data)

[AJWhite1970]

All my data servers have already been done from either 2012R2 or 2016 to 2019 without issue. They have also got rid of that annoying accept screen after the first reboot that was a pia in the 2016 upgrade as you couldn't do it via RDP and had to physically visit each server...

 

I've always been told never in-place a PDC/BDC and have never even tried....

[TwistedHelixis]

I've always been told never in-place a PDC/BDC and have never even tried....

 

I posted the same question a few weeks ago and a few have done the upgrade on DC's

 

http://www.edugeek.net/forums/windows-server-2019/201974-going-server-2012r2-2019-place-upgrade.html

[HPlum78]

A few years ago this would have been a No, but it's a fully supported senario now so there is absolutely no reason not to do in place upgrades. In fact it's now MS's default approche Windows 10.....

 

https://docs.microsoft.com/en-us/windows-server/get-started-19/install-upgrade-migrate-19#in-place-upgrade

[ITGURU]

I've never done an in place upgrade whether it's servers or clients. everything is clean install so can start fresh. if it's physical server with roles then I p2v it and run it virtually then crash the physical server and rebuild from scratch as all documented

[AJWhite1970]

I know I should burn in $eternal_hell for even thinking this but has anyone in-place upgraded a W2K12R2 server with IIS and PHP directly to Server 2019 yet?

 

Really should do this the long way round but if it in-places without issues then I might just pull the trigger over Christmas...

 

Cheers

Andrew

 

Went for it today, all in place upgraded without too much hassle, only issue was ssl certificate wasn’t bonded to 443 in IIS after the upgrade but that was easily resolved (once I’d stopped panicking and thought it through...)

[DrCheese]

Only in place upgraded that caused me headaches recently was going from 2012 r2 to 2016 on our SIMS server - Within a few weeks it died horribly from "REGISTRY ERROR" on bootup. I had to revert the c:\ drive back to 2012 & have recently migrated it over to 2016 in way of a fresh install.

 

Other than that, I've always inplaced and it's been fine. I've just done my DCs and a few less critical servers to 2019 with very little hassle.

[NoviceDev]

Went for it today, all in place upgraded without too much hassle, only issue was ssl certificate wasn’t bonded to 443 in IIS after the upgrade but that was easily resolved (once I’d stopped panicking and thought it through...)

Hi AJWhite1970,

I'm actually going through this exact same issue right where I upgraded from windows server 2012r2 to windows server 2019 and the ssl cerftificate is not bonded to 443 anymore in IIS. How did you resolve this issue? I've been going crazy trying to find the solution