firstly, I would like to say I have read the suggested threads already existing on technet for this problem, however this free/busy folder replication issue is a little different to those listed as they are single exchange 2010 mailbox server scenarios.
In my environment I have a 2003-2010 exchange coexistance setup. The 2010 environment has 2x CAS+HUB servers (in CAs array), and 2x MBX servers (in DAG).
Only one of those 2 MBX servers holds the public folder database (this db is not replicated to the second MBX server). These "Couldn't find an Exchange 2010 or later public folder server with a replica for the free/busy folder" messages appear only on the second MBX server. They do not appear on the first mailbox server (which holds the PF database)
I've opened the PF management console and checked the "SCHEDULE + FREE BUSY" folder properties under System Public Folders and under the replication tab, it is configured to replicate to the exchange 2003 "Public Folder Store" with the setting is "Always Run". (fyi, replication is confirmed as 'Always Run' on both MBX servers via the PF Management console)
Interestingly however, when try to delete the current replication folder within this replication tab, and then click "OK" to apply the changes, it comes up with "Error: you must specify a value with the replicas parameter". and subsequently wont let me apply these changes.
as for other reasons for this free/busy folder error message, I note from this article here: http://www.petenetlive.com/KB/Article/0000446.htm that it states this error is due to: "a) you have Older Outlook clients (2003 or earlier) in your Exchange org, or b) Someone forgot to replicate this public folder over to Exchange 2010 when you upgraded."
of the new exchange 2010 environment, i have only migrated over 4 'test' mailboxes of departed users across the two databases on both MBX servers (1 unique mounted database per mailbox server; with replication via DAG). so their mailbox was pre-existing on 2003 but their mailboxes are no longer accessed by any outlook client.
again, this error only occurs on one of the two MBX servers
comments?
