Odd little problem which I have sort of solved but I don't know why it would have failed in first place.
Using Interorg tool to sync free/busy between two forests with IIFP providing the contacts.
We already had some contacts in each forest which we tested with interorg and free/busy worked ok with them. We then removed these contacts before running IIFP and a full sync of Interorg.
Weird thing we saw then was that some users that had had previous contacts in our forest did then not show free/busy correctly in full Outlook client, we got blank gray boxes rather than the standard hash boxes too. But free/busy worked perfectly in OWA!!!
I cleared the problem by running Outlook /cleanfreebusy against their other forest mailbox and after interorg sync free/busy was fine in Outlook and OWA.
My question is how could this happen when both Outlook and OWA pull the free/busy info from the same folder, albeit an Exchange service does it on OWA's behalf?
Thanks
Neill
Using Interorg tool to sync free/busy between two forests with IIFP providing the contacts.
We already had some contacts in each forest which we tested with interorg and free/busy worked ok with them. We then removed these contacts before running IIFP and a full sync of Interorg.
Weird thing we saw then was that some users that had had previous contacts in our forest did then not show free/busy correctly in full Outlook client, we got blank gray boxes rather than the standard hash boxes too. But free/busy worked perfectly in OWA!!!
I cleared the problem by running Outlook /cleanfreebusy against their other forest mailbox and after interorg sync free/busy was fine in Outlook and OWA.
My question is how could this happen when both Outlook and OWA pull the free/busy info from the same folder, albeit an Exchange service does it on OWA's behalf?
Thanks
Neill