Here's an interesting one that I can't figure out. I was about to call MS, but figured I'd check here first.
Two Exchange 2010 forests federated with GAL Sync.
User Bob@domain.com had a mailbox on Exchange 2010 server.
Bob now has a new mailbox on a different Exchange forest (Bob@Awesome.com).
Bob wants his old email forwarded for Bob@domain.com to Bob@Awesome.com.
So...easy enough right? Create a contact in the domain.com Exchange server and set the forwarding on the mailbox and for grins hide the mailbox from the address books. Done, right?
Wrong (sort of)...because (note: I have federation and GAL sync allowing free/busy across forests):
Bob is getting auto-forwarded meeting requests from Sally@domain.com who used the Scheduling assistant and typed in "email@example.com" and saw that he's available. He gets the calendar forward and says "Um...Sally...I'm booked at that time" to which she replies "not from what I see".
Now if Bob is available on firstname.lastname@example.org and he accepts, it shows up on his awesome.com calendar as it should. But Sally sees the request still sent to Bob@domain.com in the scheduling assistant as he is free but email@example.com is coming to the meeting.
SO...basically users in the domain.com organization can still see free/busy details on the old calendar for the mailbox firstname.lastname@example.org even though the mailbox is hidden from the GAL.
Since I can't create a contact and then forward that contact....is there any way around the above? I don't think I can remove a calendar from a mailbox. I considered removing all calendar permissions but wasn't sure if that was the right path to go down or not.
OR even better: Can someone tell me how to accept email for email@example.com on Exchange without having a mailbox for him and then re-route it to firstname.lastname@example.org?
UPDATE: I have figured out how to handle the calendar with removing the default permissions...it's an ok fix. The BOUNTY will be for the "OR EVEN BETTER" question in bold. If it isn't possible, then that doesn't count as BOUNTY worthy. :) Thank you!