+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 54
MIS Systems Thread, SOLUS3 - Upgrade query in Technical; Originally Posted by Mike_1 however when i check the workstation it has upgraded them fine. Hurray!!! Some good news...
  1. #31

    matt40k's Avatar
    Join Date
    Jun 2008
    Location
    Ipswich
    Posts
    4,135
    Thank Post
    352
    Thanked 577 Times in 474 Posts
    Rep Power
    142
    Quote Originally Posted by Mike_1 View Post
    however when i check the workstation it has upgraded them fine.
    Hurray!!! Some good news

  2. #32
    CadlaM's Avatar
    Join Date
    May 2008
    Location
    Hertfordshire
    Posts
    55
    Thank Post
    10
    Thanked 1 Time in 1 Post
    Rep Power
    0
    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 :-)

  3. #33

    teejay's Avatar
    Join Date
    Apr 2008
    Posts
    3,051
    Thank Post
    275
    Thanked 722 Times in 550 Posts
    Rep Power
    326
    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

  4. #34
    Cache's Avatar
    Join Date
    Apr 2008
    Location
    Cumbria
    Posts
    1,116
    Thank Post
    414
    Thanked 149 Times in 147 Posts
    Blog Entries
    3
    Rep Power
    59
    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.

  5. #35
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 487 Times in 375 Posts
    Rep Power
    0
    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?

  6. #36
    skunk's Avatar
    Join Date
    Mar 2006
    Location
    North West
    Posts
    310
    Thank Post
    87
    Thanked 37 Times in 32 Posts
    Rep Power
    28
    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.

  7. Thanks to skunk from:

    russdev (13th January 2012)

  8. #37
    Heebeejeebee's Avatar
    Join Date
    Nov 2006
    Location
    Intergalactic Cruise
    Posts
    1,036
    Thank Post
    68
    Thanked 74 Times in 58 Posts
    Rep Power
    34
    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
    Last edited by Heebeejeebee; 13th January 2012 at 03:25 PM.

  9. Thanks to Heebeejeebee from:

    simongrahamuk (16th January 2012)

  10. #38
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 487 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by Heebeejeebee View Post
    Any ideas?
    Only to uninstall the SOLUS3 UI/DS/Agents, detach and delete the SOLUS3 database and then never ever think about SOLUS3 again!!!

  11. #39
    skunk's Avatar
    Join Date
    Mar 2006
    Location
    North West
    Posts
    310
    Thank Post
    87
    Thanked 37 Times in 32 Posts
    Rep Power
    28
    When is SOLUS4 SP1 out?

  12. Thanks to skunk from:

    Rawns (20th January 2012)

  13. #40
    Cache's Avatar
    Join Date
    Apr 2008
    Location
    Cumbria
    Posts
    1,116
    Thank Post
    414
    Thanked 149 Times in 147 Posts
    Blog Entries
    3
    Rep Power
    59
    Quote Originally Posted by Heebeejeebee View Post
    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).

  14. 2 Thanks to Cache:

    Heebeejeebee (13th January 2012), simongrahamuk (16th January 2012)

  15. #41
    Heebeejeebee's Avatar
    Join Date
    Nov 2006
    Location
    Intergalactic Cruise
    Posts
    1,036
    Thank Post
    68
    Thanked 74 Times in 58 Posts
    Rep Power
    34
    Quote Originally Posted by Cache View Post
    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

  16. #42
    Cache's Avatar
    Join Date
    Apr 2008
    Location
    Cumbria
    Posts
    1,116
    Thank Post
    414
    Thanked 149 Times in 147 Posts
    Blog Entries
    3
    Rep Power
    59
    Quote Originally Posted by Heebeejeebee View Post
    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.

  17. #43
    Griff's Avatar
    Join Date
    Feb 2009
    Location
    Bedfordshire
    Posts
    325
    Thank Post
    113
    Thanked 61 Times in 49 Posts
    Rep Power
    30
    "Typically an upgrade will take around 15 to 20 minutes." .............. whole day gone now waiting for Capita call back...

  18. #44
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 487 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by Griff View Post
    "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.

  19. #45

    Join Date
    Sep 2006
    Location
    London
    Posts
    1,248
    Thank Post
    33
    Thanked 335 Times in 225 Posts
    Rep Power
    75
    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.

SHARE:
+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. [SIMS] Upgrading to SOLUS3
    By prozario in forum MIS Systems
    Replies: 7
    Last Post: 14th December 2011, 09:19 PM
  2. Replies: 14
    Last Post: 14th December 2011, 08:38 PM
  3. DDR3 Memory Upgrade Query
    By flyinghaggis in forum Hardware
    Replies: 0
    Last Post: 23rd March 2011, 03:23 PM
  4. Exchange Server 2003 licensing query
    By tarquel in forum Windows
    Replies: 5
    Last Post: 4th July 2005, 01:56 PM
  5. EZ_GPO usage and helpfulness query
    By tarquel in forum Windows
    Replies: 6
    Last Post: 21st June 2005, 02:00 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •