Skip to main content

Listing Public Folder Permissions with PowerShell

By

We started off class this morning in a Q&A session.  One of the questions was how to get the public folder permissions on an Exchange Server.  In this example, Exchange Server 2013 is being used.

1

2

Get-PublicFolder -Recurse |

    Get-PublicFolderClientPermission

Line 1 Gathers all of the Public folder objects, including subfolders.

Line 2 Gathers the user rights on each public folder and then displays them

FolderName           User                 AccessRights                                                     

----------           ----                 ------------                                                     

IPM_SUBTREE          Default              {Author}                                                         

IPM_SUBTREE          Anonymous            {None}                                                           

Folder1              Default              {Author}                                                         

Folder1              Anonymous            {None}                                                           

Folder2              Default              {Author}                                                         

Folder2              Anonymous            {None}                                                           

FolderA              Default              {Author}                                                         

FolderA              Anonymous            {None}                                                           

Folder1A             Default              {Author}                                                         

Folder1A             Anonymous            {None}                                                           

Folder2A             Default              {Author}                                                         

Folder2A             Anonymous            {None}                                                           

FolderB              Default              {Author}                                                         

FolderB              Anonymous            {None}       

 

According to the Add-PublicFolderClientPermissions cmdlet help file, here are the access rights that can be assigned.

Access Right Description
ReadItems The user has the right to read items within the specified public folder.
CreateItems The user has the right to create items within the specified public folder.
EditOwnedItems

The user has the right to edit the items that the user owns in the specified public folder.

DeleteOwnedItems

The user has the right to delete items that the user owns in the specified public folder.

EditAllItems The user has the right to edit all items in the specified public folder.
DeleteAllItems The user has the right to delete all items in the specified public folder.
CreateSubfolders The user has the right to create subfolders in the specified public folder.
FolderOwner The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items.
FolderContact The user is the contact for the specified public folder.
FolderVisible The user can view the specified public folder, but can't read or edit items within the specified public folder.

 

You can also create rights based on roles.

Role Access Rights
None FolderVisible
Owner CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
PublishingEditor CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
Editor CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
PublishingAuthor CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
Author CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
NonEditingAuthor CreateItems, ReadItems, FolderVisible
Reviewer ReadItems, FolderVisible
Contributor CreateItems, FolderVisible
Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more