[sims] Connect.ini Will Not Update

[wroberts]

Hi All,

 

I have a problem with my Sims connect.ini, when installing the Spring 2015 update on the machines, they are getting the wrong ini file and it is pointing towards an old server, i have spoken to capita and they have informed me to change the ini file in Solus and click to send it to the clients, i have done this but it does not appear to do anything, does anyone have any advice to sort this problem ?

 

Also does anyone know where i can check whether this new ini file is actually being sent out ?

 

Regards

 

Will

Edited April 8, 2015 by wroberts

[minimoo]

C:\ProgramData\Capita\Solus3\Logs on the server and have a look in the ds_systemlog.txt. The way the connect.ini used to work seemed to be a bit weird to me in the past. From what I could tell, it used to be the case that it would only update the connect.ini when you click the send button - unlike other bits of solus you could only send to all pc's in one go.

 

I'd say first step - have a look at the ds_systemlog.txt and see if it logs anything when you click the button, then have a look at the local agent log files (which are in the C:\Program Files\Solus3\AgentService\systemlog.txt file) and see if that shows up anything.

 

If solus 3 is setup in solus to push our or direct people to use a network UNC based ini file path have a look in the raw file and check it's got the correct information.

 

The connect.ini file should get pushed down to C:\Program Files (x86)\SIMS\SIMS .net\connect.ini - Rename an existing connect.ini from any PC where the agent is showing up as online in solus and then hit the link - i.e. you can identify whether the problem is that they are not receiving a file, or they are being sent the wrong file.

[robjduk]

I push my connect.ini out via group policy now as I have not trusted Solus 3 to do this for a while now.

[Ghostgame]

Check the Servers target definitions.

(Environment - Targets - Servers)

 

I have noticed if the SIMS server in Servers target definitions is not changed to the new server, the connect.ini does not stop pointing at the old server.

[Michael]

I also deploy it via GPP. Maybe worth checking whether a Policy is still pushing/sending out your old MIS server details.