I'm relatively certain I know the answers, but I am looking for others' input on this. I have a small Exchange 2010 implementation with a single Public Folder database present. By default, it appears that replication is turned on, even though the Public Folder does not have an actual replication partner. Because they Public Folders replicate via sending messages containing change data, and the fact no 2nd DB exists, I believe no additional resources are actually being consumed due to having the 'Replication Interval' set to 'Always Run' in the Properties of the Public Folder DB. I see no events in the logs indicating replication is taking place. Only service start and stop events for the replication service during reboots. Can this setting below be set to 'Never Run' without negatively affecting anything? Does it matter? Is the 'Microsoft Exchange Mailbox Replication' service required to be on if the Mailbox DB is not a member of a DAG (and there is only one Mailbox DB)? Is the 'Microsoft Exchange Replication' service required to be on if there is just a single Public Folder DB, and no replication partner? In the Public Folder Mgmt Console, when viewing the properties \ replication tab of the parent folder. Could I un-check 'Use Public Folder database replication schedule', then set to 'Never Run'? Any thoughts are appreciated! Thanks!

hi, I think you can change it to nerver run. But if it not affect your server performance, i recommend that you enable it. hope can help you thanks,CastinLu TechNet Community Support

hi, I think you can change it to nerver run. But if it not affect your server performance, i recommend that you enable it. hope can help you thanks,CastinLu TechNet Community Support