Hello,

I migrate our infrastructure from an AD2008 Forest & Exchange2010 Organization to a new AD2012 forest & Exchange2013 organization.

For user continuity purpose, I would share freebusy and GAL sync over the 2 infrastructure during the migration.

For GAL sync, FIM2010 well works.

For freebusy, I configure freebusy according to : https://technet.microsoft.com/en-us/library/bb125182(v=exchg.15).aspx

this works well when 2 different namespaces are used, the problem come when I want to use the same on each parts.

I couldn't add an availabilityaddressspace for it:

[PS] C:\>Add-AvailabilityAddressSpace -ForestName smtpdomain.com -AccessMethod PerUserFB -UseServiceAccount $true -domainController "dc01.olddomain.local"
Received a referral to olddomain.local when requesting CN=OLDDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=olddomain,DC=com from dc01.newdomain.local.  You have specified the wrong server for this operation.
    + CategoryInfo          : NotSpecified: (0:Int32) [Add-AvailabilityAddressSpace], ADReferralException
    + FullyQualifiedErrorId : 2D8BFC3,Microsoft.Exchange.Management.SystemConfigurationTasks.AddAvailabilityAddressSpace

smtpdomain.com is declared as internal relay on each oranization.

I don't found any solution on google or Bing (just one post with no more answer

https://social.technet.microsoft.com/Forums/en-US/7f50c5e0-924e-4bd9-9993-660f5214de8d/free-busy-and-shared-smtp-namespace?forum=exchange2010

I don't know if it's a bug or a impossible configuration.

Someone ever see this ?

Thanks, BR

Is the forest name the same as the SMTP domain? I wouldn't think that olddomain.local would be your SMTP domain, and that looks like what your forest domain should be based on the FQDN you've specified for t

Hi Ed,

Thanks for your reply,

Old forest name is : olddomain.local

New forest name is : newdomain.local

Main SMTP domain is : smtpdomain.com

(there is a mistake on the DN : CN=OLDDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=SMTPdomain,DC=com)

Sb

I believe the only way you're going to make this work is to have two new SMTP domains, say smtpold.com and smtpnew.com, assign the new addresses to the users (you can keep the old addresses) and create contacts in each organization pointing to the new SMTP domain of the other.

I thank to this solution, but the problem is the impact to external contact's address book.

If we define smtpold.com and smtpnew.com, these will be used for external email too.

Perhaps, rewriting address could resolve this impact.

I'm looking on antispam side, or Edge side with "New-AddressRewriteEntry" cmdlet.

What do you think about it ?

Thanks,

The problem is that Autodiscover is going to point to the old or the new, not both.  It's the e-mail address that's used for cross-forest free-busy resolution.

My suggestion won't mess up the address book, it's only a proxy address.  The primary SMTP address can still be the common address.

But you still will have to create MX records for the new SMTP do

I don't think Autodiscover is an important problem. It will going to point to the new domain. It's just for a 1 or 2 weeks migration.

But I'm not sure to understand very well

FreeBusy use the primary address to resolve a MBX location, ok ?

About mail flow, if I declare smtpold.com and smtpnew.com as primary address on contacts, when a smtpOldUser send an e-mail to a smtpNewUser, with a copy to an external contact, the address book of the external contact will be mess up with smtpnew or smtpold address, not ?

That's why I hope that rewriting could help me ... :)

Thanks,

If it's not important, then why worry about it?