Jump to content

Recommended Posts

Posted

We have re-imaged all of our workstations and are now setting them up again. The SOLUS3 agent is installed ok but not checking back in and providing a version number and isn't deploying SIMS or Discover.

 

From the workstation side, you can open the agent, it knows it should have SIMS so you click the deploy button and confirm you want to install, but nothing happens.

 

We have made firewall changes to allow the ports required and turned it off on both client and server-side for testing purposes.

 

With the assistance(?) of the SIMS Support and them pushing the deploy button many times, we have removed the SOLUS3 GUI and Service from the server, deleted and SOLUS3 folders, restarted, re-installed both components, downloaded the Summer release again, re-installed the agents and still they don't install SIMS.

 

Anybody else got any other ideas? Getting desperate as staff are back at the end of the week and SIMS is only on the Exams and Data Managers machines after manually installing for results day last week!

 

Shaun

Posted

2 thoughts. You could confirm end to end connectivity on the ports by using a DOS utility called PCATTCP. You can use this to do a connection test back to the SOLUS server to check you are actually getting connectivity on the port(s) it uses. Worse case, you could export the exe's out of SOLUS and install them via your usual software deployment method using the '/s' silent switch to the exe.

 

Meldrew

Posted
Looks like we have a winner - Have manually installed the .net framework 4.7 on one of the workstations and now the agent is checking in to the server and deploying SIMS.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...