SIMS Client won't launch on SIMS Server - SOLUS 3

[truebluesteve]

Hi All

 

I've just upgraded to SOLUS 3 (yay ) and it mostly seems to be working however the SIMS client on the SIMS server doesn't want to launch. The icon appears on the task bar very briefly and then disappears and I can't see anything in task manager etc. Any suggestions as to what might be the issue here?

 

As an aside can someone confirm or deny the following?

 

1. Any devices that dont have the SOLUS 3 agent installed (e.g. laptops that are out of school) will not be able to upgrade to the latest version until the agent is installed? I.e. they can't use SOLUS 2 as it were.

 

2. Any devices that do have the agent installed but are offline when the update is deployed will not get the update unless it is deployed again? Or will the agent check?

 

Thanks!

 

Steve

[superfletch]

the SIMS client on the SIMS server doesn't want to launch. The icon appears on the task bar very briefly and then disappears and I can't see anything in task manager etc. Any suggestions as to what might be the issue here?

 

I think it is something SIMS Infrastructure related - give it a reboot first and see if that's it. Otherwise possibly UAC - try right click Run as Admin for a test - you could also try removing the reference to "SIMSLoad.exe" from the shortcut.

 

1. Any devices that dont have the SOLUS 3 agent installed (e.g. laptops that are out of school) will not be able to upgrade to the latest version until the agent is installed? I.e. they can't use SOLUS 2 as it were.

 

If you set SOLUS 3 to auto extract it's upgrade files to your existing SOLUS 2 setups folder then you should achieve SOLUS 2 style upgrade behaviour from your machines which don't have an agent on them so long as they have the correct SIMSSetupsDirectory listed in their SIMS.ini file.

 

2. Any devices that do have the agent installed but are offline when the update is deployed will not get the update unless it is deployed again? Or will the agent check?

 

Offline machines won't get it initially (at the time of deployment) but they will receive the update as long as they come online within a certain timeframe after the deployment. I'm not sure what that timeframe is though (2 weeks rings a bell for some reason). It might not occur that quickly though so you may have to redeploy for some machines.

 

For failed / offline machines you can either Redeploy the upgrade in bulk to those machines from the server GUI or use the agent on the machine itself to upgrade a machine individually.

Edited April 4, 2016 by superfletch