Do we still need a mapped S:\Sims drive with Solus3?

[TwistedHelixis]

Probably a stupid question but recently moved to Solus3 and wondered if the S:\Sims drive still needs to be mapped for staff to use or install Sims?

 

I assume it does but just checking.

Thanks

[Boredguy]

If your connect.ini is pointing directly to your database, then there is not really a need to map the drive for most users.

Some will still need access for Timetabling, exams and returns though.

[TwistedHelixis]

Thanks - Just remembered our connect.ini file is located on the S drive, so we will need that mapped.

[SimonCygnetIT]

Also don't forget about the Attendance Letter templates that schools can create which are stored in the SIMS folder paths

[Esteban_Child_of_the_Sun]

If you are using SOLUS 3, you can define the local connect.ini files to point straight to the server and thus remove the need for a mapped drive. Similar with attendance letters, if you specify the shared SIMS folder as a UNC patch you don't actually need to map it. Most of our users don't have a mapped S: drive any more, but they do still have access to the network share.

[ollieonline]

As others have said, stat returns, ctfs, exams data, timetabling still require it.

 

Personally I would advise against using a local connect.ini as it can cause problems if you need to relocate your dB server. Also the data that is transacted in those processes above can be sensitive and having it stored locally on workstations is not the best idea particularly if they are laptops and not adequately encrypted.

[Chuckster]

If you are using SOLUS 3, you can define the local connect.ini files to point straight to the server and thus remove the need for a mapped drive.

@Esteban_Child_of_the_Sun, can you tell me how you achieved this?

[Banjo]

We tend to keep them as even though the servers have S3 installed, we still pull updates at the workstations via simsload in most schools.

[Esteban_Child_of_the_Sun]

You can send out updates to the workstation's connect.ini from SOLUS 3 | Environment | Configure Workstations | connect.ini

This will update the connect.ini file of each SOLUS 3 agents with a SIMS workstation role.

[matt40k]

Personally I would advise against using a local connect.ini as it can cause problems if you need to relocate your dB server.

 

Then you'd just deploy an updated connect.ini via SOLUS3

 

 

Also the data that is transacted in those processes above can be sensitive and having it stored locally on workstations is not the best idea particularly if they are laptops and not adequately encrypted.

You would never store them locally, but again, you wouldn't want to the store them in a folder everyone can get at