[sims] SOLUS3, new SIMS Installs & no connect.ini

[Rawns]

I've come across this in a number of sites now and not sure if anyone else has seen this or experienced it.

 

We have some schools which are fully SOLUS3. Everything SIMS wise has been set up, they've had a successful upgrade in the past, Connect and SIMS.INI files have been specified in the SOLUS3 UI etc etc.

 

However, when new workstations are successfully added to SOLUS3 for SIMS .net installations, SIMS .net installs fine however in most cases, the connect.ini file is not automatically created/copied onto the workstation. Running SIMS on these new devices results in it prompting for a Connect.ini file.

 

The manual "Deploy connect.ini" file functionality in SOLUS3 is also hit and sometimes does not copy the Connect.ini file out to some devices.

 

Has anyone come across this, or have any ideas as to what is happening here?

Edited September 5, 2013 by Rawns

[MrWu]

Me too, I'm chasing Capita for suggestions t the moment, not very nice when we have 170plus machines when we changed SIMS server!

[robjduk]

we deploy the connect.ini via group policy and seems to work ok

[MrMat]

I'm having the same trouble Rawns. Only noticed it recently. Are you still on 3.5 or have you taken the plunge to 3.6?

[Rawns]

I'm having the same trouble Rawns. Only noticed it recently. Are you still on 3.5 or have you taken the plunge to 3.6?

 

Not yet. Our LA instance won't upgrade to 3.6 due to a database upgrade error.

 

We also have not rolled it out to schools yet because it seems that the SOLUS 3.6.92 auto deployment functionality is broken! We're waiting for a working version, I'm not manually upgrading 120+ SOLUS3 instances for no one!!!

[mukz]

i just had to script it to copy it across the network

[Michael]

A script or GPP would work. GPP is without doubt the easier option.

[Rawns]

Work arounds are all well and good, but SOLUS3 should be doing this in the first place. I've logged a call with capita regarding it.