Hi I have set up synchronization between two Exchange organizations; one Exchange 2003, the other 2007. I use IIFP (Identity Integration Feature Pack) to synchronize the recipients between the orgs, this works very well. Users in one org can see all the users in the other, and vice versa, in their respective address books. Mail flows between the orgs without problems. I also set up the Inter-Organization Replication Tool (InterOrg) to sync free/busy info, and here is my problem. InterOrg can successfully run, log on, read the PFs it need to etc, but all the data in either org is never replicated. When I start it up it tells me it succeeded, but I have several hundred messages in the Msg Ignores colum, and none in the others. This happens for both replication directions (I have two sessions in the config file). The kicker is that I set this all up in a lab environment before installing it in production and it all works in the lab. Granted, the configurations are not entirely similar, but very close. So I wonder; - Anyone experiencing this, or know what is causing it? - Anyone know what Msg Ignoers means? I can find no documentation for this. My theory is that somehow the tool is not able to match any of the IIFP synchronized contacts to the mailboxes. According to the documentation I can find the SMTP address is used to match, but I have checked several users and all SMTP addresses match! Thanks Morgan

Exact same problem here in my test environment. I am trying to get information from my Exchange 2003 Organization to replicate to my Exchange 2007 Organization. I have triple checked all of the settings, accounts, perms. According to event log and Replication tool log, everything is fine, but nothing is actually replicated. Have you found a solution to this problem?

Hi Matty Still struggelig with this issue. It works in my test environment, but not in the production system. I have logged a case with Microsoft PSS but they have yet to come up with an answer. Last I heard they were going to escalate my case to the US (I'm in Europe so I have had to go through the European support first). One thing I have observed is that this is related to the legacyExchangeDN attribute. InterOrg tools uses this attribute to match free/busy data to a recipient, if it finds none the Free/Busy messages end up in the ignore column. One thing you can try, since you are trying to move data from E2K3 to E2K7 is the Update-Recipient cmdlet. I missed that step in my setup, but it is actually a required step for proper IIFP synchronization with IIFP/MIIS. Have a look at the info at this link: http://technet.microsoft.com/en-us/library/aa998597(EXCHG.80).aspx. After I implemented this free/busy information started replicating from E2K3 to E2K7. I will update this thread when we reach a conclusion. Hope you sort it out. Best regards Morgan

Well the legacyExchangeDN field is populated, so no problems there. Just to make sure I wasn't going insane, I setup the Replication to replicate a temp folder I made (as we don't use public folders) and it worked fine. So why doesn't it work for FREE / BUSY? By the way, I am NOT using MIIS or IIFP to generate contacts for the other Forest. I am manually creating a single contact for a single user to see if it works. Does anyone one know if you need EVERY user setup as a contact before using InterOrg. I did assume that it would just fail for the other users and perform the sync for the user contact I created.

It wasn't that the legacyExchangeDN was not populated that was the problem, it had the wrong value. In my setup I have two Exchange administrative groups. The server I wanted to replicate to (running Exchange 2003) was in the second group, but all my contacts (representing users on Exchange 2007) had a legacyExchangeDN as if they belonged to the first administative group. If I manually changed one contact object's legacyExchangeDN to match the second admin group, InterOrg could replicated the free/busy info. I think you still need to use Update-Recipient to make sure that the contacts you have created manually are fully provisioned. It may be that you are missing some data that RUS normally would add for you. As you know, there is not RUS in Exchange 2007. Morgan

I still ran update-recipient to make sure and still no go. I should have been a little clearer when I mentioned the legacyExchangeDN... It is populated correctly. My test setup is fairly simple... a Single AD forest and Exchange 2003 Org and a Single AD Forest and Exchange 2007 Organization. Let me know if you find anything out... I may call support services tomorrow as this is the only thing standing in the way of my migration from Unix to AD (FINALLY!) so I don't want to wait any more. Thank god the logging for InterOrg is so Verbose! Bah!

Ok, So the replication works PERFECTLY going in one direction only. From Exchange 2007 to Exchange 2003. However, from Exchange 2003 to 2007 it says it processed 1 MSG CHANGE however, it can't find the free busy info. So according to the tool, it replicated, but Outlook shows "No Free/Busy Information". I am not sure why it start working in the one direction, but I am not touching it. Brutal.

And my final piece... So I actually setup an Outlook 2003 client to connect to my Exchange 2007 Server. Turns out, if I do that (which means Outlook is using the Public Folder store) it works. So InterOrg wasn't lying when it said it replicated information to Exchange 2007. However if I use a client that is using the availabilty service, it doesn't work and just gives me the familiar "No Free/Busy Information". I guess I have to read up on how the availability service interacts with the SCHEDULE+ FREE / BUSY system. I am going to leave this sucker on all night and see if it grabs the information from the Public Folder store and makes it available to the Availiblity Service. Who knows?

According to this Microsoft document at page 32. We're all out of luck with Exchange 2007 as a replication partner. http://download.microsoft.com/download/6/0/1/601c4aec-76eb-4626-b730-eafc548ac378/ExchangeServer2007_APC_chapter_02.pdf Exchange Sever 2007 does not support the Novell GroupWise connector for Exchange Server 2003 or the use of the Inter-Organization Replication tool to share free/busy and public folder data across forests. If you require these features, you must keep at least one Exchange Server 2003 server in your organization.

Umm... This actually was working for me without problems anymore. I was getting alot of ignores because there was no changes to the calendar (i am an idiot)... as soon as I made changes to the calendar on the 2K3 side and closed outlook, the rep tool saw the change and pushed it to the public folder store on E2K7. The reason I was getting Free/Busy unavailable messages was because the /PUBLIC directory on my test box had SSL enabled and because my test box had the CAS and MBX roles installed, it would generate an error. This is a problem with the MS documentation as they forgot to mention to DISABLE SSL on the /PUBLIC directory when using the CAS and MBX roles on the same iron if you need to view Free/Busy from a replicated Exchange 2003 organization. In my deployment config, I will be using a pair of CAS' and an MBX cluster, so I won't run into the SSL problem. Test Setup: Exchange 2003 SP2 on Windows 2003 SP2 using Interorg replicating to Exchange 2007 default install on Windows 2003 x64 R2 SP2... I think that document you linkedis referring to the fact that E2K7 doesn't use public folders, however as long as the public folder is there, it works. As well, I was NOT using IIFP or MIIS to sync, I was manually creating the contacts. -M