Hi,1. Upgraded Default EAP (ExchangeVersion: 0.1 (8.0.535.0))2. Added extra accepted domain3. Edit Default EAP and add second domain fails:Edit Default PolicyFailed Error: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:@demo.lan','smtp:%m@demo.nl' -Name 'Default Policy' -Identity 'Default Policy'No problem creating a new EAP.Any ideas?Martijn

Hi,Please run the cmdlt with -verbose and then post the output here. Upgrade the Default E-Mail Address Policy from LDAP Filters to OPATH Filtershttp://technet.microsoft.com/en-us/library/dd351283.aspx Please note in Exchange 2010, you can't use custom extension attributes as a filterable property. If your organization has custom extension attributes, we recommend that you use the 15 custom attributes provided by Exchange 2010 for each recipient. However, if the custom attributes don't meet the needs of your organization, we recommend that you don't upgrade objects that use custom extension attributes.Regards,Xiu<!---->

Hi,With -verbose parameter:VERBOSE: [12:15:24.819 GMT] Set-EmailAddressPolicy : Initializing Active Directory server settings for the remoteWindows PowerShell session.VERBOSE: [12:15:24.819 GMT] Set-EmailAddressPolicy : Active Directory session settings for 'Set-EmailAddressPolicy'are: View Entire Forest: 'False', Default Scope: 'demo.lan', Configuration Domain Controller: 'DC01.demo.lan',Preferred Global Catalog: 'DC01.demo.lan', Preferred Domain Controllers: '{ DC01.demo.lan }'VERBOSE: [12:15:24.850 GMT] Set-EmailAddressPolicy : Runspace context: Executing user:demo.lan/DEMO/Admins/beheer.martijn, Executing user organization: , Current organization: , RBAC-enabled: Enabled.VERBOSE: [12:15:24.850 GMT] Set-EmailAddressPolicy : Beginning processing.VERBOSE: [12:15:24.850 GMT] Set-EmailAddressPolicy : Instantiating handler with index 0 for cmdlet extension agent "Rus Agent".VERBOSE: [12:15:24.850 GMT] Set-EmailAddressPolicy : Instantiating handler with index 1 for cmdlet extension agent"Admin Audit Log Agent".VERBOSE: [12:15:24.850 GMT] Set-EmailAddressPolicy : Current ScopeSet is: {Domain Read Scope: {, }, Domain WriteScope(s): {, }, Configuration Scope: {, }, Server Configuration Scope(s): {, }, , Exclusive Scope: {, }}VERBOSE: [12:15:24.850 GMT] Set-EmailAddressPolicy : Searching objects "Default Policy" of type "EmailAddressPolicy"under the root "$null".VERBOSE: [12:15:24.865 GMT] Set-EmailAddressPolicy : Previous operation run on domain controller 'DC01.demo.lan'.The operation can't be performed on the default e-mail address policy. + CategoryInfo : InvalidOperation: (Default Policy:ADObjectId) [Set-EmailAddressPolicy], InvalidOperation Exception + FullyQualifiedErrorId : 78979DD3,Microsoft.Exchange.Management.SystemConfigurationTasks.SetEmailAddressPolicy VERBOSE: [12:15:24.865 GMT] Set-EmailAddressPolicy : Ending processing.

Hi,Please try to use the comdlt to upgrade the defualt email policy.Set-EmailAddressPolicy -Identity "Default Policy" -EnabledEmailAddressTemplates SMTP:@fourthcoffee.com,smtp:@contoso.com.When we run this command,it will add value--SMTP:@fourthcoffee.com;smtp:@contoso.com for gatewayProxy on "Default Policy".Besides, I recommend you to create a new policy and then stamp the smtp address on that policy.Regards,Xiu

I am having the exact same problem, were you ever able to edit the Default EAP? Creating a new EAP seems to work fine, but I get the same error as above when trying to edit the Default EAP from the GUI. I am running a Hyper-V server based on the Server 2008 R2 Enterprise Evaluation VHD, and I installed the Exchange 2010 RC on it. I have had plenty of experience installing and managing Exchange 2000, 2003, and 2007, and as this is a fresh install, I don't understand the problem. Is this just a limit of the RC?...Sr System Engineer

Hi Derek,First please upgrade your exchange server to RTM with the lastest update.Besides, since this thread has been silent for long time, I recommend you to open a new thread thus we can focus on your issue there.Thanks.Regards,Xiu

Although I do realize this is a bit of a stale topic, it wasn't a couple of weeks ago when I posted my comment. Anyway, I did plenty of searching around, and did not find a solution for this problem, although I found a number of people sharing my problem. That's actually how I came to this site. Anyway, at the time I downloaded the VHD, all that was available was the RC, and I was just running this in a test environment so I would be familiar with the problems I might find in a real-world scenario. In the end, my solution (after a lot of trial and error) was to copy the command produced by the Exchange Console 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?Sr System Engineer

It still fails in the console (EMC), but the EMShell command from above works: Set-EmailAddressPolicy -Identity "Default Policy" -EnabledEmailAddressTemplates SMTP:@fourthcoffee.com,smtp:@contoso.com I wonder why it doesn't work in EMC?

