I have 2007 servers left. I don't have any 2003 servers left. Attempting to mail enable the folder using the 2007 tools doesn't work, either.
From: Tom Kern [mailto:tpk...@gmail.com] Sent: Saturday, July 31, 2010 8:01 AM To: MS-Exchange Admin Issues Subject: Re: Public Folders and Decommssioning 2003 and PSS Rob do you have any Ex2k7/2k3 servers around? I ask because most of the public folder tools in Exchange 2010 have enough issues with them where the recommendation now is to use the ex2k3/2k7 tools to make modifications to folders on those servers and let the changes replicate out to the E14 replicas. Until till this is corrected in a future RU/SP you should just use the ESM or the ex2k7 EMS/EMC to make the changes to the folders that reside on those servers. Thanks On Fri, Jul 30, 2010 at 5:18 PM, Campbell, Rob <rob_campb...@centraltechnology.net<mailto:rob_campb...@centraltechnology.net>> wrote: I've got a similar situation, although not as severe. I'm not having the delivery failures, but I cannot mail-enable a legacy public folder. Existing public folders that were mail-enabled before the Servers container was deleted still get email, but any of them that were not mail enabled fail on trying to create the proxy object in AD if you try to mail enable them. If I create a new public folder, I can mail enable that. -----Original Message----- From: greg.swe...@actsconsulting.net<mailto:greg.swe...@actsconsulting.net> [mailto:greg.swe...@actsconsulting.net<mailto:greg.swe...@actsconsulting.net>] Sent: Friday, July 30, 2010 4:06 PM To: MS-Exchange Admin Issues Subject: Public Folders and Decommssioning 2003 and PSS I just got off the phone with a 14 hour PSS call with Exchange in relation to public folders and decommissioning Exchange 2003. Everything was working perfectly, no issues, all folders were replicated. We even shutdown the Exchange 2003 for a few days..No problems. As soon as we uninstalled Exchange 2003 no emails would send to public folders. We would get an NDR, "5.2.0 StoreDRV, MapiExceptionnotFound:16.18969:AB000000" After deleting the empty servers group in the First Administrative Group, using ADSIedit which is a popular issue with Public folder replication, we started getting in the undeliverable queue on 2010, "No route to database" and email would not deliver to any 2003 previous public folders. New public folders would work fine as long as they did not have the email address from the previous 2003 folder." Whats strange is that this has not happened in any of our other migrations. It's a known issue, being fixed in SP1...Their suggestion is to leave 2003 server online until Sp1..In our case, we had to delete all public folders and recreate from backup. Not a huge issue, exported to pst, and then reimported after deleting them all. Didn't know if any of the MVP's could comment.. Greg ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ************************************************************************************************** ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ************************************************************************************************** ************************************************************************************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **************************************************************************************************
