Recipe 9.2. Rehoming Public FoldersProblemYou want to move a folder from one server to another. SolutionUsing a graphical user interface
Using a command-line interface
DiscussionRehoming a public folder is simple: you're just moving it from one location to another. To accomplish this, you merely add a replica on the desired server, wait for its contents to replicate, and remove the original. Recipe 9.1 describes a tool that can automate this process for multiple folders, but sometimes all you want is to move a single folder. The process works the same way whether you're rehoming ordinary folders or one of the system folders described in the introduction. You could easily write your own script to do this, using the code in Recipe 9.10 as a base. However, there are a few quirks. First, your script needs to wait for replication to finish before removing the original. One way to do this is to check and make sure that at least one other server has a replica of the target folder (and that it is a complete and up-to-date replica) before removing the source server's replica. Another, more serious, problem: if you want to move public folders between sites/routing groups in a mixed-mode organization, you have a lot of work to do. In that situation, you'll come out ahead if you rehome your public folders using the PFMigrate script described in Recipe 9.1. As an alternative, you can also use PFAdmin or PFDAVAdmin to do the rehoming for you. In any event, before you rehome any critical folders, it's usually a good idea to make an extra backup, just in case. See AlsoRecipe 9.9 for finding replicas of a public folder, Recipe 9.10 for manipulating a server's replica list, and MS KB 288150 (XADM: How to Rehome Public Folders in Exchange 2000) |