In this post, we will look at Public Folders in Exchange 2010. More specifically:
- We will review the purpose and use of Public Folders within your organization (and discuss the fact that they may no longer be used in some future version of Exchange).
- We will go through the creation of a Public Folder database in the Exchange Management Console and see the properties that we can configure.
- We will work with the Public Folder Management Console and the Outlook client to create and manage Public Folders.
- We will review permission settings and delegating permissions for folders and sub-level folders.
- Public Folders are Nostalgic (out of date) – Public Folders were introduced with the first version of Exchange and have been used for many years as a means of collaborating with persons in your organization through a shared folder structure.
- Users will see the Public Folder structure in their Outlook client and can view items that have been either posted or emailed to the folder (if it is mail-enabled) and they may have the ability to add content, create sub-folders and so-forth if they have permissions to do so.
- Are Public Folders required in Exchange 2010?
- If you have Outlook 2007 and/or 2010 clients only, than the answer is no (it is completely optional if you want to).
- If you have Outlook 2003 clients, then the answer is yes. They use the Public Folder structure for Offline Address book distribution, free/busy lookups, organization form library, and security settings.
- Public Folders have become the dumping grounds for anything and everything your people want to share with each other. Public folders tend to sprawl out of control.
- Public Folders are so late-1990’s. They aren’t designed for two very important 2010+ aspects of corporate life: Archiving data, and Document Sharing and Collaboration (check-in/check-out, versioning). Associates tend to try to hide their personal mail archives in Public Folders so that they are backed up.
- As a result, the Microsoft Exchange Team has been making threats to pull Public Folder support from a future version of Exchange.
- The idea is to encourage organizations toward SharePoint (although you are welcome to research and use some other collaboration solution).
- While SharePoint has great features, any collaboration software has the potential to become the NEW dumping grounds for your organization.
- During the installation of the first Exchange 2010 Mailbox Server in your organization you see the question: “Do you have any client computers running Outlook 2003 and earlier or Entourage in your Organization?” If you answer “Yes” then the Public Folder database is automatically created.
- You can also manually create a Public Folder database on any Mailbox Server in your organization and then determine if you want to replicate folders to that server.
- In Exchange 2010 there are no HA solutions you can use by default. The only way to ensure content is available is to create a new database and replicate content to that server.
- Maintenance Schedule
- Replication Interval – specific to DB
- Storage Limits
- Deletion Settings
- Age Limits
- Public Folder Referral
- Replication (Both server choice and replication schedule)
- Limits (Storage, Deleted Item, Age)
You can configure certain items on individual public folders like replication. Replication at the database level can be scheduled, or you can establish on the individual folder themselves.
Go to the Public Folder Console by going to the EMC -> Toolbox -> Public Folder Management Console:
Default Public Folders – include existing public folders created by an administrator. Try to maintain and organize Public Folders with a structure to maintain focus. One possibility is organizing by location. To add new folders, select New Public Folder… in the Action Pane. You can create sub-folders inside each Public Folder. You can delegate permissions on Public Folders to allow users the ability to create new sub-folders. Right-Click on a Public Folder, choose Properties. Under the Replication tab, you can add servers to replicate the content to and if you want High Availablity, you will select a different MailBox server and replicate the folder. You might replicate content to put them closer to actual user’s locations. You can use the default public folder replication schedule, or create your own. For limits, you can use the default quotas, or establish your own.
System Public Folders – we will cover these later.
Key Focus Points of Public Folders:
What are some of the key concepts of Public Folders?
- Public Folder Trees
- Default Public Folders (IPM_Subtree – folders that users are typically aware of)
- System Public Folders (System PF structure known as the Non_IPM_Subtree – used by outlook for free/busy data, eforms registry and events root, for outlook clients that do not support 2010 or 2007 features (Availability service etc.) Legacy clients don’t know where to look for this, but can get their legacy data from these structures)
- Hierarchy – Properties of the folders, and organizational information, name of public folder, which server holds the replicas, and permissions are replicated with the heirarchy
- Content (Requires configured replication) – you decide which mailbox servers have copies of the content.
- If a client looks for somethign in the Public Folder heirarchy, if they click on the folder, do they get it from their local Mailbox server? If it can’t find the data from their Mailbox, it will look for a replica in the same site. If it can’t find it there, it will look for the lowest cost site.
- What are Mail-enabled Public Folders?
- They provide a bit more functionality to PFs
- Users can post to a PF through email.
- Exchange Administrators should consider delegating folder creation and management to others.
- The easiest way to delegate is to assign persons to the Public Folder Management Group and let them worry about creating and managing Public Folders through Outlook
- If you wanted to see the permissions or set the permissions on Public Folders, you cannot use the EMC/Public Folder Management Console. You must use the Exchange Management Shell.
- – Cmdlet used to add administrative permissions: Add-PublicFolderAdministrativePermission
- – Cmdlet used to add client permissions: Add-PublicFolderClientPermission
In an Outlook 2010 client, if a user does not have permissions to create a sub-folder in a Public Folder, check the properties of the folder first -> Summary Tab.
To add a user to a Public Folder Management Group so that they can make changes/add folders to a Public Folder, you’ll need to open the Exchange Management Shell:
Edit – you can change permissions now through the Public Folders Management Console if Exchange 2010 SP1 is installed
[PS] c:windowssystem32>Add-RoleGroupMember -Identity “Public Folder Management” -Member User.Name
After hitting Enter, nothing appears to happen, but when logged in as the user, and visiting the properties of a Public Folder in Outlook, you will see the additional properties/permissions available. And from here you can give additional permissions to other users.
If a Public Folder is mail-enabled, in the Global Address List, you can change the address book to Public Folders, which will list all available Mail-Enabled Public Folders.
Permissions: Rights vs. Roles
- When using Outlook to assign permissions to a Public Folder you assign Roles (like Editor, Author and so forth).
- Those Roles have underlying Rights assigned to them. For example, a Reviewer (role) has the rights ReadItems and FolderVisible.
- There are 10 different Rights that mix and match for each role:
With Exchange SP1, you can change permissions (rights and roles) for public folders using the Public Folder Management Console -> Right-click on Default Public Folders -> Choose Properties -> Permissions Tab.
A good majority of the content provided in my Blog’s Exchange series is derived from J. Peter Bruzzese’ excellent Train Signals Exchange Server 2010 Video Disk Series, as well as my own Exchange 2010 lab. Trainsignal.com is an invaluable source for accurate, easy to understand, IT information and training. http://www.trainsignal.com