Rawns

Sorry forgot to ask, what version of SOLUS3 are you guys running? If your still on on 118, have you applied the S3 Hotfix for Target Discovery? There was an issue where SOLUS3 was not picking up online devices correctly and pushing out the updates. Sounds like it could be this issue.

You mean C:\Users\All Users\Capita\Solus3\Deployments? I think the packages are stored in this folder, and then moved into C:\Users\All Users\Capita\Solus3\Deployments\Packages when they are being installed.

Yep, that's what I meant. Sounds like they may already have the update and the message has cleared. Maybe compare some devices that have it to suspect devices that dont, check the above path and try to identify the SIMS workstation package to see if they both have it.

Connect.ini and FMSConnect.ini configured in SOLUS3 too? Also, are all those workstations part of the SIMS Workstation group? They may have already had the update. I've noticed that sometimes, the last message received just vanishes from the message column in the SOLUS3 UI. Also worth doing a 'Check Agent Status' to some of the devices tyou think have not had the package just to ensure they "really" are online and they don't return any offline/firewall/WMI errors.

Deployment packages are stored here on Windows 7: C:\Users\All Users\Capita\Solus3\Packages. Good luck deciphering the Deployment ID's though!!! Our default SIMS.INI is basic: [setup] SIMSDirectory=S:\SIMS Folder=SIMS Applications

Maybe when the first couple of films are out, George Lucas will have a "My god... what have I done?" moment, followed shortly by a gunshot.

For info if any of you are planning on moving SOLUS3 to a new server any time soon, or if you already have done and have SOLUS3 self upgrade failures... The KB ref for Capita's notes is: KB115891 We have had 30+ schools where SOLUS3 has failed to self upgrade from 3.4.118 to 3.5.20. All sites failed at the database stage with the same error and rolled back to 118. I logged a call with Capita and it seems that this is an issue that affects schools where SOLUS3 has been moved from an old server to a new server in the past (all our sites that failed have had SOLSU3 moved to a new server). Capita's SOLUS3 migration guidance originally instructed you to detach the SOLUS3 database on the old server and then attach to the new server. This has now been identified as incorrect and will cause future SOLUS3 database self updates to fail and roll back. You have to in fact detach the database on the old server, and then use the manual installer to install a new, blank database on the new server as the manual installer also installs a number of stored procedures (or something similar). You then have to delete the blank database via management studio and attach the old database. Simply detaching and reattaching does not transfer the stored procedures that are used by SOLUS3 to self upgrade. We've been told to upgrade each of these databases manually using the manual installer, then we should be able to run the rest of the SOLUS3 upgrade using SOLUS3 itself. Capita's new notes reflect this new guidance so be sure to update your instructions.

We've not rolled out yet, but there is a thread about this on SupportNet forum and seems lots of people are coming across this in larger schools with a lot of users. The homepage (specifically the teachers timeline) is killing the SQL server and maxing the CPU out to almost 100%. The front page refreshes at different intervals, not sure how long the new Teacher Timeline refreshes: 1. Attendance Summary - 30 minutes (due to be reduced to 10 minutes for June 09 release - to be confirmed) 2. My Classes Today - 1 minute 3. My Messages - 30 seconds 4. School Diary - 30 minutes 5. Missing Registers - 10 minutes 6. My Favourites - 2 minutes 7. Behaviour Incident Summary - 4 minutes 20 seconds 8. Today's Behaviour Details - 4 minutes 20 seconds 9. Achievement Summary - 3 minutes 45 seconds 10.Today's Achievements - 3 minutes 45 seconds Also, a CR has been raised for this to be addressed: 1304-1183817 Description: Homepage refresh set to refresh too often - Kills SQL Notes: Will Capita stop setting the homepage refresh rates to be too often. Not everyone needs a 1 or 2 minute refresh. Set the default to 30 minutes for everything! Then allow the user to set to a more frequent time if this is required. The only exception I can see is messages but set that to a default of 5 minutes. The current frequency of the refresh is hogging CPU usage on the SQL server on larger schools, which causes timeout errors and problems with using the software.

Jammy Dodgers!!! (With the cream filling)

Who needs SOLUS3? Just ran the updated MSI's via CentraStage against a server with self-upgrade issues and it's upgraded them with no problems. Just need to get the updated agent out there.

Yes, I'm part of the LA support unit. 270+ sites.

kim jong-un looking at things The work of a communist leader is never done...

We do it so we can initially install SOLUS3 in a school through CentraStage. Saves a good deal of manual work!

