Rawns Posted January 10, 2012 Posted January 10, 2012 We've spent the last few days in the process of uninstalling SOLUS3 agents in order to get the Autumn release pushed out. Apparently there is a problem with the latest SOLUS3 release in that some machines do not automatically update if they are offline and then get turned on at a later date. If the SOLUS2 update method still worked then this wouldn't be too bad but, if the SOLUS3 agent is installed on a pc, it stops the SOLUS2 method of updating. Removing the SOLUS3 agent is the best way get things back up and running again quickly - if only the agent didn't have to be manually uninstalled from each workstation in order to do this. (There is a remove agent button in SOLUS3 but apparently this was broken with the last update as well - yay for testing.) Glad I'm not the only one annoyed about SIMSLoad not working!!! For info, you may already be aware, but stopping the SOLUS3 Agent service allows SIMSLoad to run normally which means SOLUS2 upgrades shoulfd apply as normal. 1
teejay Posted January 10, 2012 Posted January 10, 2012 Ok, since Capita support are being their usual helpful selves and cannot return my call, any ideas what to do when the SOLUS 3 upgrade sticks on 'in progress' after upgrading 60% of the SIMS Workstations? Cancel deployment is greyed out, have tried restarting the services and rebooting the server. It hasn't updated the deployment log file since last night.
Aethon Posted January 10, 2012 Posted January 10, 2012 For info, you may already be aware, but stopping the SOLUS3 Agent service allows SIMSLoad to run normally which means SOLUS2 upgrades shoulfd apply as normal. Wish someone had told Capita support about this, I was advised to uninstall the agent instead. (I guess if SOLUS3 can't update the computer then the agent will have to be uninstalled at some point but when you have a couple of hundred computers that need SIMS on urgently, a manual uninstall is not the best thing to do!) Ok, since Capita support are being their usual helpful selves and cannot return my call, any ideas what to do when the SOLUS 3 upgrade sticks on 'in progress' after upgrading 60% of the SIMS Workstations? Cancel deployment is greyed out, have tried restarting the services and rebooting the server. It hasn't updated the deployment log file since last night. If I recall correctly, just because it says it's in progress, doesn't mean it is. If the deployment service falls over then this can result in the upgrade displaying In Progress when it's stopped working and it'll never change. (I've a couple of upgrades in this state.) Just try to redeploy the update, or push it out again, to the workstations that haven't received it yet. 1
skunk Posted January 10, 2012 Posted January 10, 2012 Upgraded SOLUS3 to latest version 3.4.103 yesterday..................now it won't talk to its database. FFS! SOLUS2 it is again this time....................
Mike_1 Posted January 10, 2012 Author Posted January 10, 2012 I've also had the issue of the deployment getting stuck 'in progress' and also recently had it apparently fail on a few machines because it's timed out, however when i check the workstation it has upgraded them fine. Glad its not just me having issue's.
matt40k Posted January 10, 2012 Posted January 10, 2012 however when i check the workstation it has upgraded them fine. Hurray!!! Some good news
CadlaM Posted January 12, 2012 Posted January 12, 2012 Got most of the agent deployed, just a handfull of machines not playing the game. As they were some of the first I started attempting deploy to I will work through un-install and delete from environment before re-deploying. Looking better though :-)
teejay Posted January 12, 2012 Posted January 12, 2012 Got the Autumn update deployed finally. Waited 2 1/2 weeks for Capita to find out why it wasn't working, 2 days work for 2 techs and me to get it working on all the machines. Using Solus 2 took about an hour to do the server and then just deployed fine to the workstations with maybe a couple of visits to machines being silly. Not impressed. Now got Discover to do, which is completely refusing to install via Solus 3:mad:
Cache Posted January 12, 2012 Posted January 12, 2012 Deploying the Autumn update was a nightmare this time compared to the ease with which the summer one went out, to the point I phoned up and complained today. In the summer, any machine which was offline, once it came back on the deployment started - this time, this didn't happen on a single machine! My first deployment of the Autumn update stalled on the deploying workstations for some reason, to the point where it didn't even add 2 computers to the Online/Offline list (one of which being our SIMS server) meaning the service had to be restarted, the deployment started again and waited for it to go through. Redeployed to the batch of computers which failed this morning, suffered from the same problem again, some were offline, the deployment stalled and had to be restarted. I didn't have any of these issues with the summer upgrade, the only issue I had which was a pain was that one member of staff had the login screen up when it tried to do the update after coming online and with no redeploy option it was a pain to get it to reinstall. Very disappointed (and fed up) of the latest version of Solus3.
Rawns Posted January 13, 2012 Posted January 13, 2012 I still don't understand why there is no Auto-SOLUS3 upgrade feature in it yet. We can schedule SIMS, FMS and Discover upgrades to deploy automatically now but not SOLUS3 updates?
skunk Posted January 13, 2012 Posted January 13, 2012 2 & 1/2 days since I reported my SOLUS3 problems, still no call back. SOLUS2 upgrade yesterday took approx 5 minutes on the server and about half the clients upgraded automatically when SIMS was started this morning. The other half are having permissions issues (SIMSperm does not like to do what it ought) so we are re-installing via Impero (Now there is a GOOD piece of education software). We use SCCM for all of our other software, why SOLUS3, why!? On the plus side, I was just in Assessment Manager and they have finally added the replace results set feature in the templates. I actually ran around the office cheering. It has been quite a wait. 1
Heebeejeebee Posted January 13, 2012 Posted January 13, 2012 (edited) What a nightmare! Tried to deploy a scheduled update last night (Autumn update). Set it for 18:00 with all machines turned on just in case. After half an hour or so SOLUS decided not to deploy any more so I've now got hundreds of PCs that are showing 'incompatible database' messages and have 'in progress' in the deployment detail. On top of that I can't cancel the deployment and restart because it's greyed out and I can't set a new one off because the old one is still running and it gets set to 'scheduled'. It seems to have got stuck on one machine according to the logs and is still trying - 'Agent ID 34 is already executing an update. target 907 is waiting|AgentAvailable()'. It won't move on to the next and so it's stalled at this point. Have tried restarting the affected PC but no joy there. I have simply copied a working 7.142 SIMS.net folder to all of our teacher / office / admin machines which seems to work OK but I still can't cancel the SOLUS job. Any ideas? Not impressed! edit: NOTE: just copying the SIMS folder over stops Examinations from working. HBJB Edited January 13, 2012 by Heebeejeebee 1
Rawns Posted January 13, 2012 Posted January 13, 2012 Any ideas? Only to uninstall the SOLUS3 UI/DS/Agents, detach and delete the SOLUS3 database and then never ever think about SOLUS3 again!!!
Cache Posted January 13, 2012 Posted January 13, 2012 What a nightmare! Tried to deploy a scheduled update last night (Autumn update). Set it for 18:00 with all machines turned on just in case. After half an hour or so SOLUS decided not to deploy any more so I've now got hundreds of PCs that are showing 'incompatible database' messages and have 'in progress' in the deployment detail. On top of that I can't cancel the deployment and restart because it's greyed out and I can't set a new one off because the old one is still running and it gets set to 'scheduled'. It seems to have got stuck on one machine according to the logs and is still trying - 'Agent ID 34 is already executing an update. target 907 is waiting|AgentAvailable()'. It won't move on to the next and so it's stalled at this point. Have tried restarting the affected PC but no joy there. I have simply copied a working 7.142 SIMS.net folder to all of our teacher / office / admin machines which seems to work OK but I still can't cancel the SOLUS job. Any ideas? Not impressed! edit: NOTE: just copying the SIMS folder over stops Examinations from working. HBJB Bit late - sorry not had chance to look today. Restart the Solus3 Deployment Service on the server which stops all jobs running (but leaves them at their current status) and then start a new deployment which should start deploying out. Then it's a matter of going through once the deployment completes and doing redeploys. (This is the exaqct same issue I had and luckily got Capita at 4.58 on Wednesday night). 2
Heebeejeebee Posted January 13, 2012 Posted January 13, 2012 Restart the Solus3 Deployment Service on the server which stops all jobs running (but leaves them at their current status) and then start a new deployment which should start deploying out. Then it's a matter of going through once the deployment completes and doing redeploys. (This is the exaqct same issue I had and luckily got Capita at 4.58 on Wednesday night). Thanks - I figured that one out but initially the status not changing foxed me a bit. I've re-deployed to the whole lot but what I haven't figured out yet is how to re-deploy to just the failed machines and not the entire lot again (and again). Cheers HBJB
Cache Posted January 14, 2012 Posted January 14, 2012 Thanks - I figured that one out but initially the status not changing foxed me a bit. I've re-deployed to the whole lot but what I haven't figured out yet is how to re-deploy to just the failed machines and not the entire lot again (and again). Cheers HBJB Once a successful (or partially sucessful) deployment status is achieved, if you click on that deployment in your deployment history at the bottom next to the number of machines for each deployment package is a small blue arrow. If you click on that it will take you to a computer list screen at which point what I do is use the unselect all at the bottom, tick the machines that I want to redploy too, click save and then click deploy now (or schedule it). It isn't as intuitive as it could be with the save and then deploy button, I'd rather that deployment scheduling bit was moved to that same screen so you can do it all from there.
Griff Posted January 17, 2012 Posted January 17, 2012 "Typically an upgrade will take around 15 to 20 minutes." .............. whole day gone now waiting for Capita call back...
Rawns Posted January 17, 2012 Posted January 17, 2012 "Typically an upgrade will take around 15 to 20 minutes." .............. whole day gone now waiting for Capita call back... "Typically an upgrade will take around 15 to 20 minutes." .............. if you happen to own a DeLorean or a Tardis. 1
PhilNeal Posted January 17, 2012 Posted January 17, 2012 SOLUS queries are taking a long time to work through as there are many scenarios to deal with. As a result we are falling behind on our SLA in this area. Unfortunately the skill set is very specialised so increasing the team size is not easy. I apologise for the delays.
Rawns Posted January 20, 2012 Posted January 20, 2012 After setting up another SOLUS3 instance, I've just realised that an obvious addition to make things easier would be a browse button to manually navigate to locations like the Binn folder, the DMS server etc.
matt40k Posted January 20, 2012 Posted January 20, 2012 After setting up another SOLUS3 instance, I've just realised that an obvious addition to make things easier would be a browse button to manually navigate to locations like the Binn folder, the DMS server etc. So long as you can still type it in manually - I can c'n'p faster then I can navigate the browse menu 1
Rawns Posted January 20, 2012 Posted January 20, 2012 So long as you can still type it in manually - I can c'n'p faster then I can navigate the browse menu I'd hope so too! That's the way we're doing it at the moment!
Mike_1 Posted May 2, 2012 Author Posted May 2, 2012 (edited) Just thought i'd bump this, is anyone still having issues with machines not upgrading when they come back online? I've not tried the latest April release of S3 to see if it makes any difference but with .107 i am still having this issue, which is a pain when you have laptops off site at the time of upgrade etc Edited May 2, 2012 by Mike_1
matt40k Posted May 2, 2012 Posted May 2, 2012 If they're classed as failed, they won't try again until you redeploy. Where they marked as offline when the first deployment went out?
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