In Place Upgrades

[Tech13]

I want to open up the debate here? 

 

My mantra has always been - clean install of server and migrate roles / files. However with the ever increasing demand for updates / upgrades and lack of downtime I want to reflect on is this still best practice / keep away.

 

What are your thoughts on upgrading from Server 2016 / 2019 to Server 2025?

 

Note: Not for DCs.

 

I look forward to the comments!

[BKGarry]

Never really do them unless totally necessary and even then snapshot/checkpoint backups all the way.

 

For File Servers, the File Server Migration Tool in Windows Admin Centre is excellent, I used it about 2 years ago to move a 2012 file server to 2020, just make sure you have the same amount of partitions/drives available as the original and it will do everything for you. It will even rename the new server the same as the old one and do all the NTFS and Share Permissions. Makes life a lot easier.

[DrCheese]

I tend to do them nowadays, fairly painless (With the exception of DCs of course!)

[TheHyperTechie]

I have always just stuck to the no DC and no SQL rule when it comes to in place upgrades. Never had any issues.

[FragglePete]

I've done them as in place upgrades, with the exception of DCs.  Though I had some issues with the following:

 

- SMTP relay stopped working but this was sort of expected as I know it broke on a 2019 > 2022 upgrade.  It forced me to look at alternative ways for us to deal with this.

 

- Local Certificate Authority Server - just all dissappeared when I did the in place upgrade.  Should have looked into it a bit more first, that you really need to export the the config and import that it a freshly built server for CA's.  Doh!  Thankfully, did a snapshot beforehand and managed to roll back with no issues.

 

Pete

 

[LeMarchand]

OK. Someone with bad knowledge has gotta ask: Why not DCs?

[supportman]

16 minutes ago, LeMarchand said:

OK. Someone with bad knowledge has gotta ask: Why not DCs?

Generally because its safer and easier to build a new server and simply transfer the roles.

[TheHyperTechie]

17 minutes ago, LeMarchand said:

OK. Someone with bad knowledge has gotta ask: Why not DCs?

Easier to spin up a new DC promote it, and re-add all of the roles. Essentially high risk, low reward to in-place them.

[DavR]

2 hours ago, Tech13 said:

However with the ever increasing demand for updates / upgrades and lack of downtime I want to reflect on is this still best practice / keep away.

 

Is there an increased demand for upgrades, though? 

 

Apart from the regular monthly security update, most Microsoft server OSes get 10 years support. Last time I did a server upgrade a few years back, I put in Server 2022, and that's got support til 2031. 

 

I'm still very much of the opinion fresh install and migrate every time. Even with workstations, I rebuild rather than upgrade when I roll out a new OS version (although I realise that is a bit of a luxury), it prevents so many of those niggling faults that come with OS age.

[andy_nic]

I always spin up a new server and migrate over. Done all but 3 servers since i started here, only cause they have a few more years and due to be decommissioned. Mainly as most had held other roles and just had bits left over all over the place. I just like to start fresh, also i find it easier to fix as you build it, while increasing security, rather than in-place possible get random issues.  

[BKGarry]

54 minutes ago, LeMarchand said:

OK. Someone with bad knowledge has gotta ask: Why not DCs?

It is also stated in the Microsoft Documentation/Learn/Whatever they are calling the website now, that the preferred method is to install a new one and migrate rather than in-place upgrade