All our sites had this update as soon as it was released back in may(?). Also if you try to upgrade SOLUS3 to 3.5 without applying this hotfix first, it bricks your SOLUS3 database and you have to restore a backup.

We have a few schools where SOLUS3 is failing to update itself and it rolls back. If I run the MSI's manually on these servers, I can upgrade the database, service and UI without issues, then redeploy the SOLUS3.5 update via SOLUS3 to get the agents up to date. The servers with issues at first glance appear to have UAC enabled. Anyone had issues with SOLUS3 updating itself with UAC left on? Also, what permissions does SOLUS3 need to update itself? presumably it's done as the SYSTEM account so that needs full write permissions to specific SOLUS3 related areas? The failures also seem to be the Database upgrade stage.

Thanks for the response Phil, I have already logged a call about this via SupportNet anyway. The reporting in schools manager has no delay at all. Apply a patch in a school via SOLUS2, then run a activity report in Schools Manager here at the LA and it was right up to date. This report needs to be as accurate. We can't be proactive about looking at failures because of a 4 hour delay, even a 1 hour delay in the report showing the latest status of a deployment.

Only now has the report just updated!!! Still a few showing as "Not deployed" but having to wait over 4 hours for it to partially update is not good!

Well, I'm not sure what's going on with this report but so far it's not working very well! (Thats +1 black mark against SOLUS3.5!). This morning, I authorised the new SOLS3.5.20 release to a number of our LA schools. These all have auto-update enabled for SOLUS3, and are also all set up to e-mail us deployment updates. Not long after authorising, we started getting e-mails in from the schools SOLUS3 environments to inform us that SOLUS3 had been upgraded. I thought I'd put this new SOLUS3 LA report to use as it looked to be a lot more clearer then 100+ e-mails we get. I ran the report and the results show that every site has "Not deployed" the SOLUS3.5 upgrade! It's now been a good few hours since SOLUS3 was upgraded in schools and still this report is showing the wrong information. I assume that the School's SOLUS3 environment report back to Capita's servers to say "SOLUS3.5: Successful", and that when we run this report, it pulls down the info down from Capita's servers so should be accurate and up to date, so I'm baffled as to why the report is inaccurate. Anyone else used this report yet? And more importantly, has it been useful because right now it's looking just as useless as SOLUS3 itself!!

I have awful luck with phone holders for my car, they either break or fall to pieces within weeks. Can anyone recommend a good quality phone holder? I drive a 308 so if anyone else drives one and has a quality phone holder, recommendations would be appreciated!

This only applies to newly added devices that either have an old version of SIMS on them, or if they have had SIMS .net on them previously (think SOLUS3 looks for a SIMS.INI file). You will then need to follow the above to manually "redeploy" the latest SIMS Workstation version to your selected new devices. If you add a brand new machine to the SIMS Workstation channel in SOLUS3 and it's never had a trace of SIMS on it before, SOLUS3 will automatically install SIMS .net it for you without you having to actually do anything providing you have successfully rolled out a SIMS upgrade.

I'm of the opinion that any flavor of SOLUS3 will never ever be the answer.

The thing I'm toying with doing now is overclocking my Desire HD, however I think that the risk is more significant then a standard root. There seem to be alot of posts/threads/ino on the internet about it but some info conflicts with others.

@MatthewL - To reassure you, I recently rooted my Desire HD and loaded JellyTime for Desire HD on it. Had no issues what so ever. I had never rooted a phone before so did lots of reading and research before hand, then decided to take the plunge. I followed this thread for the root: How to Root the HTC Desire HD - xda-developers The process was exactly as shown in the guide and video and worked and worked a treat. Took 10 minutes roughly to complete. I downloaded and installed this ROM which is great: JellyBean - JELLYTIME for DHD/Inspire4g - 4.2.2 R7 Available - xda-developers The only issue with the ROM at the moment is that bluetooth functionality is broken, but a fix should be out soon.

Based from the last of other responses, I'm guessing either others don't have SOLUS3, or don't touch the auto-deployment area! Our SOLUS3 3 auto-deploy time is set around the clock as this upgrading at any time does not impact system use. SIMS, FMS and Discover are set from 19:00-10:00. By 19:00, only the servers are usually on so this gets upgraded automatically (usually without issues), but due to the awful way SOLUS3 agents on workstations seem to fail to check in the next day and auto upgrade if out of date, we decided to roll it over to 10am the following morning in the hope that when workstations are powered on, they get upgraded automatically as it still falls within the auto-deploy time. Once SOLUS3.5 is out in schools, I'll wait and see if this is ironed out (as Capita seem claim claim it is).

For info, IE10 is not supported for SIMS .net reporting until the Summer release.