We are installing a new SIMS server today. As part of this the old S: drive is being renamed and a new one setting up on the new server. Previously the S: drive got cluttered up as a general dumping ground for SMT/Admin/Office Staff files. I'd like for this not to happen again. So is it possible to give SIMS users read only permissions to the S: drive without breaking anything, so they don't clutter the drive up with tosh again!
Surely for SIMS to function, they will need write access of some sort to write back to the database? It might be possible to lock down the access they can have by only allowing certain folders / files read/write access, but I've never really experimented as I don't have the same problem here (I have a curriculum server for the staff to use as a dumping ground! lol)
The database connection uses TCP/IP and/or a pipe. It's got nothing to do with the file share beyond the client looking there for updates (in S:\SIMS\SIMSINST) and looking for the SIMS.INI to tell it where the Database lives.
My SIMS S:\ is setup as the following;
I have two groups - SIMS Users and SIMS admins. SIMS users only have read access to the Directory hosting the SIMS files, SIMS Admins have read/write access to the whole srive for dealing with CTF files, upgrades, Exam files etc.
This works fine with regards to upgrades etc. There is no reason for normal SIMS users to have read/write access to the drive.
Mike.
vikpaw (24th October 2009)
i was always told at my last school to give full permission, even then, i made the setups folder read only for regular users.
It's really useful to know that only read permissions are required, more useful to know that you've tested it that way.
I'll be sure to experiment with that now. The only people that need access to edit files will be the timetabler.
why not give them the rights you currently have but use an adm or reg hack to hide the drive from them. it will still be mapped, just not visible.
BoX
Nice idea.
We also hide the drive. If you have Server 2008 you can do it in group policy now.
For most people you can have read only. But as mentioned some directories will need to be writable by people who do your census etc eg star\ascout etc. Also ctf files need to go in a certain place as well.
Does anyone have a list of what needs to be writeable?
We call ours the G drive, ours was setup by Capita long before I joined.
Our G drive points to \\server\SIMS - I guess this would be similar to your S
NTFS = Support Staff & Teaching Staff have everything up to Modify (no special and not full)
Share = Everyone has Read & Change
Obviously, it depends on your AD groups as they may well be different. I don't know exactly why it needs change/modify perms though, I thought this was all through SQL but none the less this is the default setup (or at least as I know it - this has been how it is).
Presumably this must be recursive throughout the hierarchy within SIMS - I have no definite information on folders they write to and thus need perms :-(
Last edited by dwhyte85; 24th October 2009 at 08:30 PM.
robk (30th October 2009)
Look for the likes of ctfin, ascout these will be the easy ones to spot.Originally Posted by Geoff
We store our DocStorage on this drive, would this need to be writable too ?
Or is this something that should only be accessible from the server ?
Files such as CTIN, CTOUT, Census don't have to be on the S drive - I moved the Census folder on our system for data security reasons. You have the facility to set alternative paths from within SIMS.
So you're saying that you can do this without having to write a custom adm now?
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks