I have installed a new Exchange 2003 SP2 server and have migrated all user mailboxes. Everything is working normally. My last task before taking old server offline is to migrate the public folders. I have setup replication but while the folders have been created on new server the folders are empty.
One thing that may be hanging me up is when in System Manager if I right click a public folder and view All Tasks, Manage Settings is greyed out preventing me from starting the Manage Public Folders Wizard.
Any clues where to start?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
As Mestha says, check the SMTP virtual server first.
Also turn up the Replication logging level to Maximum in System Manager and check the server Application Event Logs.
These two articles have some handy info:
http://msexchange.org/arti
http://msexchange.org/arti
Ok, we're getting somewhere...
Checking email sent by appserver-is (old server with PF data) I see email being sent to new server but it ends with an NDR. Specifically:
Your message did not reach some or all of the intended recipients.
Subject: Folder Content
Sent: 2009-07-31 9:00 AM
The following recipient(s) could not be reached:
Public Folder Store (APPSERVER) on 2009-07-31 9:00 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<appserver.torringtonsupply
So, permissions are inadequate for exchange-is? If so where do I check?
How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
http://support.microso
Publ
http://msexchangeteam.com/
You can also check the WebCast at
http://support.microsoft.c
Please let us know if this helps you in anyways
Sorry, but I chickened out. The solution was looking to be more trouble than it was worth since I really don't need replication as I will be decommissioning the old server. I moved a mailbox back to the old server, opened Outlook as that user, and exported public folders to pst files. There were only 5 folders so it was no big deal. Logged back into Outlook on the new box and imported the pst's no problem.
Thanks for the quick replies and I will split up the points.
BUT....this was not a complete solution. Synchronization errors began to show up even though the Public Folders were available and correctly populated with data. Since I needed to tie this off once and for all, I bit the bullet and paid the $259 for a Microsoft support case.
First thing the engineer did was to download and install the Microsoft Exchange Best Practices Analyzer.
http://www.microsoft.com/d
Had I known there was such a (free) tool available I could have avoided this whole mess. It is a wonderful tool that identifies problems and anything that does not conform to their best practices and immediately offers suggestions on how to correct. In my case I added a replicate for OFFLINE ADDRESS BOOK / o=First Organization but not the 3 OAB sub folders. Added the 3 additional replicate locations and everything was good.
So, in hind sight, running the Exchange Best Practices Analyzer should have been the first thing I should have done on the new server, not the last. Live and learn!!
Business Accounts
Answer for Membership
by: MesthaPosted on 2009-07-31 at 06:36:21ID: 24988620
Greyed out usually means you don't have permissions.
However that wouldn't stop replication of traffic.
The most common reason I see for replication failing is a smart host on the SMTP virtual server of the original server. The second most common I see is AV or antispam quarantining the content.
Have you message tracking enabled? If not then you need to. You can then check to see whether the replication traffic is being generated and delivered correctly. The traffic is easy to spot through the message tracking center - SERVERNAME-IS is the sender.
Simon.