Rawns Posted December 17, 2013 Posted December 17, 2013 So an interesting issue has come up here. We have a large number of schools now who are fully SOLUS3. A couple of them have now become Academies and have changed their DfE numbers. Capita have update their records so in our LA SOLUS3 instance, the school now have the new DfE details against them. The schools SOLUS3 instance is registered against their old DfE number so when we authorise upgrades to them, they are not being picked up in school. It also seems you cannot just 're-register' the existing School S3 instance with new details. Got a call with Capita and waiting to hear back about how to get around this. In the mean time, keep it in mind if your schools are changing DfE numbers and have SOLUS3...
Ghostgame Posted December 17, 2013 Posted December 17, 2013 Your in for a bit of hurt putting it bluntly. Means you gotta re-register SOLUS3, so you end up with a new Solus3.Keys.DeploymentService.Public file. Means the UI's key does not match the Solus3.Keys.DeploymentService.Public thats on every agent. Means you gotta reinstall each agent on that site. Have also found that you have to do a new reinstall of SOLUS3. If they have stopped using a SIMS module (e.g. FMS) you got to rip out the SQL database for S3 and start again. Good luck, mate. I'm trying to sort out my third school that has become an academy and its a lot of work. This is a known issue with SOLUS3 which hopefully they are starting to look at. 1
Rawns Posted December 17, 2013 Author Posted December 17, 2013 (edited) Your in for a bit of hurt putting it bluntly. Means you gotta re-register SOLUS3, so you end up with a new Solus3.Keys.DeploymentService.Public file. Means the UI's key does not match the Solus3.Keys.DeploymentService.Public thats on every agent. Means you gotta reinstall each agent on that site. Have also found that you have to do a new reinstall of SOLUS3. If they have stopped using a SIMS module (e.g. FMS) you got to rip out the SQL database for S3 and start again. Good luck, mate. I'm trying to sort out my third school that has become an academy and its a lot of work. This is a known issue with SOLUS3 which hopefully they are starting to look at. How have you managed to re-registered SOLUS3 for sites like this? The Establishment and postcode details cant be changed in the UI so you can only re-register it with the existing details which is of no use? Jon Wood spent the day with us last week during the roll-out of our SIMS upgrade and I believed he talked about Capita looking at the ability to change the site details in SOLUS3 via a patch? Rest assured that this is a failing of the software so there is no way I will be removing/reinstalling SOLUS3 for the whole site. Edited December 17, 2013 by Rawns
synaesthesia Posted December 17, 2013 Posted December 17, 2013 It wasn't that bad for us, just took a bit of time re-registering but our capita guys were quite helpful with it.
Ghostgame Posted December 17, 2013 Posted December 17, 2013 In the My Site details re-register with the wrong password. Then you can change the My Site details like postcode and Establishment number. 1
Rawns Posted December 17, 2013 Author Posted December 17, 2013 In the My Site details re-register with the wrong password. Then you can change the My Site details like postcode and Establishment number. I presume aft that, the "mismatch" of the Solus3.Keys.DeploymentService.Public between server and agents kicks in?
Ghostgame Posted December 17, 2013 Posted December 17, 2013 Yep - probably not the best way to do it but probably the fastest way to do it on smaller sites. 1
Rawns Posted December 17, 2013 Author Posted December 17, 2013 Yep - probably not the best way to do it but probably the fastest way to do it on smaller sites. Can you manually copy the Solus3.Keys.DeploymentService.Public from the server onto each workstation after re-registering? Or is it not that simple?
Ghostgame Posted December 17, 2013 Posted December 17, 2013 Yes, that works as long as the agents are picked up by the UI. 1
Rawns Posted December 17, 2013 Author Posted December 17, 2013 Yes, that works as long as the agents are picked up by the UI. Cheers for the help chap. Think I'll wait on Capita in the first instance and see what they say about it. If I get nowhere, I'll give your steps a go and report back.
matt40k Posted December 17, 2013 Posted December 17, 2013 I wonder what @Rawns is buying the S3 devs for Christmas in exchange for the new Solus3.Keys.DeploymentService.Public to be a S3 patch? Hopefully he hasn't forgotten about the M40k tax!! 1
Rawns Posted December 18, 2013 Author Posted December 18, 2013 I wonder what @Rawns is buying the S3 devs for Christmas in exchange for the new Solus3.Keys.DeploymentService.Public to be a S3 patch? Hopefully he hasn't forgotten about the M40k tax!! Coal. Bags and bags of coal. Damp coal too.
Rawns Posted December 23, 2013 Author Posted December 23, 2013 Update: Huzzar! Capita came back promptly with a patch that their Dev ran via SQL Management Studio. It corrected the auth details of the SOLUS3 instance and did not affect the xml keys in any way. Took about 10 minutes for them to address and it's working a treat now. 2
Ghostgame Posted December 23, 2013 Posted December 23, 2013 Cheers, will remember to do that for next time. On the plus side I do now have a school with a squeaky clean S3.
matt40k Posted December 23, 2013 Posted December 23, 2013 Update: Huzzar! Capita came back promptly with a patch that their Dev ran Question is, did you send the damp coal or was it a last minute attempt at getting onto Santa's good list?
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