Friday, May 14, 2010

Replicate Public folders Between Exchange 2003 and 2010 Organizations Using the Interorg Replication Tool

By:Rik Hoffelder
I wrote in my article, Cross-Forest Migration with Exchange 2010 is a Piece of Cake! that it is possible to synchronize public folder and free/busy data between Exchange 2003 and Exchange 2010 Forests using the free Interorg Replication Tool. Since that time I have received a few questions on how I set that up and got it working. So by popular demand, here are the steps I used along with screenshots to help get you going.


First, a little background on the environment
In my lab, as was the case as the production enviroment, I had Exchange 2003 running in a single domain Windows 2003 forest, set at Windows 2003 Functional Level. Exchange 2010 is running in a single domain forest with Windows 2008 domain controllers, functional levels also set to 2003. A Cross-Forest Trust was established, SIDHistory filter security relaxed with the intent of migrating all domain resources to the new forest, including Exchange 2010. The Active Directory Migration Tool (ADMT 3.2) was used to migrate user accounts, groups etc as noted in Cross-Forest Migration with Exchange 2010 is a Piece of Cake! and mailbox GUIDs updated to prepare for the mailbox migration.

Setting Up Interorg Replication
To preform the steps outlined below I was running version 6.5.7408 of the Interorg Replication Tool from the Exchange 2003 Toolkit, Exchange 2003 SP2, and Exchange 2010 with Rollup 1, though it should work with Rollups 2 or 3.

1. Create a user account and mailbox to be used for the process in the Exchange 2003 organization. This account must be granted Owner rights on every public folder that you plan to replicate. For my purposes I used the EX2003\Administrator account, though not the most reocmmended for security reasons.

2. Create a user account and mailbox to be used for the process in the Exchange 2010 forest. This account must be granted Owner rights on every public folder that you plan to replicate. For my purposes I used the EX2010\Administrator account, though not the most reocmmended for security reasons. (NOTE: The public folder hierarchy must already exist in the Exchange 2010 forest, so you will need to pre-create the folders you will replicate from 2003.)

3. Create a top-level public folder named ExchsyncSecurityFolder in the Exchange 2003 organization. Assign the account created in step 1 Folder Visible rights only. Remove all other access rights for all other accounts.



4. Create a top-level public folder named ExchsyncSecurityFolder in the Exchange 2010 organization. Assign the account created in step 2 Folder Visible rights only. Remove all other access rights for all other accounts.



5. Install the Interorg Replication Tool replication service on the Exchange 2003 public folder server by running EXSSRV.EXE from the toolkit. Click the Create button which will install the service on the server. In my case I used the EX2003\Administrator account as the service account. I had problems when using local system. Administrator is also a local admin and Exchange Full Administrator



6. Open the Interorg Replication Configuration tool by running EXGCFG.EXE. Click File -> New to create a new Exchange Sync Configuration file (.esc). Click Session from the menu bar then click Add - Public Folder Replication.

7. In the Public Folder Session Configuration window enter PF 03 -> 10 in the title field to indicate 2003 public folders replicating to 2010. In the Publisher Organization section enter the Exchange 2003 public folder server and the mailbox name you created in step 1. In the Subscriber Organization section enter the name of the Exchange 2010 public folder server and the mailbox name you created in step 2.



8. Click the Advanced button under Publisher Organization then enter the credentials for the account you created in step 1. Click the Advanced button under Subscriber Organization then enter the credentials for the account you created in step 2.



9. Click the Folder List button. Click the Logon button under Publisher Public Folders and the Logon Button below Subscriber Public Folders. This will allow you to view the available folders in both organizations. Select a top-level folder under Publisher Public Folders and click the Add button. Repeat this for each top-level folder you plan to replicate.




10. Click Session from the menu bar then click Add - Schedule+ Free/Busy Replication. Repeat steps 7 through 9 to replicate free busy from 2003 to 2010.

11. Repeat steps 7 - 9 instead using Exchange 2010 as the Publisher and Exchange 2003 as the Subscriber to allow reverse replication. Do this for both public folders and free/busy. When the process is complete you will have at least 4 sessions in your configuration as shown below:



12. After completing this you can now monitor the process (I have mine running every five minutes in the lab, hourly in production) using the EXGSRV.EXE console.



For additional information on Interorg Replication Tool configuration and implementation I recommend checking out the full TechNet article here.



More information on Exchange


