When you create a contact through the EMC, by default it inherits the Default Policy in the "E-mail Address Policies". So far the only way I have found around this are:Create the contact through the EMC, and then open it after its created, uncheck the "Automatically update e-mail addresses based on e-mail address policy" setting, and remove the secondary email address from the Org it was created in.Use the EMS and add the value -PrimarySmtpAddress which turns the afore mentioned setting from the start.The issue is neither scenario is intuitive to an Administrator, and therefor we have ended up with quite a few contacts that have gotten our organization's email addresses on them w/o us meaning for that to happen.My question is if there is a way to modify the command the EMC is executing behind the scenes to include the -PrimarySmtpAddress value, or if there is a way to do something to the recipient policies to prevent them from being associated with the contacts. I.E. Is there a way to make the default such that a contact would not get the "Automatically update e-mail addresses based on e-mail address policy" value set to True?I have searched everywhere for this question and tried several word combinations, but so far I have found no way to make the EMC stop associated all new contacts with the 2007 e-mail address policies (and why you want want this as the default for all contacts which are generally outside of your organization is beyond me).Thanks!

Hi,I think its very simple by using Templates in exch 2007.e.g choose one of your contact as template, and set its attributes according to ur need, and then use it in PS command like this: $template =get-mailcontact jerrynew-mailContact -name thomas1 -externalemailAddress thomas1@yahoo.com -template $t Now if jerry had EmailAddressPolicyEnabled as false (disabled) then so will thomas1 have this property disabled.Hope this help.Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

Hi,Plz have more details regarding Templates here: How to Use Templates to Create Recipients TemplatesRegards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

I noted that using the -PrimarySmtpAddress value in the Exchange Management Shell avoids the issue, so I don't need a template. Thanks for the recommendation though.My issue is regarding creating contacts in the Exchange Management Console, and how to force them to not have this setting set automatically. I.E. The EMS can do it, I just need to figure out if there is somethign that can be changed in the EMC.

Hi,For this issue, you can try the following steps:1. Use the Exchange Management Shell to disable the application of the E-mail Address Policy to all existing contacts, as follows:Get-MailContact | Set-MailContact -EmailAddressPolicyEnabled:$false2. Use ADModify http://www.codeplex.com/admodify/Release/ProjectReleases.aspx?ReleaseId=6065 to remove the existing e-mail addresses from your contacts.3. Create a new dump Accepted Domain that doesn’t actually exist, something like “AllContacts." The point being that this is a domain you would never actually want to send mail to.4. Create a new E-mail Address Policy and choose to apply it only to “Contacts with external e-mail addresses."5. Add the Accepted Domain that we created in step 3 to this E-mail Address Policy.Steps 1-2 will take care of your existing contacts, while steps 3-5 will prevent any new contacts from being stamped by the Default Policy.If you need to edit the Default Email Address Policy and create a new to replace it, you can refer to the below thread:http://social.technet.microsoft.com/Forums/en/exchange2010/thread/9f34c97f-7112-4355-8166-771babd1a437ThanksAllen

So it doesn't sound like there is a way to modify the default behavior of the EMC, but rather we have to rely on tricking it into creating the contacts with an email address to a ficticious domain. That's a real shame. Does anyone know if this is an issue with Exchange 2010?

As a follow up to my own question on Exchange 2010, apparently this issue can be coded around using Extension Agents and telling them to automatically disable the EmailAddressPolicy and to remove any company email addresses: http://www.lucas-keller.com/?p=11 At least that is what we are hoping and we are going to test because it would sure save a lot of headaches.

The approach of using an Extension Agent did not scale well in a large enviornment with multiple DCs. First the script has to be replicated to every Exchange server that might execute the cmdlet, otherwise you get errors. Also the DC the Extension Agent uses could be totally different than the one the cmdlet used, so you will get hit or miss on the Extention Agent working properly in this context. So right now it looks like the EMS or nothing.

You could schedule a script to run frequently, looking for objects out of compliance and fixing them. This could run once an hour or whatever interval you like. Mike Crowley | MVP My Blog -- Planet Technologies

We do have a script that does just that, and we run it occasionally, it would just be nice to not have Exchange do something dumb in the first place. :-)

Templates have been requested by Exchange admin's for years and years. Microsoft has decided not to mess with them. But this is why they provide you with 2 interfaces. I don't believe there is any obligation to make all features available in both tools. We all need to step up and learn new things sometimes. All exchange admins need to learn powershell. Mike Crowley | MVP My Blog -- Planet Technologies