[sims] Solus 3 Agent won't install or update when pushed from SIMS server

[DJ-1701]

I've noticed at the Primary that Solus is refusing to deploy or update when pushing out via the SIMS server. This has been working fine until recently and was wondering if anyone else has been having an issue with it? After adding a computer to the server the Agent window states it is copying the agent installer files, and then fails to communicate, even though the computer is accessible from the server with those credentials.

 

I have managed to install the client by manually installing it from the client directory originally setup by Capita (all be it an older version of Solus), but then it doesn't update from the server (SIMS and FMS deploy fine though).

 

Another strange thing is that I had to open 8080 on the server for the clients to access the document server so reports can run, which didn't need this setting before.

[GC75]

Are they using Sophos Intercept X? If so please check out this thread:

 

http://www.edugeek.net/forums/mis-systems/190013-sophos-intercept-x-preventing-sims-net-install-windows-10-a.html

[DJ-1701]

Are they using Sophos Intercept X? If so please check out this thread:

 

http://www.edugeek.net/forums/mis-systems/190013-sophos-intercept-x-preventing-sims-net-install-windows-10-a.html

 

Good thought, but unfortunately not.

 

In continuing experiments, I have just tested a manual installation of the latest version of Solus on a new machine and that works too.

[GC75]

One problem I sometimes get is that if the IP address of the workstation is duplicated in DNS, if it is I usually clear all records of that IP and on the workstation do an ipconfig /release and then a /renew then try again, I usually find this solves most Solus problems I am having.

[DJ-1701]

One problem I sometimes get is that if the IP address of the workstation is duplicated in DNS, if it is I usually clear all records of that IP and on the workstation do an ipconfig /release and then a /renew then try again, I usually find this solves most Solus problems I am having.

 

Unfortunately that isn't the case either. Only one DNS record per machine and they are correct.

[DJ-1701]

As Solus can't be bothered to push the client out correctly... I have decided to take a leaf out of @Boredguy's book and not bother pushing out from the server console... but instead deploy it with a script which records the GUID in a CSV file for easy reinstallation.

 

http://www.edugeek.net/blogs/dj-1701/2317-deploying-solus-via-powershell-script.html