+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 26
MIS Systems Thread, Solus 3.... AGAIN! in Technical; Does anybody know when a new release of SOLUS3 is due out, and what they plan to include / fix ...
  1. #1

    Join Date
    Aug 2005
    Location
    Shropshire
    Posts
    296
    Thank Post
    17
    Thanked 11 Times in 8 Posts
    Rep Power
    21

    Solus 3.... AGAIN!

    Does anybody know when a new release of SOLUS3 is due out, and what they plan to include / fix and break in it this time.

    I have NEVER had a successful SIMS update since moving over to Solus3 (The deployment service which was suppose to make things, easier and quicker!) - OK Solus2 wasn't great, but it worked!

    Did I hear at some point that plans for Solus3 were to include some sort of Solus2 backward compatibility mode, where by IF an update hadn't taken place on a workstation, and the user clicks on the SIMS icon, instead of a useful message saying Incompatible Database or some other random message, it would kick start into running the update.

    We are also waiting for functions like the better handling of computer system name changes....

    Why some of these features were not included in the product before it was released to the public at the start I will never know!

    Any feedback, pre-release notes of forthcoming updates etc would be grateful!

    Thanks

    Matt

  2. #2
    achedgy's Avatar
    Join Date
    Apr 2006
    Location
    Somerset
    Posts
    204
    Thank Post
    42
    Thanked 39 Times in 34 Posts
    Rep Power
    24
    Just battling with PC name change now, Solus completely refusing to accept it... Sigh (and the heads PC of course)

  3. #3

    synaesthesia's Avatar
    Join Date
    Jan 2009
    Location
    Northamptonshire
    Posts
    6,221
    Thank Post
    601
    Thanked 1,089 Times in 837 Posts
    Blog Entries
    15
    Rep Power
    485
    Delete from environment, re-add to environment, problem solved (as renames are something we quite often do to get someone up and running quickly). Never had an issue with it here.

    More usefully, what steps have you taken already? Why is it failing, any relevant messages, event logs etc that may shed light?

  4. #4
    MrMat's Avatar
    Join Date
    Jul 2013
    Location
    Solihull
    Posts
    171
    Thank Post
    18
    Thanked 38 Times in 28 Posts
    Rep Power
    28
    As above!

    Alternatively uninstall the agent before the name change, perform name change, re-add machine using new name.

    If the name change has taken place before you had chance to uninstall the agent (and consequently you are now unable to uninstall using the DE because of the name change) you can easily uninstall the agent remotely using CMD/WMIC

    wmic /node:**COMPUTER NAME** product where name="SOLUS 3 Agent" call uninstall /nointeractive

    Once finished, remove the now offline agent from DE and then re-add using new name.

  5. #5

    GREED's Avatar
    Join Date
    Mar 2008
    Location
    Portsmouth
    Posts
    3,110
    Thank Post
    379
    Thanked 389 Times in 314 Posts
    Blog Entries
    8
    Rep Power
    180
    Mr Neal promised on twitter last night new Solus 3 will be great

  6. #6

    Join Date
    Jun 2012
    Location
    Maidstone
    Posts
    55
    Thank Post
    18
    Thanked 7 Times in 5 Posts
    Rep Power
    8
    I know how you feel. First SOLUS 3 deployment yesterday. Been firefighting issues since then. Some PCs that do not have SOLUS installed. Not too much of an issue, but the ones that do have it installed, and then coming up with incompatible database!! At least with SOLUS 2 you can reinstall easily, unlike SOLUS 3 which seems to take its sweet time...

  7. #7

    matt40k's Avatar
    Join Date
    Jun 2008
    Location
    Ipswich
    Posts
    4,442
    Thank Post
    369
    Thanked 650 Times in 531 Posts
    Rep Power
    160
    You forgot the quotes mate, remembers he's a sales guy, so great means face lift. To counter my cynicalism, they do have a good team who's building a better product with every release.

  8. #8

    synaesthesia's Avatar
    Join Date
    Jan 2009
    Location
    Northamptonshire
    Posts
    6,221
    Thank Post
    601
    Thanked 1,089 Times in 837 Posts
    Blog Entries
    15
    Rep Power
    485
    It'll always be good to actually say what the issues are. So often "It's rubbish, it doesn't work" etc when noone's actually said what exactly isn't working, as I said above. May well be something simple. The biggest problem in the majority of Solus deployments will without doubt be the human element, and there's lots of us to help with that!

  9. #9
    SovietRussia's Avatar
    Join Date
    Mar 2013
    Location
    Powys, Wales
    Posts
    684
    Thank Post
    75
    Thanked 156 Times in 121 Posts
    Rep Power
    49
    We have never ever had any issues with Solus 3!

  10. #10
    clareq's Avatar
    Join Date
    Dec 2005
    Location
    Doncaster
    Posts
    744
    Thank Post
    56
    Thanked 190 Times in 126 Posts
    Rep Power
    101
    Why can't we re-install the solus agent? Too often I find a machine where the agent is installed, but the service fails to start. A simple, quick solution should be to simply re-install the agent, but no. We have to wait until the machine isn't in use, uninstall the agent, remove the machine from Solus3, re-add it, hope the agent installs this time. What should have been a great tool, if thought through, is a headache, as I have to check machines for running agents.
    It's not the best antivirus, but look how Sophos handles agents on machines. I just assign the agent by GPO and Sophos knows it's there. puts it in the correct group if it was there before, or puts it in an "unassigned" group if it hasn't seen it previously.

  11. #11
    MrMat's Avatar
    Join Date
    Jul 2013
    Location
    Solihull
    Posts
    171
    Thank Post
    18
    Thanked 38 Times in 28 Posts
    Rep Power
    28
    To be fair though, that sounds more like a permissions/network/settings issue rather than a SOLUS issue. If the service is failing to start I would assume that it's something blocking it or it's been changed to manual start rather than automatic etc. Also, if it's the fact that the service is simply not starting rather than it being completely dead, you can remotely access a machines services (Administrative Tools - Services - Connect to another computer...) to start the service manually (depending on network/permissions again).

  12. #12

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    7,007
    Thank Post
    1,358
    Thanked 1,766 Times in 1,188 Posts
    Blog Entries
    22
    Rep Power
    529
    Quote Originally Posted by GREED View Post
    Mr Neal promised on twitter last night new Solus 3 will be great
    Great we can all relax then
    (Don't suppose any detail was forthcoming)
    Quote Originally Posted by matt40k View Post
    You forgot the quotes mate, remembers he's a sales guy, so great means face lift. To counter my cynicalism, they do have a good team who's building a better product with every release.
    As I've said before, the current version does the job ok, the UI is diabolical but I believe that is getting an overhaul at some point?
    My only issues really are the name change thing and this:
    Quote Originally Posted by clareq View Post
    Why can't we re-install the solus agent? Too often I find a machine where the agent is installed, but the service fails to start. A simple, quick solution should be to simply re-install the agent, but no. We have to wait until the machine isn't in use, uninstall the agent, remove the machine from Solus3, re-add it, hope the agent installs this time. What should have been a great tool, if thought through, is a headache, as I have to check machines for running agents.
    It's not the best antivirus, but look how Sophos handles agents on machines. I just assign the agent by GPO and Sophos knows it's there. puts it in the correct group if it was there before, or puts it in an "unassigned" group if it hasn't seen it previously.
    Both things are just plain daft.

  13. #13
    clareq's Avatar
    Join Date
    Dec 2005
    Location
    Doncaster
    Posts
    744
    Thank Post
    56
    Thanked 190 Times in 126 Posts
    Rep Power
    101
    I do access the services remotely and attempt to restart the service. It fails to do so. All our SIMS machines are subject to the same GPOs, and built in the same way, from the same image, so I doubt very much it's permissions, as it only effects 5-10% of machines. Which machines it affects is random.

  14. #14

    GREED's Avatar
    Join Date
    Mar 2008
    Location
    Portsmouth
    Posts
    3,110
    Thank Post
    379
    Thanked 389 Times in 314 Posts
    Blog Entries
    8
    Rep Power
    180
    Quote Originally Posted by matt40k View Post
    You forgot the quotes mate, remembers he's a sales guy, so great means face lift. To counter my cynicalism, they do have a good team who's building a better product with every release.
    I paraphrased... I know that is what he meant to say (committing Phil now...)!

    Quote Originally Posted by sparkeh View Post
    Great we can all relax then
    (Don't suppose any detail was forthcoming)
    Something about it being 4 clicks and done... that was all. C'mon he has to keep some surprises for BETT!

  15. #15
    Cache's Avatar
    Join Date
    Apr 2008
    Location
    Cumbria
    Posts
    1,257
    Thank Post
    471
    Thanked 181 Times in 178 Posts
    Blog Entries
    3
    Rep Power
    66
    Quote Originally Posted by clareq View Post
    Why can't we re-install the solus agent? Too often I find a machine where the agent is installed, but the service fails to start. A simple, quick solution should be to simply re-install the agent, but no. We have to wait until the machine isn't in use, uninstall the agent, remove the machine from Solus3, re-add it, hope the agent installs this time. What should have been a great tool, if thought through, is a headache, as I have to check machines for running agents.
    It's not the best antivirus, but look how Sophos handles agents on machines. I just assign the agent by GPO and Sophos knows it's there. puts it in the correct group if it was there before, or puts it in an "unassigned" group if it hasn't seen it previously.
    I've managed this in a variety of ways.

    You can try a repair install / manual upgrade if the upgrade has failed to work by exporting the agent installer from Solus 3 and running it on the local pc. Sometimes I've needed to specify a log file location sometimes I haven't, it seems to do as it wants.

    To reinstall a system that isn't working at all, I've taken a copy of the Solus3 program files folder, uninstalled the agent, checked the service has been removed, reinstalled Solus3 manually, stopped the service, overwritten the Solus3 program files folder and restarted the service.

    Amazingly Solus3 repicked this machine up ok, however it is such a faff I don't think I would do it on a regular basis. I only had 5 machines with major Agent problems after doing the 3.6 update.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. [SIMS] Solus 3 again
    By Simcfc73 in forum MIS Systems
    Replies: 3
    Last Post: 4th December 2013, 12:46 PM
  2. [SIMS] Solus 3 (again)
    By Cache in forum MIS Systems
    Replies: 11
    Last Post: 6th June 2011, 10:42 PM
  3. printer scripts again!
    By chrbb in forum Windows
    Replies: 4
    Last Post: 10th February 2006, 12:19 PM
  4. Nurse! The screens! It's happened again!!
    By ajbritton in forum General Chat
    Replies: 11
    Last Post: 5th February 2006, 11:47 AM

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
  •