Small Business Susan

Public folders revisited….

Public folders revisited….


You must wait for the next instance of public folder replication to complete before the public folder replicas are removed.


To verify that all public folders have been moved to the Destination Server


  1. In the Source Server, open Exchange System Manager, expand First Administrative Group, expand Servers, expand ServerName, expand First Storage Group, and then expand Public Folder Store(ServerName).

  2. Click the Public Folder Instances node. After all of the public folder replicas have been moved, the Public Folder Instances node will be empty.


Depending on the replication interval that you set and the amount of information that must be replicated, this process can take several hours or several days to complete.


So what public folder replication resources do we have?


First off make sure you’ve kicked up the replication priority so that they will go.  If you have a huge public folder don’t do this during business hours .. mind you normally it’s recommended to let Exchange move it’s thing overnight anyway…


Go into the public folder instances and on each public folder, right mouse click, go to the replication tab and mark it urgent



Be careful with reading some of the information — http://msexchangeteam.com/archive/2010/05/05/454821.aspx they don’t want you to remove the legacy administration group here so don’t go nuking things in an attempt to get public folder replication to move faster.


http://msexchangeteam.com/archive/2007/06/25/445429.aspx


More troubleshooting resources here:


Troubleshooting steps for PF Replication issues
1) Check the Mail Flow between the Source server and Destination Server.(since Public folde replication happens via email messages)

1a) Run Exbpa and check Application and System Logs.

2) Check if Content is not Replicating or Hierrarchy is not Replicating.

3) If Hierrarchy is Not Replicating then,

3a) Create a test Folder and Check If it is Replicating.

3b) Check the basic Settings under the Properties of Default SMTP Virtual server in ESM. (smart host, FQDN)

3c) Check if there is any Third party Anti-virus Application is Installed, if yes then,
Go to the Following Registry->HKEY_LOCAL_MACHINE\System\Current Control set\Services\MsExchangeIS\Virus Scan
On the right hand side zero out the following values:- 1) Background Scanning
                                                                            2) Enabled
                                                                            3) Pro-active scanning (make sure that there are no mobile device users.if so then, u will have to set this value to 1 after reboot)
Set Exclusions on Antivirus so tha it should not Scan all Exchange folders and inetsrv folder.
Reboot the server and the status. (IF antivirus is Installed on both source as well as Destination then Set the Registry and Exclusions on Both servers and reboot)

3d) Check if the Source Server Has SEND AS and RECIEVE AS Permission on Destination Server.

3e) Check If There Is any Inheritance Blocked on Public Folder Store.

4) Public Folder hierarchy Should replicate after following Step 3.

5) Bounce the Diagnostic loggings For Public Folder Troubleshooting. http://support.microsoft.com/kb/842273/en-us

6) If Public Folder Content Is Not Replicating then, Try to post Some Contents in the Test Folder you created in step (3a).

7) Check If New Items are Getting Replicated or the issue is with New Items as Well As Old Items.

8) If New Items are Not Getting Replicated Then Follow Exbpa Report and Application logs for Error Messages.

9) Check If the Replica of Destination Server is Added on the Public Folders.

11) Run PFDAVADMIN.exe (on Exchange 2003)  to:-1) Check the DACL State
                                             2) Check Item Level Permission
                                             3) Propogate Replica List 


(stolen from here – http://forums.msexchange.org/Public_Folder_Replication_2003_%26gt%3b_2007/m_1800495757/tm.htm)


 



1 comment so far ↓

  • #   Robert on 02.16.11 at 8:54 am     

    12) When all else fails, replicate manually (Been there, done that
    )