MIS Systems Thread, Solus deploy problems in Technical; Morning,
I noticed the release of Autumn last night so thought I would deploy it. It seems fine for the ...
15th November 2011, 09:39 AM #1
Solus deploy problems
I noticed the release of Autumn last night so thought I would deploy it. It seems fine for the computers that are on at the time but any computers which are off fail and don't update. Now I am in the situation where most Sims computers are getting username and password prompts becaise of incompatible database.
The deployment history says 'An existing connection was forcibly closed by the remote host' , the logs says loads of connection attempts failed.
I can't believe they don't have a deploy now or check now for individual machines after you have approved the updates.
And why in gods name do they push the database update seperately even though its in the main update so when you redeploy it messes about skipping these on the server before it starts the clients.
Utter utter garbage.
15th November 2011, 09:45 AM #2
Just seen the redeploy link on Solus 3 but it does all the failed ones.
15th November 2011, 09:56 AM #3
No wait.. it does nothing.
Have I signed up for a Beta release?
The normal way I fix this is run the simsapplication .exe from the Sims driver but that not working.
15th November 2011, 10:11 AM #4
It's not working because SOLUS3 doesn't use the Setups directory - so it doesn't get updated. Log a call with your local support team and they'll help you out.
PS: Sounds like a firewally\AV problem to me.
15th November 2011, 10:16 AM #5
Sorry, its nothing to do with the firewall. Last time a support engineer had to remote in and change the fails on the Solus console to something else so they would deploy. I can't remember which table I need to change or I woudl do it myself.
I have one machine stuck deploying holding everything else up.
I've logged a call and expect a reply within 28 days.
15th November 2011, 10:20 AM #6
Is it a machine it's trying to install the agent on? Or the actual upgrade?
15th November 2011, 10:28 AM #7
its an upgrade.
I have a long list of machines just showing in progress (for over an hour now)
I think they need failing and redeploying in the SQL table.
15th November 2011, 10:44 AM #8
I feel your pain, I wasted about a month of my life wrestling with Solus 3 over last Summer.
Your experience seems to be similar to mine. Solus 2 is going to be canned possibly next year, so
I hope that '3' is going to eventually do what it says on the tin, otherwise we are all going to be right in it.
15th November 2011, 10:49 AM #9
This is where the next SOLUS3 release due out by the end of the month will help - it'll "ping" the workstations to confirm they're still alive.
16th November 2011, 02:32 PM #10
Got it sorted.... was nearly 3 hours on the phone with them but the tech was good. Its a shame now my Solus console is all messed up as he had to deploy the update 9 times to get it working. One computer in particular hated it and stopped it deploying to the rest of the machines which they had to replace a DLL on to get it fixed.
Agreed about the next release of Solus 3 with the pinging... he said its a common issue where the console thinks there is an error on the machine and calls it as a fail when its really just not turned on.
16th November 2011, 02:59 PM #11
SOLUS3, the work of the Devil.
16th November 2011, 03:28 PM #12
Don't even get me started about SOLUS 3! I've got a list of complaints that seem to be ignored in each update. And what about after re-imaging of PCs - what a disaster area! They never pick up the clients again so never get updated. You have to remove them from the SOLUS system and then faff about getting it to re-deploy (alolng with extra fiddling to get Discover working again). Then they all stay listed as 'removed' but with the current client working. Gaaahhh!
I'm dreading the next update to SIMS now. It was so easy before this.
16th November 2011, 03:41 PM #13
I thought that was just SIMS? Seriously, I always knew SOLUS3 wouldn't be smooth, we've been installing it our fully managed schools and the amount of problems we've had and it's not with SIMS, is where the server\workstation wasn't configured right. Like if the SIMS Server is also the DNS server, some of them weren't set to use it's self as a DNS server so you couldn't browse the domain, or the domain had additional (wrong) IP set, or the workstation weren't using the right DNS server - so you couldn't qualify the full DNS name or the firewall wasn't set right. It's all these bit that stop SOLUS3 from working, which isn't Capita fault but it's seen as a SOLUS3 fault as that's the only thing that is affected.
Originally Posted by Rawns
Hopefully SOLUS3 will get the credit when the network bugs disappear at least, regardless I'm not looking forward to doing this for the rest of the schools!!
16th November 2011, 04:17 PM #14
Not sure how Solus 3 can get credit when the old system seemed to work perfectly well. The client checked the version number and if it wasn't right then it installed the updates.
The new system is fine and dandy if it didn't break the connection everytime a database update installed. If there is any problem with the client then the outdated client does not work.. where are we.. 1996? There should be at least an option to tell the user that it needs an update instead of going to the username and password with an incompatible database error.
The heartbeat update will be good but come on.. this should have been put in at the get go not after the horse has bolted and they have annoyed lots of techies.
Not getting at you by the way, just annoyed at another problem.. I really wanted Solus 3 to be the answer... they really should have looked at how others did the updating.. anti-virus software for one inparticular Sophos (not the best av but the console is great)
Thanks to Simcfc73 from:
Rawns (16th November 2011)
16th November 2011, 04:45 PM #15
Agree. It's like capita have said, "this is how you should deploy upgrades" but it does not meet the needs of everyone and in some cases like ours, will cause a vast additional workload. Our schools buy our support and we manage their upgrades for them as part of the service. We release the upgrades to them, we automatically install them and we mop up any failures for them. The work load is minimal and the process works a treat with minimum impact in the schools.
The thought of having to manual install SOLUS3 into 270 odd schools is a nightmare! It's something myself and my colleague share between us so most of our time will be spent on it. We're using the opportunity of Discover requests from School to get it out there initally, but when it becomes necessary to get SOLUS3 out to every school and move SIMS and FMS onto it, it's going to be awful getting the agents out to all relevant PC's, ensuring that every SIMS/FMS/Discover device has an agent, ensuring new/imaged/rebuilt PC's are re-added to the SOLUS3 environment to ensure they don't miss out on any upgrades etc! Most of the info you put into SOLUS3 is already in the SIMS.INI file! Why Can't SOLUS3 pull the info from there to save a bit of work?
We will have a Central SOLUS3 UI here to authorise upgrades to Schools, but as far as I can see, there is no suitable report in SOLUS3 to check on the status of any released upgrades. SOLUS2's reporting function worked a treat and gives a clear view of how the deployment went. I really hope there is something like that added to S3 soon.
By local-lad-steve in forum O/S Deployment
Last Post: 22nd March 2010, 05:30 PM
By paulmc in forum Network and Classroom Management
Last Post: 9th March 2010, 04:13 PM
By SteveCIS in forum Windows Server 2000/2003
Last Post: 27th November 2009, 09:40 AM
By cheredenine in forum Windows
Last Post: 30th July 2008, 12:49 PM
By Southwell in forum Educational Software
Last Post: 18th July 2008, 04:27 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)