Jump to content

Recommended Posts

Posted

Sims server is still 2003, any advice on upgrading ?

 

SQL is on separate 2008 r2 box.

 

obviously windows is a fresh install so can i copy SIMS over, i presume i need to install ?

 

What should i make sure i have before I start?

Posted

If you are Capita supported requested the latest SIMS installation ISO on SupportNet. :-)

 

Run SIMSINST.EXE and tick the boxes that this will be a SIMS Server & Document Management server

You'll be asked where the SQL is - put in the existing details if you are not moving it over.

 

Once the installation is complete, copy the docstorage from the old server over the top of the new folder on the new server - so that all of the linked documents, reports, etc work on the new server.

 

Finally check and double check sims.ini and connect.ini files on client machines.

 

Hope that helps!

  • Thanks 1
Posted

no it's fine, but you must ensure that it's changed on the connect.ini which is much easier if you use a centralised one, e.g. one on the Shared SIMS drive.

each client will need to have the new drive mapped, presumably by group policy, but manual or scripts if necessary, so they are looking at the new location.

it's worth checking the local sims.ini files too just in case it's been hardcoded with server name to fix dns / networking issues.

if you're moving to a new 2008 box, then the firewall will need configuring to allow access for SQL else you'll get reason 0 errors.

also once you've installed the new setup, log in and configure the setup for document management service as it will need to know the new location, plus if the server name has changed, you need to alter this in the folder structure.

  • Thanks 1
Posted

isn't the doc management service folder the name of the server running SQL?

 

not sure i was clear in the original post.

 

SQL server is a dedicated SQL server which runs lots of databases not just sims, that stays as is. then there is a 2003 box which is just basically sims file server / doc storage.

 

but thanks i feel much more confident now.

Posted

oh yes, right you are. no need to modify that then.

basically, you're just moving files. i quite often find my test server doesn't have enough room, so just whack on another virtual drive, copy the files over and then delete the old small one. so long as the mapping for S: stays the same, the system doesn't notice. So in your case, you just need to ensure the mappings and references are up to date.

i changed our server name when i went virtual. the biggest hassle is forcing clients to get the new mapped drive. most got it via GP, others, i wrote a batch script and whacked it on another shared drive that hadn't changed and it disconnected and reconnected for them.

 

out of interest, it doesn't link to any other services, that could be affected does it, e.g. FMS, LA audits / returns, B2B, that sort of thing?

  • Thanks 1
Posted

FMS, and the LA uses AnyComms for datatransfer.

 

S: drive mapping doesn't worry me, its in group policy. the local sims.ini isn't a problem as I use app-v and will repackage SIMS when this is done but I'm glad you reminded otherwise i probably would have forgot.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...