Ghostgame

SIMS Autumn 2012 update has been pushed back to 2nd November. This message was posted on SupportNet by Jonathan Wood on 23/10/2012: *** SIMS 2012 Autumn - Change of Date SIMS 2012 Autumn Release Delay An issue has been discovered in our final release candidate for the SIMS 2012 Autumn release. In order to accommodate a fix to this issue and to complete a new round of regression and deployment testing the new revised date will be Friday the 2nd of November. We apologise for any inconvenience that this delay may cause. Regards, Jonathan Wood SIMS Product Manager (Technical and Releases)

Looking at their technical road map: -2003 will not be supported any-more after the Spring 2013 update. -XP (x32) won't be supported after the Summer 2013 update. -Vista after Spring 2013 update. -Also Microsoft Office 2003 won't be supported after Autumn 2012 update. Who knows though, Capita might push some of them back. Link to Capita resources. http://support.capitaes.co.uk/user/resources.asp Search for resource 17910 for the latest SIMS technical roadmap.

A way to speed up SIMS is to make it an exception in the anti-virus. Another way is to check the connect.ini files. If you got a redirect, might be worth changing the connect.ini to point directly to the server. Only downside is if you change the server name for any reason you got to make sure the connect.ini files reflect that change.

Solus3 Agents - Update Environment. Select SIMS in channel. Click Select Computers in SIMS workstations. Add Browse for your computer and add. Save and save. Put in the admin password and login (remember the domain in front of the domain login) Should deploy SIMS automatically, if not deploy the latest SIMS update to that workstation.

There is a massive thread about EYFSP on Capita's Supportnet forums. Its in the Pupil Performance and Assessment forum. Someone just reminded me. Its in the LA forum.

Thats Capita's supportnet for you

The agent version is missing and is what is causing the agent installation to fail. This may need to be logged with Capita.

Logs are in C:\Documents and Settings\All Users\Application Data\Capita\Solus3\Logs for server 2008. C:\ProgramData\Capita\Solus3\Logs for server 2003. You can manually install an agent but I would not recommend it. Only best for when a workstation is not on the same domain or not on site. You can create an installer from System Settings in SOLUS3.

Voted

Stupid question but have you ticked the ‘Trust access to the VBA project object model’ in Excel?

Have you tried re-installing SIMS and FMS?

Be in regedit. Thats where i did all my changes for the workstation GUID. (HKEY_LOCAL_MACHINE - SOFTWARE - CCS - SOLUS3 - Agent -AGENTID) Hope thats what ur after.

Yes it will be fine in the image but it will mean that you have all your SOLUS3 agents on the workstations will have the same GUID. If you don't have a script or something you will have to manually change all the agents GUID's in the registry and in the config on each workstation.

Just please, don't include the SOLUS3 agent in the image for workstations. We had one school do that and it caused no end of problems. It took a good day to sort out and fix.

Whoops. Got that wrong. Yes you do. Sorry

As far as I'm aware no. But it has to be done before the next census otherwise there's a load of errors.

True. When all the machines are on, connected to the server, etc SOLUS3 (usually) works fine as an install, update and monitoring client. The problem is when you have laptops connected as well which half the school staff take home with them or some people turn their computer off at night. The update goes out that night and when they come back the laptops/PC's don't automatically update. That leads to a load of teachers\office staff are trying to assail the office which you call your castle trying to get you to fix their incompatible database problem (usually fixed by deploying the update again). It gets even worse when your a LA. Also SOLUS3 deploying the update to machines that come back online after an update is supposed to be a feature of the SOLUS3 agents.

This has been an ongoing problem with SOLUS3 since an upgrade (3.4.106 or something) However this was supposed to be fixed in 3.4.118 (Capita had assured me this would be fixed in this release ) We haven't got round to doing the update in our area yet for SOLUS and SIMS so we can't say for sure if it has not been fixed. I will be interested to hear what Capita has got to say.

Logged a call with Capita about this problem. They got back to me and said that this issue had been fixed in SOLUS 3.118. Not sure if it has as we are waiting for the next round of SIMS updates before we update SOLUS3 Going to be waiting for the next update and we will see. If not fixed going to poke Capita with the number 3 sized stick.