MIS Systems Thread, Migrating SIMS to a new server in Technical; It's getting high-time to decommission our elderly SIMS server and migrate the whole SIMS kerboodle to a nice new one. ...
12th July 2011, 05:36 PM #1
12th July 2011, 05:48 PM #2
We've had to migrate SIMS to a new server before and it is not too bad.
Basically if you set up a blank server and run the SIMS installer on the S:\ drive of the current server you can tell the machine that it is going to be a server.
You then have to set up where the Document Server and SQL servers are going to be located and follow the prompts through.
You then need to use DB attach to move the database between the servers.
Capita have this documented somewhere to follow through - we used it when we migrated our SIMS roles across - but I can't find it at the moment. I'll keep on looking.
We found if you keep the server name the same, its much eaiser than changing the connect.ini on each machine
Hope this helps
2 Thanks to eddyc:
AlfaTech (13th July 2011), Sephiroth (24th February 2014)
12th July 2011, 11:12 PM #3
I did it at Easter. Will the server move also mean you're changing OS i presume. It doesn't matter, just wondering.
I took the opportunity to change servername, and database name too.
If the connect.ini is redirected to a central one, you only need to change it in one place. We use the path via a mapped drive, so did have to do some scripts to remap the S: drive, but it was no biggie.
I recently wrote up some info on the process in another thread, and others have done the same. The easiest way by far is by downloading the New install ISO from Capita. This way you get a clean setups folder. If you search for SIMS ISO in the forum here, you'll find some useful threads and there are others that discuss moving server and clean installs too.
Don't decommission the old server for a while and until happy the new one works okay for users.
Defo use dbattach to detach from old and reattach to new as eddyc said.
Don't forget to reconfigure the document store location from within SIMS itself.
You may have to allow the SQL ports through on the windows firewall in order for comms to work. The SQL install usually warns about this.
Set up your new backup routines.
The Spring installable ISO is available, so if you use that. Assuming you're already on spring 7.138, then you can move the db over, and then upgrade to summer after - if you dare..
Thanks to vikpaw from:
AlfaTech (13th July 2011)
13th July 2011, 08:12 AM #4
I too have moved SIMS from one box to another on many occasions (the latest being Windows 2008 & SQL 2008 to 2008 R2 for both).
In addition to what @vikpaw says; when you've installed SIMS, moved the DB and changed the location of the DMS in SIMS, import the latest reports (Reports > Import) before restoring your original DocStorage stuff. This will create the new directory structure for docstorage on the new server in which you can copy your files and overwrite what you've just imported.
I too highly recommend using the latest install ISO to make sure you get the latest SIMSInst.EXE file. An old version will cause problems.
Thanks to NorthernSands from:
AlfaTech (13th July 2011)
13th July 2011, 08:35 AM #5
Just to reassure you, I have moved SIMS many times, almost monthly. It is quite simple. Just follow the above and NorthernSand's tip about creating the Docstorage structure is a good one.
Thanks to creese from:
AlfaTech (13th July 2011)
13th July 2011, 09:19 AM #6
Great! Thanks for giving me something to go on (you will all be 'thanked' accordingly). I didn't think it would be to major a task, but it being a critical system we want to get it right first time. Thanks again, if I have further questions I will be back.
14th July 2011, 10:36 PM #7
One of our network manager is moving everything to virtual servers, do I need to nervous or it this a good idea?
14th July 2011, 10:43 PM #8
Been running our MIS system (SIMS) as virtual for some time now and it couldn't be better not a problem at all.
Go for it
15th July 2011, 08:24 AM #9
Remember to put .NET framework V4 (extended) on your new server as future SIMS releases will need it.
15th July 2011, 08:39 AM #10
15th July 2011, 08:46 AM #11
SIMS on a VM is absolutely fine. That's how we run it and I think it's ultimately where most schools will go.
15th July 2011, 09:31 AM #12
Thanks to all who replied. My network manager takes it personally if you question him about everything.
15th July 2011, 09:33 AM #13
That sort of "Manager". I know him well.
Originally Posted by CatherineMay
15th July 2011, 09:40 AM #14
One thing no one has mentioned is that if you do give the server a new name then you need to keep an eye out for the SIMS.ini file on workstations (lives in the windows folder) as well as the connect.ini.
It may have entries which point it to a UNC path for the SIMSDirectory and the SIMSSetupsFolder.
If the paths in the SIMS.ini files are to a mapped drive (eg S:\SIMS and S:\SIMS\Setups) then you shouldn't have any problem with this.
15th July 2011, 09:51 AM #15
Yes. When moving database and servers always check connect.ini, SIMS.ini and docstorage location. Let SIMS create the docstorage file structure by running a report.
Originally Posted by superfletch
By DLW13 in forum Windows Server 2008 R2
Last Post: 11th October 2011, 09:49 AM
By bandgeekmafia78 in forum MIS Systems
Last Post: 28th September 2010, 06:47 AM
By Ric_ in forum MIS Systems
Last Post: 9th August 2008, 07:09 PM
By Oops_my_bad in forum MIS Systems
Last Post: 26th October 2007, 08:18 PM
By PrimaryTech in forum Windows
Last Post: 2nd October 2007, 08:02 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)