11 comments:

  1. Hi Rik,
    i followed your instrucctions but i´m still not able to browse the public folders at the subscriber side. The only difference is, that our trust settings are not relaxed.
    Regards,
    Felix

    ReplyDelete
  2. For those of us having the infamous "Unable to logon to Exchange server using mailbox information" error, try disabling the encryption requirement on your CAS servers. That is what did it for me, it's not documented yet on any MS article. Perhaps it's because it only applies to Ex2010.

    ReplyDelete
  3. Hi Rik,

    Were you actually able to get Free/Busy info working between Ex2003 and Ex2010? The IORepl tool is reporting "successful" for the Free/Busy replications but there is no information available in either orgs.

    Thanks,
    Hyu

    ReplyDelete
  4. Hi Rik,

    please could you help, you say:
    (NOTE: The public folder hierarchy must already exist in the Exchange 2010 forest, so you will need to pre-create the folders you will replicate from 2003.)

    i have hundreds; does this mean i need to manually create the hierarchy first? or is their another method.

    thanks
    Simon

    ReplyDelete
  5. I have found this on MS Exchnage Team Site (http://msexchangeteam.com/archive/2010/08/10/455779.aspx)

    The Availability service is supported only for Outlook 2007 clients and newer. If Outlook 2003 clients still exist in one of the forests, the only solution will be to deploy Exchange 2007 first in the Exchange 2010 organization (because adding it late is not possible if Exchange 2010 is deployed first) and implement the IOREPL tool to replicate Free/Busy system public folders to the Exchange 2007 server. The Free/Busy system public folder replicas can then be replicated using PF replication to your Exchange 2010 server. IOREPL will not replicate a public/system folder directly to an Exchange 2010 server.

    Rik, are you saying we can get around this?

    Help appricated
    Simon

    ReplyDelete
  6. Hi Simon,

    Unfortunately yes, you will have to recreate the hierarchy, IOREPL will not do that for you. It only allows you to map one folder to another.

    There are a couple ways around it. First you can automate it by building a CSV of the source folders and feed into a Import-CSV | Foreach {New-PublicFolder ...} cmdlet. You can run the Export List off the Admin Group\Server\Storage Group\PF_DB\Public Folders container in ESM to get the source folder information.

    What I did, because they were small enough (like I said in the "Piece of Cake" article, I only did this becuase they were very small, can't recommend it for anything of any real size) was to export all PFs into a PST then imported on the other side. I used IOREPL to sync permissions and on going changes until I ran the cutover. I didn't note that in the article, though I probably should have.

    BTW: Thank you posting the information about FB info from MSExchangeTeam. I didn't know that, but I also didn't encounter the problem. The F/B data was populated into Ex2010 when I moved the mailboxes. I never ran this as a co-existence environment, I moved everything over one weekend in a cutover operation. Like I said they were very small. I don't recommend co-existing beyond testing with this method, rather you should use third party tools. Much less chance for error and problems.

    Rik.

    ReplyDelete
  7. Hi Rik,

    Thanks for the repsonse. I will take your advice on migrating the public folders, very much appricated.

    The free/busy info is conflicting from MS; all the testing i have done so far has shown the mailbox moves includes the calendar info, then i have been running "outlook.exe /cleanfreebusy" on users machine at first logon after the move, which seems to do the trick.

    Your blog on the the migration; has really helped me progress, thank you for the great help and info.

    Kind regards

    Simon

    ReplyDelete
  8. This works like a charm. We tried everything we could to make the replication work but no lucks until we found this article. It's awesome. Thanks

    ReplyDelete
  9. Hello,

    Great article. Will this work with Exchange 2010 SP3 > Exchnage 2010 SP3 Cross-Forest?

    Cheers

    ReplyDelete
  10. Does it work with Exchange 2003 to Exchange 2010 on the same forest?

    ReplyDelete
    Replies
    1. It isn't necessay in the same organization. Just use the built-in PF replication by adding a replica to all sources PFs you want to move to 2010.

      Delete

Microsoft Virtualization, Citrix, XENServer, Storage, iscsi, Exchange, Virtual Desktops, XENDesktop, APPSense, Netscaler, Virtual Storage, VM, Unified Comminications, Cisco, Server Virtualization, Thin client, Server Based Computing, SBC, Application Delivery controllers, System Center, SCCM, SCVMM, SCOM, VMware, VSphere, Virtual Storage, Cloud Computing, Provisioning Server, Hypervisor, Client Hypervisor.