Hello,

we want to create a number of Mail-Enabled Contacts. Now, when creating them with provtest and then open the Contact in EMC, EMC allways displays a message, that there is invalid data. What i found out is, that EMC expects the Target/External Address to be also specified in the Proxy Addresses.

Okay, this can lead to trouble in Hosted Exchange, since i can have a Proxy Address only once in AD.

Anyway, is there a way to provision the Contact in a way, that EMC doesn't display errors?

Or is there no need for this? Mail-Enabled Contacts seem to work, allthough EMC displays Errors. But why are they displayed then? It would be a horror if we had to find out, that our contacts don't work reliable.

Thanks for your help

Filipp
 

It is all depend on what do you want: working contacts or nice looking EMC.

Couple things, that are "disaster" from EMC point of view, are just Ok for Exchange itself. It you will add "Target/External Address" to Proxy address list, then you can't create another contact with the same e-mail address, or even more, if this e-mail address belongs to existing mailbox in environment, you can't create contact at all. So, the way how HMC 4.0 deals with contacts is a workaround (see Managed Email 2007 namespace source):

    <!--
    ***************************************************************************    
      Delegate work to Exchange 2007 Provider
      
        Note that we are passing primarySmtpAddress as the externalEmailAddress
        this to work around Exchange 2007 constraint that externalEmailAddress
        must be unique when set through exchange cmd-let interface
    ***************************************************************************    
    -->
    <execute namespace="Exchange 2007 Provider" procedure="MailEnableContact" impersonate="2">
      <before source="procedureData" sourcePath="path" destination="executeData" />
      <before source="procedureData" sourcePath="primarySmtpAddress" destination="executeData" />
      <before source="procedureData" sourcePath="preferredDomainController" destination="executeData" />
      <before source="procedureData" sourcePath="primarySmtpAddress" destination="executeData" destinationPath="externalEmailAddress" mode="merge" />
      <before source="procedureData" sourcePath="emailAddressPolicyEnabled" destination="executeData" ifNull="ignore"/>
      <before source="procedureData" sourcePath="owningOrganization" destination="executeData" ifNull="ignore"/>
    </execute>
    <!--
    ***************************************************************************    
      Use Active Directory Provider to reset the targetAddress - A.K.A
      externalEmailAddress to the desired value
    ***************************************************************************    
    -->
    <execute namespace="Preferred DC Active Directory Provider" 
             procedure="Set Properties" impersonate="1">
      <executeData>
        <properties>
          <property name="targetAddress"/>
        </properties>
      </executeData>
      <before source="procedureData" sourcePath="path" destination="executeData" />
      <before source="procedureData" sourcePath="preferredDomainController" destination="executeData" />
      <before source="procedureData" sourcePath="externalEmailAddress" 
              destination="executeData" destinationPath="properties/property" mode="merge"/>

    </execute>

filippg:

But why are they displayed then?

it is a question for Exchange team... Looks like a bad design decision: to much attention to PowerShell frills then to Exchange itself.

Hi,

DmitriG:

It is all depend on what do you want: working contacts or nice looking EMC.

Guess what. I want nice looking, working contacts ;-)

But when they're working, I'm allready satisified. So, i will just use the MPS MailEnableContact-Method.

Thanks for your Answer!

Filipp

Hi,

I created the contacts now (using Hosted AD:CreateContact and Hosted Email 2007:MailEnableContact).

But every user got a proxy-address in the form cn@hostingdomain added, where hostingdomain is the AD-Domain Name in which HMC was setup, not a valid SMTP-Domain. Is this normal Behaviour? Since the CN is created out of First- and Lastname I can't create a contact for the same person in two Customer-Orgs (only if i change the pattern for CN-Creation).

Bye

Filipp
 

filippg:

I created the contacts now (using Hosted AD:CreateContact and Hosted Email 2007:MailEnableContact).

It will be nice if you will post your XML requests.

Hi,

so this doesn't seem to be normal...

The XML-Code is:

<request>

Are you creating contact in OU=Hosting,DC=hosting,DC=net?

Yes, since hosting it's part of the Domain name (of course, this is only an example-Name). Let's name your Domain contoso.com, then I'm creating the contacts in

LDAP://OU=myBuisOrg,OU=myHostingOrg,OU=Hosting,DC=contoso,DC=com.

The created Addresses then would be:

Thanks

Filipp

ok. I got impression from you previous post that you are trying to create contact in "OU=Hosting,DC=contoso,DC=com".

To deal with your situation you can remove smtp:myCN@contoso.com from the list of contact's proxy addresses after MailEnableContact.

Or you can create contact with CN=myCN@myBuisOrg and then use this as the internal e-mail. One condition for this - myBuisOrg must be valid SMTP domain name in your Exchange org. In this case, MailEnableContact will not create smtp:myCN@contoso.com proxy address.

 Hi,

 thank you for your reply - took some time till i could test it.

Unfortunately the second method didn't work like expected - it created a Proxyaddress wit myCN?myBuisOrg@contoso.com (so, replacing the @ in the CN with a ? and appending contoso.com). myBuisOrg is a valid SMTP-Address of the BuisOrg.

At least, the primary SMTP-Addresses of the contacts will now be unique accross the Orgs, since myBuisOrg is part of the Address.

Thanks

 
Filipp