Upgrading sims server in situ

[THERADIOTUBBY]

Hi

 

Currently our Sims SQL and Doc storage is running on a decent Windows server 2012 standard box under Microsoft SQL 2012

 

Whilst checking for updates for the latest processor vulnerabilities it appears microsoft are not going to release a 2012 standard update only a R2 one.

 

How safe is it to upgrade from 2012 to 2012 R2 with Sims in situ?

 

Would it be better to do a whole reinstall to the latest server OS and SQL version?

 

Any advice much appreciated?

[3s-gtech]

If you can snapshot/test or have proven backups, it may be worth a shot. I wouldn't do it without an insurance policy. My experience of in-place upgrading Windows servers has been good, but your mileage may vary!

I would update the OS first, then SQL (that's usually straightforward nowadays).

When it's done, stress test it!

[synaesthesia]

As above, I'm doing exactly that now. However we're going up to 2016, no point upgrading to 2012 R2 and finding yourself in a similar boat when Capita drop support for that.

[deano3693]

As above, I'm doing exactly that now. However we're going up to 2016, no point upgrading to 2012 R2 and finding yourself in a similar boat when Capita drop support for that.

 

I'd be interested in how you get on as i want to do an InPlace upgrade our of SIMS server to 2016 as well!

[markwilfan]

I did an inplace upgrade 2012 R2 to 2016 in the summer. Couldn't face reinstalling sims. All went fine. Mine is a VM though so I snapshotted just in case.

[kingoranks]

Anyone done in place upgrade of the sims server?

[Michael]

Yes - I've done 2008 R2 > 2012 R2 > 2016 without issues. As some have commented, it was a VM, so I could go back if needed.

[3s-gtech]

Yup, did mine this year. 2008 R2 to 2012 R2, though 2016 would have been fine. Only issue I had was that .NET wasn't at the latest version post upgrade so SIMS wouldn't load (not a problem if you install 2019 or maybe 2016). Installing the latest version fixed it fine.

[Ausy]

Our SIMS server was not visualised and running on 6 year old hardware (don't ask), so two weeks ago I p2vd it then did an in place upgrade from 2012 to 2016 followed by an in place upgrade SQL to 2016. No problems at all now running as a VM.

[kingoranks]

Thanks everyone, just what I need to give me the confidence to attempt it, It is a 2008 R2 vm so going to backup and smash it. Just done our Biometric/cashless server. Edited December 9, 2019 by kingoranks

[mavhc]

Upgrade it straight to 2019, by the time that's EOL maybe web sims will be ready

[jezi55]

Im going to do an inplace upgrade from 2016 to 2019 as i have been having issues with hyperv network speeds and the only fix i have found so far is to update the VMs to 2019, i have been told that capita do not officially support server 2019 so if you are going down this route make a backup of your 2016/legacy server encase you need support. Server 2019 should hopefully be supported Feb/March 2020.

[markwilfan]

Im going to do an inplace upgrade from 2016 to 2019 as i have been having issues with hyperv network speeds and the only fix i have found so far is to update the VMs to 2019, i have been told that capita do not officially support server 2019 so if you are going down this route make a backup of your 2016/legacy server encase you need support. Server 2019 should hopefully be supported Feb/March 2020.

Assume you have turned off vmq on all NICs and the vswitch?

[ass17]

I’m hardcore..... I installing fresh side by side

[ITGURU]

I’m hardcore..... I installing fresh side by side

 

I always do clean install of windows and sql then do sims migration server to server.

[kingoranks]

My in place upgrade from 2008 to 2012 test was successful but we will build a new server 2016 .

[denzal2k4]

I've got this to do in the new year is it best to do a copy of the machine in Hyper-V and upgrade that, or just snapshot it first then upgrade that, don't want the SIS ID changing or anything like that , that might break it.

[3s-gtech]

I snapshotted it first, and had to use that first time as the upgrade didn't work and borked. You could do a copy as well, if you have the space.

[DrBeaker]

How are you managing and transfering anything like Groupcall or 3rd party apps to the new server?

[ass17]

How are you managing and transfering anything like Groupcall or 3rd party apps to the new server?

 

I’m having to contact each on for documentation and installers, but what I’m planning on doing is installing them the copying over the group call folder overwriting them, so all the jobs and data re-appear.

[kingoranks]

For all 3rd party, we contact them and get them to assist.

[DrBeaker]

For all 3rd party, we contact them and get them to assist.

 

I’m having to contact each on for documentation and installers, but what I’m planning on doing is installing them the copying over the group call folder overwriting them, so all the jobs and data re-appear.

 

With the amount of 3rd party apps running on the SIMs server, have you ever had any issues with moving everything across? E.g. CPOMs, Inventry, Groupcall, Cunninghams/BioStore off the top of my head run on ours. We migrated our Server last year to a new one, but it took FOREVER to get the 3rd party bits installed and working in order to get everything sorted.

[TwistedHelixis]

For those that have done an in-place upgrade of the OS, did you login as a local admin account to run the upgrade or not, rather than using a domain account? The reason I ask is I have noticed better outcomes when doing similar with Windows 7 to 10 migrations.

[3s-gtech]

I was in as domain admin, which is a member of local admins.

[DrCheese]

I did an inplace from 2012 to 2016 and a week or so later it died horribly from registry corruption - In the end I restored the c:\ drive back to 2012 from backups and left it like that until I could do a fresh install.

 

I wouldn't go to 2019, as Capita don't support that yet. I'm aware that 2019 is basically 2016 anyway, but the last thing you want to do is give capita an excuse not to support...