Hi, From technet article,it said that: You can't use the EMC to upgrade the default e-mail address policy. (http://technet.microsoft.com/en-us/library/dd335105.aspx) Base on my research, I found that it is by design. We blocked some UI for default policy but without blocking corresponding parameters. Regards, Xiu

I guess my more basic question is Why? Why did Microsoft make Exchange management so much more difficult in 2007 and 2010? A large part of Microsoft's success is Windows which is a GUI. A GUI is easier to use and that is why we don't use DOS anymore. There is no technical reason you could NOT have a 64-bit DOS and everyone could do everything from the command line. The reason that we have GUI's is that they are easier to use. I like having the command line available...I have used scripts of various kinds for years. However, I HATE being FORCED to use the command line or power shell or anything not GUI. I have been a Windows engineer since 1993 and earned my MCSE in 1995. It appears to me that Microsoft doesn't care about small business anymore...you almost have to be a full time Exchange engineer to learn all this stuff about the command line and make it work. So...why did Microsoft decide to move backward in time 20 years and abandon the Windows interface for so many critical functions in Exchange 2007 and 2010? Why not have all functions available in both Exchange Management Shell and Exchange Management Console?

I would really REALLY like to know the why as well. The TechNet article mentioned above had no information on the Default E-mail Address Policy, it dealt with the Default Address Lists. The article I believe you meant to link to is http://technet.microsoft.com/en-us/library/dd351283.aspx, which does indeed talk about how useless the Console is for such a trivial task. The part that really bothers me is that the Console says (and I quote), "Error: The operation can't be performed on the default e-mail address policy." It doesn't say it can't be done via the console, it simply says it can't be done. It took a lot of trial and error before I got it to work in the shell, and I'm with Drew on the whole anti-small business thing. I am an IT consultant, and the majority of our customers are ~20 man shops. Most of them don't even understand what Exchange does, and it seems like Exchange management is only getting more and more complex.Sr System Engineer

Hi, It has been reported to PG, so far we do not get update. Personally, I think it would be a way to aviod anyone who do not know exchange well to do modification on the default email address policy, since the default email address policy may assign to all the users. Regards, Xiu

Wait until you have to mess with certifcates or legacy public folder migration or uninstalling 2007 or 2010.For years Linux 'people' have said that they like Linux being difficult to use/administer/mess with because it means that the average joe won't mess it up. So I guess Microsoft wants us all to drop Windows and go with Linux?Of course not! Microsoft, please, please, please make ALL Exchange management 'stuff' available/doable in the Exchange Management CONSOLE as well as the EMS for Exchange 2007 and 2010 and future versions of Exchange. More than that, give me lots and lots of wizards for Exchange management. I would absolutely love to have a pretty little wizard that would completely automated the setup and configuration of private SSL certificates (small companies will NOT pay for public SSL certs, Microsoft!). Pretty please, with sugar on top, AND a cherry!?!This is all coming from an MCSE with 5 digit MCP number (missed the 4 digit ones by like a month or two...dangit!), who has been supporting all the Microsoft email technologies since the Microsoft Mail MTA ran on Microsoft OS2 (no, not IBM OS2...OS2 was a Microsoft product before it was an IBM product...it was a 32-bit character based OS, sorta like DOS).

I just ran into this problem myself and it looks like the problem is that the Powershell syntax that EMC generates is incorrect. Here's what EMC generated for me: [PS] C:\Windows\system32>set-EmailAddressPolicy -verbose -ConditionalDepartment @() -ConditionalCompany @() -Conditional StateOrProvince @() -ConditionalCustomAttribute1 @() -ConditionalCustomAttribute2 @() -ConditionalCustomAttribute3 @() - ConditionalCustomAttribute4 @() -ConditionalCustomAttribute5 @() -ConditionalCustomAttribute6 @() -ConditionalCustomAttr ibute7 @() -ConditionalCustomAttribute8 @() -ConditionalCustomAttribute9 @() -ConditionalCustomAttribute10 @() -Conditio nalCustomAttribute11 @() -ConditionalCustomAttribute12 @() -ConditionalCustomAttribute13 @() -ConditionalCustomAttribute 14 @() -ConditionalCustomAttribute15 @() -RecipientContainer $null -EnabledEmailAddressTemplates 'SMTP:@example.com','smtp :@example2.com','X400:c=US;a= ;p=Example;o=Exchange;' -Name 'Default Policy' -Identity 'Default Policy' That wasn't working, so I deleted everything up to "-EnabledEmailAddressTemplates" and tried it: [PS] C:\Windows\system32>set-EmailAddressPolicy -verbose -EnabledEmailAddressTemplates 'SMTP:@example.com','smtp:@example2.com' -Name 'Default Policy' -Identity 'Default Policy' This also didn't work. Then I looked at the above example, which just has "-identity" without "-name" and tried that: [PS] C:\Windows\system32>set-EmailAddressPolicy -verbose -EnabledEmailAddressTemplates 'SMTP:@example.com','smtp:@example2.com' -Name 'Default Policy' -Identity 'Default Policy' This did work. So my assumption is that the "-Name" attribute is what causes the error, and EMC includes this attribute in the command it executes, causing the error.