kennysarmy Posted February 26, 2016 Posted February 26, 2016 I've just been sent the install files from our LEA and the following documents to read through: SOLUS³ for System Administrators : Document SOLUS3SysAdmin3.9/HBK/060315/NR SOLUS³ Installation and Configuration : Document SOLUSIC3.8/HBK/121114/NR But before I get too deep in to the reading, can anyone advise any gotchas to watch out for when upgrading from Solus 2 to Solus 3? Seems I have to have all this running before 1st April!
splattthecat Posted February 26, 2016 Posted February 26, 2016 Make sure all of the pre-requisites are in place first, especially the firewall rules, also that there are no issues with DNS. These are the two leading causes of issues wit the schools we support.
kennysarmy Posted February 26, 2016 Author Posted February 26, 2016 Stupid question but is SOLUS 3 typically installed on the SIMS Server? Or do you create a new "deployment" server?
hardtailstar Posted February 26, 2016 Posted February 26, 2016 Stupid question but is SOLUS 3 typically installed on the SIMS Server? Or do you create a new "deployment" server? Ours is on our sims server 1
Boredguy Posted February 26, 2016 Posted February 26, 2016 Typically the Solus 3 deployment server is installed on your SIMS server for simplicity 1
psydii Posted February 26, 2016 Posted February 26, 2016 If you have staff wireless laptops, which may or may not be on/in at a given moment, then prepare to weep in frustration as you try to get Solus3 on to them. Also for us the Solus3 service on the server tended to fail under the load of a large deployment of solus3 clients. Once you've got it everywhere, it isn't too horrific, unless you go re-imaging machines.
kennysarmy Posted February 26, 2016 Author Posted February 26, 2016 If you have staff wireless laptops, which may or may not be on/in at a given moment, then prepare to weep in frustration as you try to get Solus3 on to them. Also for us the Solus3 service on the server tended to fail under the load of a large deployment of solus3 clients. Once you've got it everywhere, it isn't too horrific, unless you go re-imaging machines. Thankfully it's 99% fixed PC's in offices and classrooms. My only concern is we are pretty hot on power management so PC's are forced in to sleep mode if left unattended, this is for admin areas and classrooms.
kennysarmy Posted February 26, 2016 Author Posted February 26, 2016 With regards to the "Update Repository" My Server currently has C:\ 54Gb free S:\ 104Gb free I was just going to create a new folder on S:\ called "Update Repository", I believe it then needs to be shared, can this be a hidden share?
PhilNeal Posted February 26, 2016 Posted February 26, 2016 The last release supported via S2 is Spring 16. You have until the summer release to move to S3 1
sparkeh Posted February 27, 2016 Posted February 27, 2016 Make sure your DNS is spot on else you are in for some pain. Make sure that you understand the UI, it's really, really awful. 4
TomHD Posted February 27, 2016 Posted February 27, 2016 (edited) unless you go re-imaging machines. I had problems with the agent not auto deploying after reimaging some machines. Something to look out for after the installation. And as others mention, the UI isn't great till you've been sat with it for some time. Time doesn't make the UI any better just you get better at understanding it [emoji57] Edited February 27, 2016 by TomHD 1
sparkeh Posted February 27, 2016 Posted February 27, 2016 I had problems with the agent not auto deploying after reimaging some machines. Something to look out for after the installation. And as others mention, the UI isn't great till you've been sat with it for some time. Time doesn't make the UI any better just you get better at understanding it [emoji57] Yeah I always remove the agent before reimaging and redeploy after reimaging. It's not difficult for S3 to get itself in a mess. 1
Gibson335 Posted March 10, 2016 Posted March 10, 2016 Has anyone else seen a marked difference in CPU use? Since Solus3 went on, our CPU has started running markedly higher. I'm told there should be no real difference, but my understanding is that the server and the clients communicate at regular intervals, so was wondering whether this might be the cause. Thanks for the tip above by the way, especially regards reimaging clients. 1
ITGURU Posted March 10, 2016 Posted March 10, 2016 Stupid question but is SOLUS 3 typically installed on the SIMS Server? Or do you create a new "deployment" server? SOLUS 3 is installed on the SIMS server, then I have installed just the UI on my workstation so can deploy/manage the remote agents from that rather than having to keep logging on to the server. Reluctant to use SOLUS 3 years ago, but the product seems to have been improved. 1
Greg Posted March 11, 2016 Posted March 11, 2016 All the above is good. Make sure WMI is running on the clients If firewalls are on and you have problems installing then make sure ports and WMI are allowed And DNS...
Meldrew Posted March 12, 2016 Posted March 12, 2016 If you have staff wireless laptops, which may or may not be on/in at a given moment, then prepare to weep in frustration as you try to get Solus3 on to them. Also for us the Solus3 service on the server tended to fail under the load of a large deployment of solus3 clients. Once you've got it everywhere, it isn't too horrific, unless you go re-imaging machines. We have this problem, so we don't install the agent anywhere except the SIMS server. We then use our existing software deployment solution to push out the installer for the update, obtainable via the 'export' button in SOLUS3. Meldrew.
sparkeh Posted March 12, 2016 Posted March 12, 2016 We have this problem, so we don't install the agent anywhere except the SIMS server. We then use our existing software deployment solution to push out the installer for the update, obtainable via the 'export' button in SOLUS3. Meldrew. Interesting, we don't have any issues with laptops. When they connect they get the update as expected.
Barcrest Posted March 15, 2016 Posted March 15, 2016 Interesting, we don't have any issues with laptops. When they connect they get the update as expected. I suspect the issue is the name resolving back to 2 IP addresses if the laptop was built wired and then used wireless.
sparkeh Posted March 15, 2016 Posted March 15, 2016 I suspect the issue is the name resolving back to 2 IP addresses if the laptop was built wired and then used wireless. Ah yes that is a good point. S3 can easily get in a mess due to way it uses DNS.
kennysarmy Posted March 15, 2016 Author Posted March 15, 2016 In the SOLUS³ Installation Checklist it states that: Framework 4.0 must be installed on all devices in the Deployment Environment. I take this to mean any version of the Microsoft .NET 4 framework - from 4 to 4.5 - is this correct?
Barcrest Posted March 15, 2016 Posted March 15, 2016 (edited) I believe so, I have 4.6 on my machine and I have the Solus client installed and working. Edited March 15, 2016 by Barcrest
DaveJ2717uk Posted March 16, 2016 Posted March 16, 2016 Yeah I always remove the agent before reimaging and redeploy after reimaging. It's not difficult for S3 to get itself in a mess. Question from a none sims user, currently!, (though possibly soon to be ) If the PC is past the point where you can access it to remove the agent, are you in for all kinds of pain? Surely in this day and age re-imaging and giving the PC/Laptop the same name and reinstalling the agent would be enough. Or am I being to logical?
bobsmith Posted March 16, 2016 Posted March 16, 2016 from my now slightly distant experience of deploying solus 3 for the first time, what each machine gets is a unique id assigned by solus, if the machine screws up and you rebuild it then solus will "forget" about it. Naming it the same won't reinstate the uid. You'll have to re-add it through the Solus - AD interface. Could be wrong though 1
TomHD Posted March 16, 2016 Posted March 16, 2016 (edited) are you in for all kinds of pain? Not really just that it won't redeploy without some intervention from yourself. The actual redeployment is a few clicks once you know what you're doing @bobsmith says about the ID and SOLUS forgetting the machine sounds right Edited March 16, 2016 by TomHD 1
hyb80 Posted March 16, 2016 Posted March 16, 2016 Apologies if this has been mentioned above, I scanned it quickly Huge one for us, depending on your version of SQl but we had to enable compatibility mode in SQL 2014 to SQL 2012 mode. Reports just hung until then
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