Exchange Server environment, public folders are a vital source of information as these enable shared communication and collaboration within the teams in an organization. Exporting public folders can be a challenging task and often a complex procedure which involves scripting and requires technical expertise. In this article, we will be discussing some common issues and challenges you might face when exporting public folders and the possible solutions to resolve them.
Why do you need to export public folders?
You need to export public folders due to various reasons, such as:
- Migration to another Exchange Server.
- Migration to Exchange Online (Microsoft 365).
- Archiving the public folders data due to size limitations.
- Meeting the compliance and regulations, such as data retention.
Common Issues you may Encounter when Exporting Public Folders and their Solutions
Below, we will take a look at the issues which are commonly found in such environments – from the easy ones to the most complex ones. We will also provide solutions to resolve them.
Note: We are excluding the export of public folders using the Microsoft Outlook client since this is not recommended due to several limitations.
1 – Lack of Permissions Preventing the Export
Lack of permissions is the most common issue that you might encounter when attempting to export a public folder. As an administrator you might have full access on the Exchange Server, you still need specific permissions on the public folders to be able to export them.
Solution
You must get owner permissions to the public folders in order to export them. This permission can be assigned temporarily until the export is complete. First, you need to make sure that the Public Folder Management role is assigned to the user you will be using for export. Then, you need to verify the access of the user. This can be done using the below PowerShell command in the Exchange Management Shell (EMS).
Get-PublicFolderClientPermission -Identity “\<folder name>”
If the user is not listed as owner, you can run the below command to grant the permission.
Add-PublicFolderClientPermission -Identity “\<folder name>” -User “<export user>” -AccessRights Owner
Ideally, the permissions should be checked by the administrator before exporting to prevent unnecessary delays in the export task.
2 – Slow Performance during Export
Depending on the size and complexity of public folder, the export process might be exceptionally slow. This might happen due to a number of reasons. For example, you could have a high-volume email traffic or outdated infrastructure. This may delay the export and impact the overall Exchange Server performance.
Solution
You should perform the export process outside working hours. During the maintenance windows, load on the server is low. This will increase the performance and speed of the export and not hinder the experience of users or disrupt the business.
You need to also ensure that the storage of the server has enough Input/Output operations per second (IOPS) to handle the export and load on the databases.
Optimizing the Exchange Server indexing can also reduce search delays during extraction runs.
You can use third-party EDB converter tools to export the public folders. This will increase performance of the export tasks, without impacting the server.
3 – Timeouts or Slow Exports due to Large Public Folders
Public folders tend to become quite large. When exporting large public folders, the task may get difficult to manage and often result in timeouts, slow exports, and other issues such as corruption.
Solution
Here are some solutions that can help reduce the margin of errors and timeouts:
- Reduce the public folder size or split the data. This task requires the effort of users and business as it would be a spring-cleaning task which will make the public folders more efficient and easier to work with.
- Change the organization limit to accommodate the large folders (if the storage allows). It does not exceed the size limit.
- Use the built-in tool – EseUtil – to run a defragmentation and compact task on the Exchange Server to reduce the I/O overhead. This will improve the efficiency of export and overall performance of the database.
- Consider using third-party tools that can handle large databases and volume more effectively than the native Exchange utilities.
4 – Unforeseen Migration Issues
Sometimes, unforeseen issues during migration to another Exchange Server or Exchange Online (Microsoft 365) hinder the migration task. Such issues include:
- Folder hierarchy inconsistencies.
- Configuration issues on the Exchange Server.
- Data duplication.
- Scripting errors and human errors.
- Export is too large.
Solution
There is no exact solution for such issues but you can follow the below preventive measures to avoid them:
- During the scripting part, you must confirm the mapping before initiating the transfer.
- Perform a data cleanup prior to exporting and migrating the data. This will reduce the size and complexity of the export.
- Use PowerShell scripting to validate consistency of the data, prior to migrate or import.
- Carefully plan the export process as bad planning would lead to migration failure.
A Simple Solution to Prevent Issues when Exporting Public Folders
An easy way to avoid such issues is by using a specialized EDB converter tool. Such a tool can minimize the impact on server, simplify the export, and ensure data integrity. Stellar Converter for EDB is one such reliable tool that can open live, offline, and orphaned Exchange Server database independently, without having a running Exchange Server, from any Exchange Server version, and of any size. You can browse through the database and export public folders and other items, such as user mailboxes, user archives, shared mailboxes, etc. to PST and other file formats. You can also export the public folders and other EDB items directly to a live Exchange Server database or Exchange Online (Microsoft 365). Additionally, the tool features automatic mailbox matching, parallel export with multi-threading, and priority exports.
Conclusion
Exporting Exchange Server public folders can be a daunting task and requires skilled technical expertise and meticulous planning. You may encounter several issues and challenges when exporting the public folders. However, you can overcome most of the issues and challenges with the right solution and minimize the impact on business, ensures data integrity, and simplify the export. You can use a third-party EDB converter tool, such as Stellar Converter for EDB, for effectively exporting the public folders with ease and peace of mind.
Site Hierarchy That Affects SEO: Subdomains VS Subfolders