After a number of other hits and misses too numerous and lengthy to explain, I'm back where I started.
If I uninstall the old (first one in the org) server, and PF delivery is broken after that, should re-installing the first server fix it easily enough? Carl From: Carl Houseman [mailto:c.house...@gmail.com] Sent: Wednesday, March 31, 2010 1:24 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 public folder message routing after swing Well... I googled and got this article, http://www.kreslavsky.com/2008/07/exchange-2003-event-log-id8206-with-0x8015 0856-error.html which led me to a SiteFolderServer DN that was pointing to the old server. Corrected that, bounced everything on the new server, and still the messages are queueing up for the old server. Checked to make sure it replicated to all DC's and it had. Seems like SiteFolderServer is something I would have needed to do anyway, but there must be something else? Thanks, Carl From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, March 31, 2010 12:31 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 public folder message routing after swing Gosh talk about trying to remember things from long ago!!!! :-P Check out where the siteFolderServer is pointed. I don't remember exactly which object that is hosted on, but a biggle should bring it up really quickly. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Carl Houseman [mailto:c.house...@gmail.com] Sent: Wednesday, March 31, 2010 12:27 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 public folder message routing after swing I just completed, or so I thought, a swing migration from single-server 2003 to new server also 2003. There are a lot of mail-enabled public folders. I followed the recommendations of setting up replication to the new server, waiting for replication to complete, and then removing the replicas from the old server. All inbound SMTP traffic is now directed to the new server, and none of the mail-enabled public folders are listed for the old server, when looked at with ESM from either server. I also changed the routing group to make the new server the Master, the old server the Member. It all looked good, since new messages were arriving in the newly re-homed public folders. As a test, I shut down the old server. And then all public folder messages stopped arriving on the new server. Where were they queued up? On the new server, trying to be sent to the old server! Start up the old server and now the messages are arriving in the new server's public folders. So messages arrive on new server, are then sent to old server, where they then get sent back to new server. WTF? And I did try bouncing all Exchange services on the new server, in case it was caching something or remembering something it shouldn't. No help. What am I overlooking here? Or will this self-resolve when uninstalling Exchange from old server? thanks, Carl
