Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2209
  • Last Modified:

Exchange 2010 public folder problem

I am in the process of migrating my users off an Exchange 2003 server to an Exchange 2010.  Many of my users that have been migrated to the new server cannot see objects in the public folders any more.  They can still get into the folder, but it's like it's empty.  Users that have not been migrated can still see object in the public folders.  Could it be a replication issue?  If so, how do I check that?  I have made sure that replication is set between the old and new server (I think) but I am not sure the replication is happening.  Advice anyone?
0
lgeccuex
Asked:
lgeccuex
  • 7
  • 7
1 Solution
 
terminateallCommented:
1) Do you see the Public Folder Hierarchy in Exchange 2010 server under "public Folder management console"?
2) Did you added replicas to all Public Folders in Exchange 2010?
3) To get the PF replication working, you need to make sure that the mail flow between the Exchange 2003 and Exchange 2010 (vice-versa) is working.
0
 
lgeccuexAuthor Commented:
1.  I do see the Public Folder Hierarchy.
2.  I went through the properties of every Public Folder on the 2003 box and checked the 2010 server in the replication tab.
3.  I can send mail to (and between) both the 2003 and 2010 boxes.
0
 
terminateallCommented:
Now double check on Exchange 2010 Public Folders if you can see replicas of both the servers or not.

Set the replication schedule to always run and priority to urgent if PF size is not Huge.

Then go to the Exchange 2003 System manager Right click on the PF tree and click to resend changes.

Check the queues on both the servers if there are any messages stuck.
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
lgeccuexAuthor Commented:
"Now double check on Exchange 2010 Public Folders if you can see replicas of both the servers or not." I still don't see items in the public folders in Outlook, if that's what you mean.

"Set the replication schedule to always run and priority to urgent if PF size is not Huge." Done.

"Then go to the Exchange 2003 System manager Right click on the PF tree and click to resend changes." Done.  Soure 2003 Destination 2010

"Check the queues on both the servers if there are any messages stuck."  Done.

Still nothing.  I have restarted Outlook and rebooted just to be sure.  Nothing.







0
 
terminateallCommented:
On Exchange 2010 power shell
Run :-

get-publicfolderstatistics | fl

You will get the list of the public folders and their size and number of items.

0
 
lgeccuexAuthor Commented:

All of them say this:

AssociatedItemCount      : 0
0
 
terminateallCommented:
Have you compared the size of the databases on both the servers.
Also Do you have exchange 2010 SP1 and what update roll ups?
0
 
lgeccuexAuthor Commented:
Yes, I'm all up to date.  The public folder data is much bigger on the old.  It's definatly a content replication problem, but I don't see anything in the logs.
0
 
terminateallCommented:
Turn off Antivirus if you have any from both the servers and reboot..
You can also download PFDAVADMIN tool and run on the Exchange 2003 server. And perform the Following:-
1) Fix Folder DACLS
2) Remove Item Level permission if you don't want them.
0
 
lgeccuexAuthor Commented:
That doesn't seem to have any effect, however I did get this error from the PFDAVADMIN tool when I tried "probogate replica list"

************** Exception Text **************
System.Exception: Could not find server in msExchOwningPFTreeBL
   at pfdavadmin.AdsAccess.GetLegacyDNFromServerName(String serverName)
   at pfdavadmin.Form1.PropagateReplicas(TreeNode node, Boolean noReplicas)
   at pfdavadmin.Form1.propagateReplicas_Click(Object sender, EventArgs e)
   at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.MenuItemData.Execute()
   at System.Windows.Forms.Command.Invoke()
   at System.Windows.Forms.Control.WmCommand(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.TreeView.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Could it be related?
0
 
terminateallCommented:
OK...go to adsiedit.msc from a domain controller and browse to the location.

Cn=COnfiguration---services--Microsoft Exchange----Your ORG NAME---Administratove Groups---Exchange Administratove Group--Folder Hierarchies--cn=Public Folders
Go to properties and check the attribute "MSExchOwningPFTreeBL"

If you cannot finr Folder hierarchies under Exchange Admin Group then check it under First Admin Group/

0
 
lgeccuexAuthor Commented:
Both the new and the old servers are listed.
0
 
terminateallCommented:
Try to follow thos article:-
http://support.microsoft.com/kb/842273
Also increase the diagnostic logging for PF replication and check the event viewer.
0
 
lgeccuexAuthor Commented:
I managed to side-step the whole issue by moving all public folder replicas to the new exchange server.  After I did that, everyone (new and old) could see everything they needed to see.  Thanks for all your help!
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 7
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now