[sims] SIMS.INI - mapped S:\ drive

[Koldov]

Just trying to get some clarity here...

 

I remember reading that there is no need to map an S:\ drive anymore for SIMS clients and that in the SIMS.INI file (in the WINDOWS folder) it can just be pointed at the server...?

 

Is that right and if so how is that accomplished, do you make a new one and adjust the setting in SOLUS to push it out to clients?

 

Also, is it supposed to reference files and folders on the remote server or the local PC...?

 

As ours references both the mapped drive S:\ but also folders on the C:\ drive and the D:\ drive (which we don't have on the local computers).

 

[setup]

SIMSDotNetDirectory=C:\Program Files (x86)\SIMS\SIMS .net

SIMSDirectory=S:\SIMS

SIMSSetupsDirectory=S:\SIMS\Setups

SIMSSQLAppsDirectory=D:\Program Files\Microsoft SQL Server\XXXXXXXXXXXX\MSSQL\Binn

Folder=SIMS Applications

SIMSDiscoverDirectory=C:\Program Files (x86)\SIMS\Discover Client\

FinanceDirectory=C:\Program Files (x86)\SIMS\FMSSQL

[LastChecked]

SIMSInfrastructureSetup=1.617.1.0

[installationLogs]

SIMSSQLApplicationSetup.exe=C:\Users\XXXXXXXXX\AppData\Local\Temp\1\SIMSSQLApplicationSetup.log

[FMSSQL]

FMSSQLAppsDirectory=D:\Program Files\Microsoft SQL Server\XXXXXXXXX\MSSQL\Binn

 

Our SIMS was apparently set up by a Capita engineer before I started, but our server has a shared network drive (S:\) which points to a folder on itself called SIMSROOT and an S:\ drive is also mapped to all clients who use SIMS/FMS which points to the same folder on the server.

 

The CONNECT.INI and the FMSCONNECT.INI both just reference SERVER/SQL but in SOLUS come from the default file which is hosted on the S: drive (on the server?)......

[Boredguy]

In your SIMS.INI file, the SIMSSetupsDirectory & SIMSDirectory values can just be your UNC path to the folders in place of S:

In your connect.ini file, make sure, make sure you have the following in place of the Redirect

[sIMSConnection]

ServerName=\

DatabaseName=SIMS

ServerType=SIMSSQL

CommandTimeout=10000000

 

Then only assign the S drive to those staff that actually need it, such as Timetabler, Finance, Admissions.

[psydii]

Use the hostname, not the IP address for connectivity. Otherwise you fail back to NTLM authentication.

[jthompson]

I think before the days of SOLUS3, it was easier to have connect.ini redirect to a connect.ini in S:, so that any changes were easily applied to all users. Now you can just push out a new connect.ini to clients from SOLUS3 if you need to, and leave S: in place only for those few users who actually need it.

[Boredguy]

Good point, however our connect.ini is configured to access multiple schools DB's within the MAT, so we can't use hostnames as they don't resolve at each site