SIMS client only asking for connect.ini location

[OllyM]

Hi all

 

I've just pushed out the SIMS client via the Solus agent on the desktop machine. The SIMS.net icon appears on the desktop and the user can double click it. However when they do it prompts them for the location of the connect.ini file or the database location.

 

If you enter this (I:\sims here) then the box goes away, but the SIMS package never actually appears.

 

If you double click it again then you are asked for the location again.

 

Anyone seen this before? Is there a way I can beat it in to submissions?

 

The prompt defaults to c:\sims so I even tried creating a local connect.ini in the c:\sims folder on the desktop, but that didn't help at all.

 

Olly

[MichelleC]

Yes, our Solus frequently forgets the connect.ini. I normally copy the SIMS folder from program files from a working workstation, but you can just copy the connect.ini from another workstation into the SIMS folder in program files instead.

[bobsmith]

Shouldn't your connect.ini be here?

 

C:\Program Files\SIMS\SIMS.net\connect.ini

[clareq]

The end user doesn't have permission to create the connect.ini file, so will be prompted for it repeatedly. I deploy it by GPO.

[matt40k]

@OllyM Sounds like you need to check your SOLUS3 config, sounds like the INI files bit isn't setup correctly. Contact your local support team and they'll sort you out.

[KibosJ]

This happens with a few of our clients too, SOLUS3 is set up properly because it works for most of the clients.

 

As others have said, a GPO or manually copying it over is the best things to do.

[OllyM]

Thanks all

 

The chap I took over, looking at it, was doing it all by hand with various scripts and notepad instructions.

I'll clone another program files folder for now and brute force it and then sit down over the holidays and get it beaten.

 

Ta

 

Olly

[matt40k]

This happens with a few of our clients too, SOLUS3 is set up properly because it works for most of the clients.

 

As others have said, a GPO or manually copying it over is the best things to do.

 

I'd avoid this. It's just a problem waiting to happen (ie you leave, they update S3, but don't update GPO, yes I know, easy to fix, but its a un-needed pain). If S3 is having trouble deploying a 1 KB file, I'd suggest you'd get the underlying problem fixed.

[KibosJ]

I'd avoid this. It's just a problem waiting to happen (ie you leave, they update S3, but don't update GPO, yes I know, easy to fix, but its a un-needed pain). If S3 is having trouble deploying a 1 KB file, I'd suggest you'd get the underlying problem fixed.

 

We don't use a GPO here, it's just a manual process that the techs know about, but it only ever happens on a rare occasion.

 

99% of the machines work fine, which is the strange thing, Solus3 can deploy a whole SIMS install, FMS Install and Discover, but fails to copy over a 1KB file. I'm not sure where to even start looking to pinpoint the issue :/

[matt40k]

99% of the machines work fine, which is the strange thing, Solus3 can deploy a whole SIMS install, FMS Install and Discover, but fails to copy over a 1KB file. I'm not sure where to even start looking to pinpoint the issue :/

It's what you pay support for