Problem with Sync Connector and replication of Free/Busy from Exchange 2003 to Exchange 2010

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Running Webservice and Sync on Exchange 2003 front end server, mixed with 
Exchange 2010
2. All Google Apps user mailboxes were migrated from Exchange 2010
3. Free/Busy folders setup to replicate from 2003 to 2010 Public Folder 
Database and vice versa

What is the expected output? What do you see instead?
Expect to see free/busy information from Google Apps users to be visible on 
their old Exchange 2010 mailboxes. Instead, we see the information for these 
users from mailboxes that reside on Exchange 2003.

What version of the product are you using? On what operating system?
Latest versions of Webservice and Sync connectors, Exchange 2003 on W2K3 and 
Exchange 2010 on W2K8 utilizing a CAS and a DAG.

Please provide any additional information below.
Webservice connector is working great, although takes about 30 minutes for 
events scheduled by Exchange 2010 users to be visible to Google Apps users. 
While we transition from Exchange 2010 to Google Apps, we need users in both 
Google Apps and Exchange 2010 to see free/busy information. Have reviewed all 
logs and diagnostics and event logs and there are no errors. Information from 
Google Apps users (who were migrated from Exchange 2010) is only visible to 
users with mailboxes on Exchange 2003. That information is not visible for 
users with mailboxes on Exchange 2010 from Outlook 2007, Outlook 2010 or OWA.

Original issue reported on code.google.com by hittlem...@themarsagency.com on 18 Dec 2011 at 2:22

[GoogleCodeExporter]

If a user's mailbox exists both on Google and Exchange, both systems would keep 
overwriting each other's free busy information published to Public folder. You 
can not have the same user on both the systems.

Original comment by jaideepg...@google.com on 23 Dec 2011 at 2:34

[GoogleCodeExporter]

I am having a similar problem.  When you say that the mailbox cannot exist in 
both exchange and google what configuration changes are necessary on the 
exchange side?  I have been trying to get our exchange users to be able to see 
the free/busy info for our google users for a couple of weeks now and so far 
have been unsuccessful.
we have exchange 207 running with a public folder database.
Latest versions of web and sync connectors.
Thanks

Original comment by rbertr...@pima.edu on 26 Jan 2012 at 7:58

[GoogleCodeExporter]

This would be a problem when Exchange and Google domain name are same and a 
user exists on both the system. So if you write the free busy of this Google 
user to the Exchange server, who also has the mailbox on the Exchange server 
with the same email address, then it would overwrite the free busy written by 
the Exchange Server for this user. Next time when Exchange Server writes free 
busy to PF, this will overwrite Gcal user's free busy.
One way is to create a contact in Exchange for Gcal user with the different 
email address (ex. user@gapps.exchangedomain.com) and sync the free busy of 
gcal user to this contact. But exchange users would have to add this contact's 
email address to lookup the free busy of gcal user.
Whats your scenario, could you please explain this ?

Original comment by jaideepg...@gmail.com on 27 Jan 2012 at 12:51

[GoogleCodeExporter]

You've pretty much described our scenario in your response.  We have the same 
domain on both the google and exchange sides and the user does exist in both 
systems.  We have a domain alias in google apps that we are forwarding exchange 
mail to for our pilot users using an exchange contact.  We can see exchange 
free busy information in gmail, albeit without details. 
If I understand what you are saying we can sync free busy info to the exchange 
contact but the only way to look that info up on the exchange side is to use 
the google alias, the contact info instead of the user info.  This makes the 
pilot a little more difficult.  What if we were to detach the mailbox for the 
pilot users on the exchange side?  The only major concern is that we are trying 
to maintain dual delivery in case the pilot is unsuccessful and we have to move 
back to exchange, we don't want to lose any mail. 
Thanks

Original comment by RichTheT...@gmail.com on 27 Jan 2012 at 8:35

[GoogleCodeExporter]

Apologies.  The comment above is from me, I just wasn't paying attention to 
what account I was signed into.
Thanks

Original comment by rbertr...@pima.edu on 31 Jan 2012 at 11:06

[GoogleCodeExporter]

In above case you can not sync the free to the Exchange mailbox because GCC 
writes the free busy to public folder. So if any other Exchange user looks up 
the free busy of this user, it would return the free busy based on the 
appointments present in the mailbox instead of the free busy written in the 
public folder. Also you can not create a contact with the same email address as 
of the user mailbox. So you would have to create contact with different email 
address and other Exchange users would have to use this address to lookup the 
free busy. If you remove the mailbox for the user then you can change the email 
address of the contact to the same as it was for the user mailbox.

Original comment by jaideepg...@gmail.com on 1 Feb 2012 at 6:14