[sims] Joined up thinking?

[localzuk]

We're migrating our SIMS installation to a new server this Easter and have come across an interesting and slightly odd set of conundrums.

 

Firstly - whilst Server 2012 and SQL Server 2012 are supported for the SIMS server and FMS server, SQL 2012 isn't supported for Discover or SOLUS3.

Second - Windows 8 is supported for the client, but IE10 isn't until summer 2013. Whut?

 

It makes things a little complicated. We are having to install a separate SQL 2008 R2 install for Discover and SOLUS3 until it can be migrated later in the year.

 

I'm just wondering why Capita have produced their support roadmap like this?

[LosOjos]

I'm just wondering why Capita have produced their support roadmap like this?

 

Bad communication between teams and lack of unified forward planning I imagine.

 

It annoys me no end the little inconsistencies in SIMS as it's clear that separate teams working on different parts of SIMS just don't communicate well with each other and end up duplicating work (how else could you end up with two different forms for the same task in a .NET environment?)

 

I imagine a similar thing has happened here.

 

Although I must say Win 8 support but no IE10 is funny. Wondering what about IE10 they think will be incompatible though, AFAIK the only interaction SIMS has with the browser is dumping out HTML reports to it isn't it? Shouldn't make a blind bit of difference which browser you're using if that's the case.

[Rawns]

Firstly - whilst Server 2012 and SQL Server 2012 are supported for the SIMS server and FMS server, SQL 2012 isn't supported for Discover or SOLUS3.

 

For info, Windows Server 2012 is not "officially" supported until the SIMS Spring release is applied.

 

I have attempted a test install of install Discover on a SQL 2012 instance (in case it 'kind of' works) but the database refuses to create outright.

 

As for Win 8/IE10 support, that's a fail on Capita's front. You would assume that they have tested SIMS .net in a Windows 8 environment to death including it's use with IE10. I'd assume that it will work, but could encounter an odd issue here and there.

Edited March 21, 2013 by Rawns

[localzuk]

The spring release is due out any time now I believe, so shouldn't be an issue.

[Rawns]

The spring release is due out any time now I believe, so shouldn't be an issue.

 

Capita should release it to us COB tomorrow hopefully. We won't be getting it out in schools though until the end of April.

[localzuk]

Fair enough. Realistically though, there are several using it already without issue. I think we'd survive a month as from what I can tell from my own development work, there aren't as many changes from 2008 R2 to 2012 as there were 2005 -> 2008 etc...

[Rawns]

Second - Windows 8 is supported for the client, but IE10 isn't until summer 2013. Whut?

 

Are you planning on getting Windows 8 out in your environment soon too?

 

Got a Windows 8 test system set up here with SIMS Autumn 2012 Green Abbey running on SQL2012 Express. I've done some limited testing so but experienced no real difficulties.

Edited March 21, 2013 by Rawns

[localzuk]

Are you planning on getting Windows 8 out in your environment soon too?

 

Got a Windows 8 test system here with Green Abbey running on SQL2012. I've done some limited testing ad experienced no major difficulties.

 

Nah, not touching Windows 8 yet. Too many issues with manageability for the 'interface formerly known as Metro', along with proxy issues with it.

[ConradJones]

Nah, not touching Windows 8 yet. Too many issues with manageability for the 'interface formerly known as Metro', along with proxy issues with it.

 

yeh, first time I've actually seriously thought about how to get linux on the desktop. (not going to happen but,)

[psydii]

Have you looked at the support / inter-op caveats with the Office/Server 2013 releases from Microsoft? I'm sticking with 2008 R2/W7 for a few more years, unless some LoB application's 'must have' feature depends on a later version.

[localzuk]

Thing is, I have to migrate to a new server now, so if I can ensure I don't need to do another change next year 2012 is the way forward.

 

Office 2010 + SIMS.net + Server 2012 + SQL 2012 should all work together perfectly. Not moving to Office 2013 yet - we've only just finished migrating to Office 2010!

[psydii]

Fair enough. I think what I was saying is that even the biggest vendors don't necessarily have their interoperability between product versions working on initial release. So some pain is required to be put up with if you adopt early on in the support life-cycle.

 

But hell, we work in IT and we know that already. /redundant post.

[matt40k]

We're migrating our SIMS installation to a new server this Easter and have come across an interesting and slightly odd set of conundrums.

 

Firstly - whilst Server 2012 and SQL Server 2012 are supported for the SIMS server and FMS server, SQL 2012 isn't supported for Discover or SOLUS3.

Second - Windows 8 is supported for the client, but IE10 isn't until summer 2013. Whut?

 

It makes things a little complicated. We are having to install a separate SQL 2008 R2 install for Discover and SOLUS3 until it can be migrated later in the year.

 

I'm just wondering why Capita have produced their support roadmap like this?

 

My guess and I hope I'm wrong, is the fact SOLUS3 and Discover have a fancy MSI creating using WIX which would have - quite rightly so - been given a "you must be running OS X,Y,Z" - as 2012 wasn't around at the time and therefore support - I bet it's not on the list and - I hope this isn't the case - since Capita WIX expert has left, the replacement can't figure out how to add it on - or perhaps add it in - in time for cowboys they call testing, can test that it will work with 2012.

[vikpaw]

@localszuk - go virtual and a change of server is no biggie. especially if you keep the name and ip. if done properly, remapping the S drive by policy should sort most things.

As for IE support - perhaps they don't need to rush, since it's not truly part of windows now is it? If you have to opt-in to use it, they have just chosen not to

[localzuk]

This is our physical -> virtual migration. Its also our SQL Express -> SQL Full migration too.

[vikpaw]

Relax then buddy, in the virtual environment you'll have lots of flexibility. It's really easy to clone machines and bring them up and down, i won't say quickly, because for some reason, my SIMS server takes a few minutes to Power On, but it does in the end.

I'd recommend doing a P2V conversion and create a virtual clone of your current set up. Then you can experiment with making a new server. You could in fact make two, one on each platform, and ship the backups over daily, so if anything goes wrong you can always revert to the other version.

snapshots FTW

[localzuk]

My experience of P2V with MSSQL is not a good one. I'd much prefer to do a clean migration this time - you know how legacy stuff builds up. The existing server has been running for about 6 years now.

[vikpaw]

That's the exact reason i ran a converted box. I wasn't confident legacy stuff wasn't going to stuff it up if i removed it.

To be honest, setting up a new SIMS server is really easy. The hard part is installing windows + sql and patching it up. After that running the install CD and / or restoring a database is SIMSples the only extra fiddling to make it live, is making a share and publishing and open up the firewall ports.

Clean migration shouldn't be a problem either. I wouldn't be concerned about changing to another server version later, it's seriously straight forward. You're better off staying on the tested platform for a bit, in case there are any anomalies as yet undiscovered.