Using Solus3 to deploy Sims.ini

[TwistedHelixis]

I have just noticed that after the LA installed Solus3 on the schools servers they did not setup the Sims.ini file to be deployed. We do have connect.ini and fmsconnect.ini listed in solus3.

 

So whats the best way of setting up solus3 to deploy the Sims.ini file?

 

Do I copy the Sims.ini file from the C:\Windows folder on the server or from a client?

 

If I pick one from a client, when I hit deploy will it overwrite the Sims.ini file installed on the server?

 

Cheers

[matt40k]

I'd check with them why they haven't done it. (Personally I'd never get why you would want to deploy a sims.ini)

[TwistedHelixis]

Personally I'd never get why you would want to deploy a sims.ini

 

We have an error with the Sims documentation not opening from within Sims, and need to add the correct location to the sims.ini. I was then think if I do that at each workstation, would it not get removed when the next update comes out?

 

Open to other ideas

[matt40k]

Pretty sure when you configure the SIMS client in SOLUS3 you can define that path and that should get pushed out. Again, get your LA to check as they've missed something and they should fix it.

[kennysarmy]

Pretty sure when you configure the SIMS client in SOLUS3 you can define that path and that should get pushed out. Again, get your LA to check as they've missed something and they should fix it.

 

I agree, failing that can't you add something to your logon scripts /policies to push out the file if it does n't exist?

[Esteban_Child_of_the_Sun]

You could just specify the UNC path for the SIMSDirectory variable in the sims.ini and that way it wouldn't matter what drives are mapped or used.