SIMS Server upgrade

[itgeek]

Hi,

 

I am planning my sims.net server upgrade from 2008 R2 to 2019 including upgrading sql server from 2012 to 2016 (I think this is the current version capita support) . We have sims, FMS, Solus, Docstorage etc installed. I have built a 2019 VM and just wanted to know if anyone has any guides to migrate from 2008 to 2019 and if I should keep the server name the same etc. Also regarding the clients running solus will I have to redeploy this again from the new server?

 

If possible I want them running in parallel and then just make the change when we can get some downtime.

 

Thanks in advance

[jthompson]

I'd recommend arming yourself with whatever installation guides Capita/ESS have available on the support portal, along with installation media (An ISO each for SIMS and SOLUS3, iirc). If you're thinking of migrating the SOLUS3 stuff, rather than starting over, you'd probably need to keep stuff like the server name the same as much as you can. When I did our SIMS migration recently, I started over with the SOLUS3 part as it was for a new domain, so I was needing to redeploy the agents anyway.

 

The Capita knowledge pages should provide some answers:

SOLUS 3 - Is it possible to migrate SOLUS 3 to a new SQL Server?

Manually migrating SIMS and FMS

 

The relevant PDF guides should be available as attahments to articles here https://support.capitasoftware.com/csm?id=kb_article_view&sysparm_article=KB0036895&sys_kb_id=cba2eee51b473854c723edb2b24bcbcd&spa=1. I'd recommend getting those as they'll includes details of things like Windows Firewall rules, Group Policy settings, etc. (maybe this one for SIMS and this one for SOLUS3).

Edited December 15, 2021 by jthompson

[password1234]

Hi,

 

I am planning my sims.net server upgrade from 2008 R2 to 2019 including upgrading sql server from 2012 to 2016 (I think this is the current version capita support) . We have sims, FMS, Solus, Docstorage etc installed. I have built a 2019 VM and just wanted to know if anyone has any guides to migrate from 2008 to 2019 and if I should keep the server name the same etc. Also regarding the clients running solus will I have to redeploy this again from the new server?

 

If possible I want them running in parallel and then just make the change when we can get some downtime.

 

Thanks in advance

 

For upgrading SQL server use the SIMS Migration tool (for FMS/SIMS)which capita provide, dont use DBattach using the Migration tool

 

The rest are just flat files Docstorage / sims files so that can be moved over easily

 

Solus - i generally just tend to reinstall it from scratch and push it out again to all the existing clients

[jthompson]

I'd recommend arming yourself with whatever installation guides Capita/ESS have available on the support portal, along with installation media (An ISO each for SIMS and SOLUS3, iirc). If you're thinking of migrating the SOLUS3 stuff, rather than starting over, you'd probably need to keep stuff like the server name the same as much as you can. When I did our SIMS migration recently, I started over with the SOLUS3 part as it was for a new domain, so I was needing to redeploy the agents anyway.

 

The Capita knowledge pages should provide some answers:

SOLUS 3 - Is it possible to migrate SOLUS 3 to a new SQL Server?

Manually migrating SIMS and FMS

 

The relevant PDF guides should be available as attahments to articles here https://support.capitasoftware.com/csm?id=kb_article_view&sysparm_article=KB0036895&sys_kb_id=cba2eee51b473854c723edb2b24bcbcd&spa=1. I'd recommend getting those as they'll includes details of things like Windows Firewall rules, Group Policy settings, etc. (maybe this one for SIMS and this one for SOLUS3).

 

Updated URLs for the links above, now hosted by ESS rather than Capita.

SOLUS 3 - Is it possible to migrate SOLUS 3 to a new SQL Server?

Manually migrating SIMS and FMS

 

PDF guides available as attachments to articles here . (This one for SIMS and this one for SOLUS3)