[sims] Moving SIMS to new server

[vikpaw]

Cool

I've found the odd executable out of date from time to time.

For instance simsinst wouldn't install clients! Satellite setup was old. There have been a couple of threads on it.

I don't see why they differentiate the installable iso then. Why not just make every update CD installable? So it gives you a base and adds updates on top. Or just rebate every time. How hard is it to make the MSI?

[Rawns]

How hard is it to make the MSI?

 

Don't start that debate off again!!

[matt40k]

Just a shame that the Capita installer only Has SQL2008 and not SQL2008R2

 

Last installable I had had SQL 2008 R2 not SQL 2008, so you're setups directory is out-of-date Also remember SOLUS2 is selfish, it only cares about SIMS and FMS installers, it won't update SIMSInst etc... unless you tick the check for CCS infrastructure updates and you've had them deployed to you.

 

RE: Why every update isn't installable - answer would be takes too long to build from what I've heard.

[vikpaw]

All you have to do is run the update ISOs after the installable to get up to date.

So surely I can make one by adding the diff files and running the installers one after the other.

You could train a monkey to do that

[matt40k]

Haha, what is it with you and monkeys? Do you run a pet shop in your spare time and your trying to sell Capita a few? Pretty sure it's a bit more complex then that, that's maybe how you could get an updated setups directory, but I'm pretty sure the simsinst normally gets updated as well, so it won't run old SIMSApplicationsSetup for example. Then you have to update the new SIMS database as well - which is the hard bit, then you have to poke the documentation folk to update date the documentation - who take months to do a find'n'replace on the document to update the version number only to forget that they need to update the screenshots - actually seriously the documentation people are generally pretty good, it's just when they miss something they had to take the shame - and schools always find those pesky spelling mistakes. Part of the reason they put it on the interwebby.

[vikpaw]

I volunteer at the WWF and we're trying out care in the community

 

I'm just saying i don't think it's that hard and 4 months is a long time to do the necessary.

 

Plus it reduces confusion with the user base and makes a consistent, easy to follow procedure to do a new setup or even a disaster recovery setup.

 

I never understood why the KB had the link removed from it. I guess if you sell installation as a service it makes sense.

[matt40k]

Personally, all you should need is MS-SQL installer from Microsoft, SOLUS3 installers. Ideally from your main SOLUS3 system, you should be able to configure a test\dev server as well.

[vikpaw]

Personally, all you should need is MS-SQL installer from Microsoft, SOLUS3 installers. Ideally from your main SOLUS3 system, you should be able to configure a test\dev server as well.

 

Double Meh

[Rawns]

Last installable I had had SQL 2008 R2 not SQL 2008, so you're setups directory is out-of-date Also remember SOLUS2 is selfish, it only cares about SIMS and FMS installers, it won't update SIMSInst etc... unless you tick the check for CCS infrastructure updates and you've had them deployed to you.

 

RE: Why every update isn't installable - answer would be takes too long to build from what I've heard.

 

So much for logical through being right!

 

That's interesting. We did release an infrastructure update a while back (2 years?), so just looked in School Manager and the latest one listed is the 'Summer 2011 Infrastructure Package', no newer one available for us. Think I'll e-mail Capita. In your LA schools manager, what's the latest infrastructure version you have?

[synaesthesia]

So, there's a shedload of info here and elsewhere on actually doing the SIMS side of it.

Any hints, tips and gotchas for SQL Server? Just thinking best practices for it's installation if anything. Obviously can install it with all the defaults, leaving the default instance names etc in place but I'm sure there's more to it than that. Does anyone have a good set of guidelines? Collation, service accounts, if you set up the instance during install or leave SIMSinst to do that for you, what parts you install to C: and what parts go to D:, etc etc.

[vikpaw]

So, there's a shedload of info here and elsewhere on actually doing the SIMS side of it.

Any hints, tips and gotchas for SQL Server? Just thinking best practices for it's installation if anything. Obviously can install it with all the defaults, leaving the default instance names etc in place but I'm sure there's more to it than that. Does anyone have a good set of guidelines? Collation, service accounts, if you set up the instance during install or leave SIMSinst to do that for you, what parts you install to C: and what parts go to D:, etc etc.

cue @jinnantonnixx