Exhange 2010 SP1 supports InterOrg, but it’s important to stress that although Exchange 2010 SP1 includes support for the InterOrg tool, you need to do the following to get it working:
- Use a 32-bit based Windows 2003/R2 Server
- Install the Exchange 2003 System Manager on the machine running InterOrg
- If enabled, disable the RPC encryption requirement on the CAS server used by InterOrg
- One of the InterOrg endpoints need to be an Exchange 2003 server (no direct Exchange 2010 < > Exchange 2007 replication)
The old InterOrg (IORepl) tool doesn’t work directly against Exchange 2010. Well, here’s the deal. You will be able to configure the tool and get public folder data to replicate, but free/busy info will not.
This is important to bear in mind if you think you at some point in time need to provide free/busy sharing between Exchange 2010 and Exchange 2003 (or earlier) orgs. In that case, you need to point InterOrg at a legacy server (Exchange 2007 or 2003) located in the Exchange 2010 organization.
So I guess we have one more reason to introduce an Exchange 2007 server before we deploy the first Exchange 2010 server in a new Exchange 2010 org. Or keep a legacy server around if you’re doing an upgrade (formerly known as a transition) from Exchange 2003 or 2007 to Exchange 2010.
Will this issue be fixed? Well time will tell. There is a bug opened for this, but we all now the Exchange Product Group is busy with Exchange 2010 SP1 and many other things 🙂
Thanks to Nino Bilic for this tip.