Windows Forum

Ask something
Discussion Locked

Two NT Questions

0 helpful
5 replies

by aspiring_one

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am using a script to connect everyone to a share on an NT 4.0 network. Everyone has full control on the share and NTFS for that directory. It is my understanding that this is required for them to be able to see the share.

So, when you log on,the script will map you to a K: drive which contains several directories. Each of these directories have appropriate NTFS permissions on them. Users have to issue a formal request in order for additional directories to be created on the K: drive.In this way, I am able to maintain control over who uses what directory and for what, quotas, etc.

The problem that I am having is users are going to the K: drive and creating directories on their own and/or using the K: drive for temporary storage. This defeats the whole purpose of having a quota system in place and having everyone issue a directory request.

How can I keep users from creating directories on the K: drive? I don?t mind them being able to create directories within the folders that they have access to, however I don?t want additional directories made on the K: drive.

Also, how do I automatically delete a directory at a certain time every week?

5 replies

by syscokid

1. Restrict access to Read/Write only on the K: share itself, and apply more liberal rights to the subdirectories.

2. Use the AT command either at the command prompt or WinAT which ships with the resource kit. Create a batch file to delete your directory. Then make sure the scheduler service is running.

You can get the syntax by typing AT /? at a command prompt, but it's basically
AT 12:00 AM /every:F mybatch.bat

Good luck!

by nert

Just because the share-level permission is full control for everyone, does not mean that the secutiry, not permissions for that directory have to be full control. We have shares on our network that different people have different access to. Case in point: the server on which our MS Office files are stored on (we use the network installation) is pretty limited. All users have full control permissions to the share, but only read access security to the actual "drive" to be able to use MS Office. However there are other folders under this share that certain people do need to make modifications to and this is where the security is different.

by shanghai sam

(1) Lets say the folder being shared is J:\fldr\... You can reduce the Everyone group NTFS permissions on J:\fldr\ itself to READ (RX), leaving individual users' or groups' NTFS permissions on the various sub-folders within j:\fldr (i.e. j:\fldr\steffi, j:\fldr\hans etc) as FULL CONTROL (or reducing them to CHANGE (RXWD) access) as appropriate. This will allow them to see the top level folders (i.e. steffi, hans) but not add new ones, etc. Within the top level folders and sub-folders, individuals and groups with permission on that particular folder can read / create / modify / delete files and/or sub-folders, which is what you want.

I'm not aware of any need for FULL CONTROL to see the share; however READ on the top-level folder isnecessary for that purpose.

Everyone FULL CONTROL is suitable as the permission on the share itself.

(2) Make a batch file containing commands (e.g. del on the contents, rd on the directory itself) and use the AT command to schedule it to run on the server bwhen required.

However, this may fail if anyone is actually using the directory at the time. To be sure, consider adding seriously drastic commands to the start of your batch file, like "net stop server". This will immediatelydisconnect all users of all shared resources on the server. After deleting your directory, use "net start server" to allow new connections.

This discussion is closed to new replies.