Departments use file servers to more efficiently share files, as compared with emailing files.
Notes
- But as with any change in workflow, conventions may need to be discussed and agreed on, and new skills and habits developed.
- When and if it's a "go" per Physics's decision, PhysIT can make this server "drive" appear automatically so it becomes easily available on staff computers. This is almost immediate, once committed, via AD policy.
- Roger is working with Greg at A&S to set up the space (as of 11/15), in anticipation that this service will prove of value to Physics. This can easily be reversed if a "no go", of course.
November 2014
Phase one: Shared folders
Synonyms: Folders == directories.
Conventions used among staff will limit actions not necessarily enforced by the permissions.
Objective: Reduce complexity to reduce mistakes and facilitate debugging, balanced with ensuring security and adequate access.
Groups
Group name: AS-PHY-AdminStaff
Sub-group name | NetIDs | Members |
---|---|---|
Management
| jcm8 dah6 | John Miner Deb Hatfield |
Business | nbs4 | Nancy Searles |
Grad | klb79 | Kacey Acquilano |
OtherStaff Individual group members | rjf2 sfc1 ? | Rosemary Barber Sue Sullivan Brad (temp) |
Folders and permissions
Folder name | Primary directory (folder) owner(s) (NetID) | Full folder access, by group or individual (NetID) | Notes | Sort |
---|---|---|---|---|
Undergrad | Sue Sullivan (sfc1) | AdminStaff | Access by all staff | 1 |
Duplicating | Brad (temp) | AdminStaff | Access by all staff | 2 |
Course Management | Rosemary Barber (rjf2) | AdminStaff | Access by all staff | 3 |
General and Central | Sue Sullivan (sfc1) | AdminStaff | Access by all staff | 4 |
Grad | Kacey Acquilano (klb79) | Grad, Management | 5 | |
Faculty | Deb Hatfield (dah6) | Grad, Management | Kacey needs occasional access | 6 |
HR and Staffing | Deb Hatfield (dah6), Nancy Searles (nbs4) | Business, Management | 7 | |
Budget and Finance | Nancy Searles (nbs4), John Miner (jcm8) | Business, Management | 8 | |
Chair | Deb Hatfield (dah6) | Management | 9 |
Folders hierarchy options/ ideas
Do you want an "Instruction" folder, containing folders specified above?
Do you want a "Business" folder, containing folders specified above?
Do you want some other folder, to contain folders specified above?
Idea 1: One level deep for some folders
Top Level Folder | 2nd Level Folder | Notes | Sort |
---|---|---|---|
Instruction => | Undergrad Duplicating Course Management | Access by all staff | 1 |
General and Central | 2 | ||
Grad | 3 | ||
Faculty | 4 | ||
Business => | HR and Staffing Budget and Finance | 5 | |
Chair | 6 |
Idea 2: All folder at top level
Top Level Folder | Notes | Sorting |
---|---|---|
Undergrad | Access by all staff | 1 |
Duplicating | Access by all staff | 2 |
Course Management | Access by all staff | 3 |
General and Central | Access by all staff | 4 |
Grad | 5 | |
Faculty | 6 | |
HR and Staffing | 7 | |
Budget and Finance | 8 | |
Chair | 9 |
SysAdmin Note:
- Permissions on shared dept folders will be applied only by groups, not ID's (Due in part to the complexity of tracking /adding / removing individual permissions applied to folders, as well as possible file inheritance & permissions settings.)
- Individual ID permissions should only be granted to folders in "Users" folder trees, if used. (Scripting / variables may be preferred)
- Groups should have a functional name (please) "Business office", "Instruction", etc.
- All Phy dept sub-groups will be put in a primary Physics Admin / dept group - which is used to apply policies, map drives, apply networked printer queues, allow access to the share, etc.
- A special
- All staff must be in at least one sub-group, and preferably only one - even if the group only contains one person. (To allow access to share, policy’s, etc.)
- Folders which everyone can access do not need finer grained permissions. (Use primary group @ root only)
- Groups may either be nested (HR in Business Office), or multiple groups may be given permission to a folder (Safety, Facilities), as appropriate.
- Where group nesting/ combining is not sufficient, a user may be placed in more than one group.
- Caution is advised with any nesting or combined group access, unintended future rights may result.
- It is desirable to use these same groups for all services, such as Group Policies, FileMaker, Printing, File Sharing, etc.
- Policies can only be applied to accounts which are in the AD Tree cornell.edu\CUinv\NetIDs\Staff\AS\, or are created by AS/ChemIT/Physit (Special admins, guestID's, etc.)
Phase two: Individual's folders
- TBD
Info from John Miner, to inform this:
Folder name | Primary directory (folder) owner (NetID) | Full folder access, by group or individual (NetID) | Notes |
---|---|---|---|
FACILITIES | JOHN | ||
MANAGER | JOHN | Q: Is this more a personal folder, not a "shared" folder? A: Sounds that way. "Users\jcm8" |