When synchronizing Public Folders, there are folders on the source of different types - for example - Calendar folders, tasks folders, etc. These folders are successfully created on the target, however they appear as normal "post" folders. Why is this happening?
If you specify a non-standard-type folder as the synchronization root and create the target folder with the Collection Wizard, a folder with standard "post" type is created, regardless of the source folder type.
IMPORTANT: Do NOT delete any public folder data in the target. This can cause tombstone issues that can be difficult to resolve. To resolve this particular problem, perform the following steps:
1. Stop the Public Folder Agents.
2. Remove the problem public folder from the collection.
3. Rename the target public folder.
4. Manually create a new target public folder with the correct name, and correct folder type.
5. Add the public folder to the collection, and specify the new folder as the target.
6. Modify the public folder collection to perform a full re-sync. This setting is under the synchronization tab. For more information please review the product user guide.
7. Commit changes.
8. Using the Service File Viewer Utility, remove any .pub files that are awaiting processing on the target server for the collection in question. The source object column can be used to determine the source of the file.
7. Start the Public Folder Agents.
You should now see the public folder data arriving in the new target folder, and should be displayed in the correct format. Once you confirm this, you can move the messages from the folder you renamed into the new folder.
Please note that if the source folder with a non-post type is "under" the synchronization root, the target folder will be created by the agents and will have the correct type.