Rawns

Yea, I'm aware they are part of the ongoing development process. I just choose not to put too much time in it because of the wipes.

I avoided this sale completely which is nice. I ran through my Steam library and reviewed all the games I've rarely plaid/not played at all in my collection. Borderlands 2, Skyrim, Starbound, DayZ, Payday 2, Red Orchestra 2, ARMA3 are just to name a few and you know how many hours you can spend playing just those!!! From now on, I'm only buying games I really REALLY want!

Not played it for a good while. Don't think I will play it 'seriously' either until wipes are no longer needed. Some of the homes people have built and posted on Reddit are incredible! To think of all those hours put in to build top tier epic buildings/ships etc, o0nly to have them wiped must be a right blow!

Is it still true that you are not allowed to use a custom router for Sky broadband access? I've scanned their T's & C's but can only find a statement saying non sky provided router/modems may not work. However some older posts on other support sites say Sky can terminate your broadband access if you use a non Sky provided router. The farther-in-laws net access is flaky at the moment, and I'm fairly sure it's the router. I have a spare but don't want to test it in case Sky do say he's breached their T's & C's. And from what I hear, trying to get a new one from Sky is a mission and a half!

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.

Me and the wife were up at 7am on Sat. Thought 'Sod it...Supermarket'. Got to Sainsburys at 7:30am and the car pack was 3/4 full and the store already had tanoy announcements for extra staff to the checkouts!

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.

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.

Woop! GTA: San Andreas now available on iPad too!

What capture software do you use @CAM?

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....

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!

@Domino - The quality I converted this into is just a 'little' bit bad. Also seems Bandicam recorded my mic REALLY loudly, you lot really quiet and BF not at all, so I removed sound.

A log viewer? Could be useful when battling with the S3 log files.

Humm, it rings a bell. I think they had something like that for an early version of SIMS Discover maybe? A log viewer for Discover? This is SOLUS3's current log file viewer (and it can't be made any larger):

Not sure if anything will come of this but it really bugs me that the log files for SOLUS3 deployments are opened in a 'wrapper' where the text is slightly smaller, you can't maximise the log file and you can't search it unless you save a copy of the log and then open the copy in notepad (or manually browse to the actual logs). The CR is to get the 'View deployment log' and 'View agent deployment log' buttons to load the log files directly into Notepad (or the default text editor). Please vote if you like the idea. CR No is 1312-1264397.

It's either a firewall issue on the client or a DNS issue. Investigate both.

Coal. Bags and bags of coal. Damp coal too.

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.

Can you manually copy the Solus3.Keys.DeploymentService.Public from the server onto each workstation after re-registering? Or is it not that simple?

I presume aft that, the "mismatch" of the Solus3.Keys.DeploymentService.Public between server and agents kicks in?

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.

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...

Once common issue is not closing windows in SIMS. If you open various windows and instead of closing them, open more, SIMS struggles after 10+ windows are open. Monitor it by going to the 'Window' menu from time to time and seeing what windows are still open within SIMS.

It was an accident!!!