Rawns Posted December 20, 2013 Posted December 20, 2013 (edited) All of our schools have the SIMS Autumn 2013 v1 release. Since SIMS Autumn v2 was released, it appears that Capita have withdrew the SIMS Autumn 1 release for all schools and LA's. Since then, I've noticed an issue in two schools now where devices new have been added into the SIMS Workstation channel. They add successfully, the SOLUS3 agent installs successfully, it reports back to the UI that it has an old version of SIMS installed successfully. The message in the SOLUS3 UI shows the agent has downloaded the SIMS Autumn v1 client release successfully but it does not automatically install it. Doing a manual re-deploy in the UI prompts that "The SIMS Autumn 2013 package has been withdrawn but you can still install it. Do you wish to continue?" and clicking yes installs the SIMS client successfully. It seems that Capita withdrawing the SIMS Autumn 2013 v1 release has stopped auto-installation of the clients in SOLUS3. Can anyone else confirm if this is happening to them as well? We've decided our schools don't need the SIMS Autumn v2 release so don't want to go through a whole other upgrade just to restore the auto-deployment of SIMS clients! Edited December 20, 2013 by Rawns
MrMat Posted December 20, 2013 Posted December 20, 2013 Yup same here mate. I've just replied to your comment on SupportNet! Another job well done by Capita 1
TheScarfedOne Posted December 20, 2013 Posted December 20, 2013 Hmmm, sounds like a solus issue rather than a Sims client/install issue. @PhilNeal...ideas? Im not using solus to deploy so cant test out here to see
Simcfc73 Posted December 20, 2013 Posted December 20, 2013 Thank god I unplug all our PCs over Xmas so I didn't deploy it.
PhilNeal Posted December 21, 2013 Posted December 21, 2013 I think you are asking for a change in the way SOLUS3 behaves. As we have been forced to re-issue, the logic warns that you are about to deploy an out of date copy of SIMS but it will allow you to say yes go ahead. What you want is no warning for a school that has already started rolling out the old version? It would be helpful if you could discuss with Jon Wood the Product Manager. (Secondary schools will almost certainly require V2 hence we have stopped releasing V1 but you can request it.)
Rawns Posted December 22, 2013 Author Posted December 22, 2013 I think you are asking for a change in the way SOLUS3 behaves. As we have been forced to re-issue, the logic warns that you are about to deploy an out of date copy of SIMS but it will allow you to say yes go ahead. What you want is no warning for a school that has already started rolling out the old version? It would be helpful if you could discuss with Jon Wood the Product Manager. (Secondary schools will almost certainly require V2 hence we have stopped releasing V1 but you can request it.) No Phil, the warning is a null point and not an issue at all. The real issue is that Autumn v1 has been pulled and for all schools that have had v1 installed, and only v1, the SIMS client no longer auto installs on new devices added to SOLUS3, presumably because v1 has been pulled. All primary's don't need v2, so we're not releasing it to them, however it means sims is not auto-installing on new devices. So what do we do? Release v2 to them too? Ask schools to manually redeploy every time a new device is added to the environment? This seems more like a bug in SOLUS3, so I'll log a call on support net and email john for clarification.... 2
matt40k Posted December 23, 2013 Posted December 23, 2013 we have stopped releasing V1 but you can request it.) @Rawns you missed this bit. Just request it, then raise it with your account manager\Phil\Jon\anyone who'll listen why the heck when they de-authorised it they didn't have an option to exclude those already with it deployed and if they do, why it wasn't used. And why when you raised it they didn't task a helpdesk grunt with manually re-authorising it to those affect rather then waiting for them to request it. 2
FragglePete Posted December 23, 2013 Posted December 23, 2013 I'm doing the Autumn v2 update from home today (child care issues) - I can't even deploy v2 as it claims not all updates have been downloaded! As far as I can see all updates are downloaded with non waiting. Call open, but who knows what the response time will be at this time of year! Why is it never easy!???! Pete
creese Posted December 23, 2013 Posted December 23, 2013 I'm doing the Autumn v2 update from home today (child care issues) - I can't even deploy v2 as it claims not all updates have been downloaded! As far as I can see all updates are downloaded with non waiting. Call open, but who knows what the response time will be at this time of year! Why is it never easy!???! Pete Having similar issues. checked the INI files and amended. It seems to be working..... sloooooowly.... now.
FragglePete Posted December 23, 2013 Posted December 23, 2013 Having similar issues. checked the INI files and amended. It seems to be working..... sloooooowly.... now. Could you be so kind as to explain what you did? Pete
creese Posted December 23, 2013 Posted December 23, 2013 Just checking all the sims.inis pointed to the same place. Once it is completed I think I need to do some cleaning up. I am using Solus 2, then will copy the Setups folder to other schools.
FragglePete Posted December 23, 2013 Posted December 23, 2013 Just checking all the sims.inis pointed to the same place. Once it is completed I think I need to do some cleaning up. I am using Solus 2, then will copy the Setups folder to other schools. Ah. Solus3 here - it's just refusing to deploy. Pete
Rawns Posted December 23, 2013 Author Posted December 23, 2013 Great stuff. Capita re-authorised SIMS Autumn v1 to us. We had to do a re-authorise to all our SOLUS3 schools via our SOLUS3 LA instance but after checking some, they all now show as 'downloaded' and auto-deply is working again.
MrMat Posted December 23, 2013 Posted December 23, 2013 Ah. Solus3 here - it's just refusing to deploy. Pete What version are you upgrading from mate? Are you trying to go from a Summer release straight to V2 or have you already deployed Autumn V1 and are now going to V2?
FragglePete Posted December 23, 2013 Posted December 23, 2013 What version are you upgrading from mate? Are you trying to go from a Summer release straight to V2 or have you already deployed Autumn V1 and are now going to V2? From Summer to Autumn V2. SIMS 2013 Autumn v1 is not showing in update list anymore, however Database 2013 Autumn is! !!! Pete
danbee Posted December 23, 2013 Posted December 23, 2013 I've managed to get from Summer to 3.62.114 but it will now not get beyond that - tolerance not met! I've tried skipping straight to Autumn 2 (3.62.122) but no luck. Frustrating!!
Rawns Posted December 23, 2013 Author Posted December 23, 2013 I've managed to get from Summer to 3.62.114 but it will now not get beyond that - tolerance not met! I've tried skipping straight to Autumn 2 (3.62.122) but no luck. Frustrating!! We had that at one site. SOLUS3 hung and in the end, we had to manually restore a backup pre-upgrade, then run it again.
speckytecky Posted December 23, 2013 Posted December 23, 2013 Why on earth aren't these things fully tested before release?
FragglePete Posted December 23, 2013 Posted December 23, 2013 Capita connected in. They rebuilt the repository which involved downloading every single update again and this seemed to get things back to life again. The actual database upgrade took a lot longer than normal. Pete
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now