Chriss31 Posted October 30, 2017 Posted October 30, 2017 Afternoon all Been happily (!) using SOLUS 3 for a few years now. Pushing out the SIMS client is usually not a problem. I do however have one PC which SIMS just will not install onto. The SOLUS 3 client installs fine when deployed via the SIMS server, but then nothing else happens. The PC is sitting in the list of clients, but there is no SIMS version listed and SIMS isn't installing. When I check in with the agent it responds to a status check. I've not seen any errors come up. Any ideas? Never had this issue before. Chriss
caffrey Posted October 30, 2017 Posted October 30, 2017 I get this, it's usually because .net isn't installed (I think it needs 4.7)
hardtailstar Posted October 30, 2017 Posted October 30, 2017 May sound silly but remove and then add it to the domain. Had similar issues and this solved it.
Cache Posted October 30, 2017 Posted October 30, 2017 Another daft thing, but have you assigned it as a SIMS Client target?
Iain.Faulkner Posted October 30, 2017 Posted October 30, 2017 I get this, it's usually because .net isn't installed (I think it needs 4.7) I’ve been having this and installing 4.7 has resolved it
dapaulio Posted October 30, 2017 Posted October 30, 2017 Iv had this from time to time and not being able to tie it down to just one solution. I have carried out many different solutions to the same symptoms Iv had to remove duplicated dns records Remove lines from solus 3 sql table where the agent records are stored. Our sims support drew my attention to this Restart the target pc Reset the password to the account deploying the agent. The symptoms... Doesn’t affect all targets. Add the sims target in deployment manager solus agent deploys successfully but fails to deploy sims. show up as 0.0.0 in the solus 3 client on target pc. If you click on reinstall it does so without any issues. 1
minimoo Posted October 30, 2017 Posted October 30, 2017 I’ve been having this and installing 4.7 has resolved it At the same time - sims have been replying to support cases they do not support .net 4.7. To quote from a support case on the 12th October: "Please be aware that despite .net 4.7 being deployed alongside Windows 10, we cannot offer support for that version of .net framework at this time. Work is being done around getting around this as it's caused numerous issues with several aspects of our products, not just Solus. If you can test this on a non .net 4.7 machine then we can progress this, if this isn't possible then we cannot do much more on this issue as officially it is not supported, therefore I cannot pass this to our 3rd line." 1
minimoo Posted October 30, 2017 Posted October 30, 2017 @Chriss31 / @dapaulio - What method do you use to install the agent ? i.e. are you pushing the agent out from solus - or grabbing the installer and deploying that and letting the agent connect to solus in the first instance? 1
caffrey Posted October 31, 2017 Posted October 31, 2017 Hrrm, interesting about 4.7, I never knew that and I don't *think* we are having issues with those particular PC's
dapaulio Posted October 31, 2017 Posted October 31, 2017 @Chriss31 / @dapaulio - What method do you use to install the agent ? i.e. are you pushing the agent out from solus - or grabbing the installer and deploying that and letting the agent connect to solus in the first instance? Deployed through solus 3 deployment manager here.
Chriss31 Posted November 1, 2017 Author Posted November 1, 2017 Deployed through solus 3 deployment manager here. Likewise. SOLUS client installs fine. I've now updated to the latest .net framework and no luck. I'll try removing it from the domain and re-adding.
Esteban_Child_of_the_Sun Posted November 1, 2017 Posted November 1, 2017 You can always use the manual Discover upgrade on the server and SOLUS3 for the agents afterward by doing a standard deployment which will skip the server as you've already done it manually.
dapaulio Posted November 1, 2017 Posted November 1, 2017 Anything in the computer event viewer. Not completely dismissing a computer issue but I’m guessing the task sequence is not launching for some reason whether that be a target limitation or a server side block. When you reinstall the agent do you reinstall from the agents menu (retaining its guid) or Do you remove it then select it from the targets menu (likely will generate a new guid)
Greg Posted November 1, 2017 Posted November 1, 2017 The workstations need to have .net framework 4.5.2 installed for the agent to report back with the correct version. Solus3 only currently deploys version 4.5 Are firewalls on and are all required ports open and WMI enabled What does it say in the Agent log file on the workstation, that should give you an idea why SIMS isn't installing.
minimoo Posted November 1, 2017 Posted November 1, 2017 I've had a case open with the helpdesk for a while regarding solus not sending out an update after an initial install of the agent - if the agent already has a record in the database. i.e. it's a reinstall. However, note, we use the .bat file from sims (if you hit export agent installer in the software) and the predefined targets functionality in 3.12 to do the initial install. (IMO this should be easiest method as it can be added to a task sequence in mdt for a zero touch install - once capita fix the "deployment on a reinstall" bug). Would really appreciate it if anyone is trying to do exactly the same as that to know - as capita seem to think i'm the only person trying to do this sort of thing ;/
Esteban_Child_of_the_Sun Posted November 2, 2017 Posted November 2, 2017 I've had a case open with the helpdesk for a while regarding solus not sending out an update after an initial install of the agent - if the agent already has a record in the database. i.e. it's a reinstall. However, note, we use the .bat file from sims (if you hit export agent installer in the software) and the predefined targets functionality in 3.12 to do the initial install. (IMO this should be easiest method as it can be added to a task sequence in mdt for a zero touch install - once capita fix the "deployment on a reinstall" bug). Would really appreciate it if anyone is trying to do exactly the same as that to know - as capita seem to think i'm the only person trying to do this sort of thing ;/ I've just started trying to do this for our schools, I've re-written the .bat and javascript files in Powershell and seem to be making some slow progress.
dapaulio Posted November 2, 2017 Posted November 2, 2017 Have capita got an approved deployment method yet? 1
minimoo Posted November 3, 2017 Posted November 3, 2017 I've just started trying to do this for our schools, I've re-written the .bat and javascript files in Powershell and seem to be making some slow progress. My issue with that is support then bounce it back as being unsupported. I customised the .bat file previously to fix some an issue we were having and support refused to escalate a case as we'd modified the file.
Chriss31 Posted November 16, 2017 Author Posted November 16, 2017 To follow up, this appears to be a wider issue. SOLUS 3 just doesn't seem to want to interact with any clients. The only thing I can think has changed is that we are now on a different proxy server, but I have moved all devices over to it now, (SOLUS included). I've removed my own PC from the SOLUS deployment service, but it hasn't uninstalled either the agent or SIMS itself. However when I now try to reinstall the client it says the remote machine cannot be contacted. This was working fine for years. Such a pain.
Chriss31 Posted November 17, 2017 Author Posted November 17, 2017 To follow up, this appears to be a wider issue. SOLUS 3 just doesn't seem to want to interact with any clients. The only thing I can think has changed is that we are now on a different proxy server, but I have moved all devices over to it now, (SOLUS included). I've removed my own PC from the SOLUS deployment service, but it hasn't uninstalled either the agent or SIMS itself. However when I now try to reinstall the client it says the remote machine cannot be contacted. This was working fine for years. Such a pain. Further follow up. All machines currently connected to SOLUS have received their SIMS update automatically today with no issue. It seems to be just an issue with adding/removing new machines and having SIMS install onto them.
Chclark Posted January 17, 2018 Posted January 17, 2018 we are currently having issues with this, Machines already with the agent and sims installed appear to be updating fine with sims\fms. fresh built machine selected add sims machine in targets and it installs the agent then goes no further, also noticed that on these machines we have tried to install to the agent version isn't reporting in solus3, our local sims support are now saying its not suppose to push sims out and solus is just a sims update tool and you have to manually install Sims on new machines.
paulellam Posted January 17, 2018 Posted January 17, 2018 We restart after install of agent, as sometimes it just kicks it into action. We install new stations via Solus, sometimes they work with no problem other times takes a few attempts.,
TwistedHelixis Posted January 17, 2018 Posted January 17, 2018 our local sims support are now saying its not suppose to push sims out lol, under the Solus3 desktop icon it says the word deployment. - - - Updated - - - Most deployment issues I have come across are DNS related
Chclark Posted January 17, 2018 Posted January 17, 2018 I know ive said its been fine for the last couple of years and it recently stopped, will double check for dns issues but strange its only happening now.
Chriss31 Posted January 17, 2018 Author Posted January 17, 2018 our local sims support are now saying its not suppose to push sims out and solus is just a sims update tool and you have to manually install Sims on new machines. What on earth are they talking about? It is of course for deployment of SIMS. I resolved my issues by removing the DNS records for the questionable PC and re-adding it to the domain.
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