I wanted to try out the new version of Exchange and Server 2008 R2, so I downloaded and installed the Server 2008 R2 Enterprise Evaluation VHD (on my Hyper-V Server R2 machine), and installed Exchange 2010 RC. Now, this problem could very well be limited to the RC, as I have not had a chance to test this on RTM, but I ran into a bit of a problem when trying to edit the default E-mail Address Policy. I added an external domain name to the Accepted Domains and set it to Default, but when I tried to edit my Default EAP (via the Exchange Management Console) to include this new domain, I got the following:
The operation can’t be performed on the default e-mail address policy.
Exchange Management Shell command attempted:
set-EmailAddressPolicy -ConditionalDepartment @() -ConditionalCompany @() -ConditionalStateOrProvince @() -ConditionalCustomAttribute1 @() -ConditionalCustomAttribute2 @() -ConditionalCustomAttribute3 @() -ConditionalCustomAttribute4 @() -ConditionalCustomAttribute5 @() -ConditionalCustomAttribute6 @() -ConditionalCustomAttribute7 @() -ConditionalCustomAttribute8 @() -ConditionalCustomAttribute9 @() -ConditionalCustomAttribute10 @() -ConditionalCustomAttribute11 @() -ConditionalCustomAttribute12 @() -ConditionalCustomAttribute13 @() -ConditionalCustomAttribute14 @() -ConditionalCustomAttribute15 @() -RecipientContainer $null -EnabledEmailAddressTemplates ‘X400:c=US;a= ;p=MailOrg;o=Exchange;’,’SMTP:%email@example.com’,’smtp:@exchtest.local’-Name ‘Default Policy’ -Identity ‘Default Policy’
I found a few posts out there on the InterWebs about this same problem, but everyone’s solution was to just create a new EAP. My solution (after a lot of trial and error) was to copy the above command to the Exchange Management Shell and remove the -Name property. Without this, my command ran fine, so it begs the question: If the -Name property of the set-EmailAddressPolicy cmdlet causes an error, why is it auto-generated from the Exchange Management Console?