Moving Public Folder Replicas to Ex2010

Migrate Public Folders to Exchange Server 2010 from 2003

 
For most Exchange Server organizations migrating public folders is as simple as moving replicas from one server to another. This can be achieved using one of two methods:
  • Moving all Public Folder replicas using the Exchange 2003 System Manager console
  • Moving all Public Folder replicas using the Exchange 2010 Management Shell
Either method will work in just about any scenario, it just comes down to which one you’re most comfortable using.

Moving all Public Folder Replicas to Exchange Server 2010 Using the Exchange 2003 System Manager Console


In this example scenario the public folders hosted on the Head Office Exchange 2003 server are being moved to the Head Office Exchange 2010 Mailbox server.
As with mailbox migrations public folder migrations can generate heavy disk I/O on the source server, and will generate a lot of transaction logging that consumes free disk space on the target server.
On an Exchange 2003 server open Exchange System Manager. Navigate to the server that currently hosts the public folder replicas, and browse to the public folder Instances folder of the public folder database.
Note the public folder instances currently on this server.
Public Folder Instances shown in the Exchange 2003 System Manager console

Public Folder Instances shown in the Exchange 2003 System Manager console
Right-click the public folder database and choose Move All Replicas.

Move all Public Folder Replicas

Move all Public Folder Replicas
Choose the public folder database to move the replicas to.

Choose the database to move the Public Folder replicas to

Choose the database to move the Public Folder replicas to
A warning appears that the move may take a lot of time depending on the amount of public folder content to be moved. Click OK to begin.

Note that moving Public Folder replicas can take some time

Note that moving Public Folder replicas can take some time
You can refresh the public folder instances folder to monitor progress. This operation can take some time, even for a small amount of public folder content. When the public folder instances displays an empty list the operation has completed.

All public folder replicas have been moved

All public folder replicas have been moved

Moving all Public Folder Replicas to Exchange Server 2010 Using the Exchange Management Shell

Public folder replicas can also be moved using the Exchange Management Shell. In this example the public folders hosted on the Branch Office Exchange 2003 server will be moved to the Branch Office Exchange 2010 Mailbox server.
On the Exchange 2010 server open the Exchange Management Shell. Navigate to the scripts folder of the Exchange installation folder.
[PS] C:\>cd $env:exchangeinstallpath\scripts
Microsoft has supplied a PowerShell script called MoveAllReplicas.ps1 for moving public folder replicas. Run the script with the following parameters:
  • -Server is the name of the Exchange 2003 server
  • -NewServer is the name of the Exchange 2010 server
Note that this is a single-line command run from the folder containing the scripts.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\MoveAllReplicas.ps1 -Server ESP-BR-DC -NewServer ESP-BR-EX2010
You can use the same method as with the Exchange System Manager console technique to determine when all replicas have been moved.

Comments

Post a Comment

Popular posts from this blog

How to change the Mailbox Password using shell command

To set a new password for a Mailbox Set-Mailbox -Identity "Mailbox Name" -Password (ConvertTo-SecureString -String "NewPassword" -AsPlainText -Force) and to reset the password on next logon Set-Mailbox -Identity "Mailbox Name" -Password (ConvertTo-SecureString -String "NewPassword" -AsPlainText -Force) -ResetPasswordOnNextLogon $True
Read more

Installing, Configuring Exchange 2007 Edge Server (Part 2)

Image
Installing, Configuring Exchange 2007 Edge Server (Part 2)   In Installing, Configuring Exchange 2007 Edge Server (Part 1) we started the installation of an Exchange 2007 Edge server at the DMZ. So far we installed the Exchange Edge role on a standalone Windows 2003 server. The server is still not connected to the rest of the Exchange organization running internally. Indeed we could employ Edge as the perimeter server even if we were not running Exchange internally. As is, Edge only requires port 25 communications and the configuration of send/receive connectors, to act as a relay to any SMTP server. However, quite obviously, Edge also includes special support for running together with an internal Exchange 2007 organization. This functionality is provided by the EdgeSync service. Running on an internal Hub transport server, EdgeSync pushes information to the Edge server. The following is some of the information transferred; more details are available from the article EdgeSy...
Read more

Managing mailboxes in Exchange Server 2007 (Part 1)

Image
Overview In this article, we are going to approach a simple but important subject: the mailbox user management for Exchange Server 2007. It may seem a simple issue to discuss, but we will see some advanced points related to user management tasks in order to assist beginners and advanced administrators. This article will be split into two parts; in this first part we will review mailbox management and user level functionalities. Creating a mailbox using the Exchange Management Console This procedure is the starting point of this article. Exchange Server 2007 allows administrators to create objects such as Mailboxes , Contacts , Mail Users , and Distribution Groups . In the following steps we will see how to create a mailbox object: Open Exchange Management Console Expand Recipient Configuration Click on Mailbox In the Mailbox pane, click on New Mailbox ... (Figure 01) Figure 01: Creating a new user in the Exchange Management Console Introduction. We have to ch...
Read more