Exchange public folder size
In Exchange 2013 the Public Folder is no longer a separate database. The drawback with this replication is that sometimes the user needs to wait for minutes to get the PF updated. In Exchange2010, the public folders were not part of Database Availability Groups (DAGs) and used same PF replication method to achieve resilience and high availability. This was done for to allow PF replica to be available to users on the nearby network/server in order to save bandwidth and improve performance. All seems to work just fine but we have the question about whether or not a replica of the System PF is neccesary on the Exchange 2010.įrom my readings, this was only needed if you were migrating from EX2003 to EX2010 to allow services to be available during migration period or if you were to support Outlook 2003 on your EX2010 environment.Public folders used their own database replication between servers for high availability. With this in mind, I have performed tests to ensure services such as Availability, OOF, OAB, etc work from mailboxes hosted on Exchange 2003 and Exchange 2010.
Our Office in APAC is also migrating to Exchange 2010 with Outlook 2007 clients, with the difference that we wont host a PF database locally but we will point our databases to the instance in the HQ Office (I know, not ideal but I just dont see the need to host a local copy when we are migrating PF content to Sharepoint). Our HQ Office is migrating to Exchange 2010 with Outlook 2007, they have a dedicated PF Server hosting a PF database, they have added replicas for the Top Level Folder. Wanted to confirm about the need to add replicas for system public folders (Free Busy, Organizational Forms, etc) when a) there are no Outlook 2003 clients, b) OAB distribution is set to web only and c) mixed environment that includes mailboxes hosted on Exchange 2003, 20 (across multiple regions). Public folder database successfully removedĮxchange Server Exchange 2007, Exchange 2010, Public Folders When you try to remove the public folder database again you should find that it now removes without error. Highlight it and then click Edit.Ĭlick the Clear button so that the value changes to “not set”.Ĭlick OK, and OK again to commit the change.ĭepending on the size of your network you may need to wait for that change to replicate throughout your Active Directory. Scroll down until you find the msExchHomePublicMDB attribute. Right-click the mailbox database you want to remove the default public folder database from and choose Properties. For Exchange 2010 you’ll find this in CN=Services -> CN=Microsoft Exchange -> CN=(your organization name) -> CN=Administrative Groups -> CN=Exchange Administrative Group (FYDIBOHF23SPDLT) -> CN=Databases. Navigate to the container that holds the Exchange databases. Connect to the Configuration naming context with ADSIEdit Open ADSIEdit.msc and connect to the Configuration naming context. However all is not lost, there is another way, using ADSIEdit.msc. + FullyQualifiedErrorId : ParameterArgumentValidationError, Set - MailboxDatabase Here is what happens if I try to use Set-MailboxDatabase to set the value to $null. So instead I want to set the mailbox database to have no default public folder database. It is simple enough to change the public folder database configured for a mailbox database to some other public folder database, but in this situation I’m trying to get rid of public folders entirely. All I need to do is modify that mailbox database so it no longer uses the public folder database. Before deleting the public folder database, assign a new default public folder database to the mailbox database(s). Public folder database “PF-BR-01” is the default public folder database for the following mailbox database(s): The public folder database ‘PF-BR-01’ cannot be deleted.
The public folder database cannot be deleted When I attempt to remove the public folder database I receive this error. Ensured all my clients are Outlook 2007 and above.Ensured OAB distribution is set to web only.Removing all of the public folder content.In this scenario I have gone ahead and prepared to remove the public folder database by: If you’ve been using public folders in your Exchange organization and decided to get rid of them completely then you may run into this particular issue. Microsoft has made it pretty clear in recent years that public folders will be going away at some stage in the future of Exchange Server.