We have a forest with multiple domains and multiple sites serving several companies of same conglomerate. We have one Exchange 2010 organisation (recently migrated from Exchange 2007) where my exchange servers 2010 (seven servers) are located in two main sites (something like double-star physical structure). Due to an existence of legacy clients (outlook 2003) in "only" one domain, we keep a replica of (empty) public folder to support them on one specific server. We have removed the mailbox database referal to public folder server in all MB db, except for the database that supports these legacy clients (this database supports users from that specific domain only). All OAB are web-based distributed. After some monitoring, we observed all outlook 2010 and outlook 2007 clients from all sites are trying to open session with this server (as they were looking for the public folder).
Is this an expected behavior? Could be some "dirty" information in the public folder? How can we change it, once this behavior is resulting in both performance and security issues.
Presently, to minimize these issues, we have created a copy of the public folder on another server in the "second site" (the traffic between the two main sites are strongly controlled). But I don't believe this is the best solution.