How to Move Public Folder Content from one Public Folder Database to Another Public Folder Database

[Caden]

Move all public folder content in a database to a new public folder database To move all public folders in a public folder database to a new public folder database, use the MoveAllReplicas.ps1 script. This script replaces a server with a new server in the replication list for all public folders, including system folders.

Move content in a tree of folders from one server to another To move all the replicas of a public folder subtree from one server to another server, use the ReplaceReplicaOnPFRecursive.ps1 script. This script adds a new server to the replication list for a public folder and all the folders that are beneath it in the hierarchy. If the server is already listed in the replication list for a folder, nothing is changed for that folder.

Before You Begin :

To perform the following procedures, the account you use must be delegated the following:

To move all public folder content from Server01 to Server02, run the following command:

Exchange Server Administrator role and local Administrators group for the target server.

MoveAllReplicas.ps1 -Server Server01 -NewServer Server02

To use the Exchange Management Shell to move content in a tree of folders from one server to another

To move the public folder called Legal and all of the folders within that hierarchy from Server01 to Server02, run the following command:

ReplaceReplicaOnPFRecursive.ps1 -TopPublicFolder "\Legal" -ServerToAdd Server02 -ServerToRemove Server01

[jasonR]

rehome public folders

1. If the home server locations cannot be determined, install Exchange Server on another server with the Pub.edb file that was backed up before the rehoming occurred. Then manually check the home server of the public folders. You can also use the Pfinfo utility to list the permissions and the home server location on the temporary server.
   
   
   
   • Install a server in the domain as a backup domain controller (BDC).
   • Disconnect the computer from the network, and promote it to a primary domain controller (PDC).
   • Change the Computer name, and install Exchange Server with the same organization and site name. Use the same service account and password.
   
   
2. On the Exchange Server computer where the public folders have rehomed, go to the following sub-node on the administrator tool:
   
   Configuration\Servers\Servername\Public Information Store
   
   On the File menu, click Properties, and then click the Instances tab. Move the public folders from the left side to the right side to rehome the public folder.
   
3. For each public folder that you want to rehome, type the following command at a command prompt, and press ENTER:
   
   

   pfadmin profile rehome folder path site\server

   
   where profile is a user profile that is assigned the Service Account Admin role on the source and destination servers, folder path is the path of the public folder, site is the name of the new home site, and server is the name of the new home server. Note that the Yes option specifies that subfolders below the public folder also be rehomed. If you do not want the subfolders to be rehomed, use the No option instead.
   
4. After all the public folders are rehomed to the original servers, allow enough time for replication to complete to the destination servers. The rehoming must be done to the previous home server. The data is still available on the previous home server. After replication occurs, the Pub.edb file on the destination server has the updated home server but the Dir.edb file does not have the updated information. If the public folder is rehomed to the wrong server, placing a replica of the public folder on the server with the "ghosted" data enables the data to be replicated back to the newly homed server.
   
5. On every server where a public folder is rehomed, DS/IS Consistency Adjustment must be run to populate the Dir.edb file with the updated home server name.