 They’re available in Exchange Online  Great for simple sharing and distribution list archiving in Outlook  Site Mailboxes and SharePoint are better for rich document collaboration  No changes to end user experience

Working towards a shared outcome/purpose Working together on shared deliverables Need to get all the tools we need to be successful Working together as a team Team appears as virtual identity (e.g., Working on shared queue of incoming requests Answering as the virtual identity, not the individual Working on behalf of a virtual entity History of public conversations Accessible to everyone Discoverable/searchable for everyone Not in the inbox Public, unobtrusive conversations Delivering information into the inboxes of a group of people Direct communications with a group Site Mailboxes Public Folders Shared MailboxesDistribution Lists

Cross-premise & cross-forest access: E2013  E2013, E2013  E2010, E2013  E2007 OWA access for Public Folders EAC UI for admin tasks Public Folder and Mailbox restore Full text search Automated Storage Management for service customers What’s new? Migration support from E2010 and E2007

Clients - Outlook 2013, Outlook 2010, Outlook updates - Outlook Web App (in Exchange Online) Exchange Server - E2013 users can access E2013 / E2010 / E2007 Public Folders - E2007/E2010 users cannot access E2013 Public Folders, so migrate Public Folder users before Public Folder data Migration support - Cutover migration from E2010 and E Same forest and cross-premise

Public Folder databases replaced by mailboxes High availability, data redundancy, and low cost storage support through use of DAGs Multi-master replication simplified and replaced by single-master replication of folder hierarchy

Public Folder architecture Architectural bet Public folders are based on the mailbox architecture Details Hierarchy is stored in all public folder mailboxes Content can be broken up and placed across multiple mailboxes Similar administrative features No end-user changes Red Folder Green Folder CAS 2013 Blue Folder Pink Folder Yellow Folder Public logon Public logon Public Logon

Storage and scale Create a mailbox in a DAG New-Mailbox -PublicFolder Users create folders and messages Users grow Create more mailboxes! (New- Mailbox -PublicFolder) Hierarchy is copied automatically Users create more folders and messages Mailbox grows. Split it! Split-PublicFolderMailbox.ps1

Like one big online mailbox move, but migrate users first.

2. Analyze Take snapshot of existing PF folder structure, statistics and permissions Map PF folders to PF mailboxes Outlook clients 1. Prepare Install Exchange SP and/or updates across the ORG Migrate all users that require access to Exchange Begin Migration Request Clients continue to access and create new data during copy After copy is complete migration request status is AutoSuspended 5. Finalize Migration Request Update snapshot of existing PF folder structure, statistics and permissions Lock source, clients logged off, final sync occurs 3. Create new Public Folder mailboxes Set to HoldForMigration Mode, mailboxes invisible to clients MBX 6. Validate Check and verify destination folders PF dbase 2 PF dbase 3 E2007 SP3 or E2010 PF E2013 CU1 or Exchange Online PF mbx 1PF mbx 2 MB X 5 PF dbase 1 PFs PF mbx 3 3 RURU SP3