We faced the following issue:
We have Exchange 2003 and Exchange 2010 servers in our organization. We still use public folders, some of them are mail-enabled and receive e-mails from outside the organization. Couple of years ago we had Public Folders in Exchange 2003 environment with replicas on 2 servers. When we installed the first Exchange 2010 Mailbox (EXCH1), we made Public Folder database (PublicStore1) on it. First we made replicas only for System Public Folders to PublicStore1. Then our users started to complain that mail-enabled public folders didn't receive any messages from the Internet. According to message tracking logs, messages weren't delivered because of
420 4.2.0 No local replica for public folder
We added replicas for Default Public Folders as well to PublicStore1. Then Mail-enabled Public Folders started to receive e-mails from the Internet.
Exchange 2003 servers with replicas, EXCH1 (with PublicStore1) and Exchange 2010 Hub-Transport server which receives e-mails from the Internet are in Default-First-Site.
Now after several years we want do delete EXCH1 server. We installed Exchange 2010 Mailbox server (EXCH2), but in another AD-site (we have HT and CAS servers in this new AD-site as well), made PublicFolder2 on it, made replicas for System and Default Public Folders on PublicFolder2, changed Default Public Folder in properties for all Mailbox Databases to PublicFolder2, moved OAB generation to EXCH2. Everything worked fine. So we started to delete replicas from PublicFolder1 and... received
420 4.2.0 No local replica for public folder
for messages for mail-enabled Public Folders again!
The difference between EXCH1 and EXCH2 is that they are in different AD sites. So Hub-Transport from Default-First-Site couldn't put e-mails in Public Folder database in another AD-site?
Could you please help me to solve the issue? We really need to rid of EXCH1, but we can't because of mail-enabled Public Folders. And we can't change AD sites for any servers because of business purposes.