Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Cannot modify default email address policy even after upgrading it

Proposed Answer Cannot modify default email address policy even after upgrading it

  • Friday, March 02, 2012 2:04 PM
     
     
    Sign In to Vote
    0

    Cannot modify default email address policy even after upgrading it. Neither conditions tab nor recipient types can be configured, greyed out.

    Set-EmailAddressPolicy "default policy" –IncludedRecipients AllRecipients

    Anand_N

     

All Replies

  • Friday, March 02, 2012 2:19 PM
     
     
    Sign In to Vote
    0

    Have you tried?

         Set-EmailAddressPolicy "default policy" –IncludedRecipients AllRecipients -forceupgrade

    You may also have an address list that is corrupt and is causing you an issue with a corrupt address list.

    JAUCG


    • Edited by JAUCG Friday, March 02, 2012 2:27 PM
    •  
     
  • Friday, March 02, 2012 2:22 PM
     
     
    Sign In to Vote
    0

    When i run that it says the operation cannot be performed. assuming maybe because it has already been upgraded

    Anand_N

     
  • Friday, March 02, 2012 3:50 PM
     
     
    Sign In to Vote
    0
    How many email address lists do you have?  I had a client who had about a dozen of them and I was not able to create a new Public Folder Store on the Exchange 2010 installation without removing some old address lists.

    JAUCG

     
  • Friday, March 02, 2012 4:05 PM
     
     
    Sign In to Vote
    0
    only just the default policy

    Anand_N

     
  • Friday, March 02, 2012 4:24 PM
     
     
    Sign In to Vote
    0
    Have any of your public folders been moved over per this article? http://technet.microsoft.com/en-us/library/gg576862.aspx

    JAUCG

     
  • Friday, March 02, 2012 5:40 PM
     
     
    Sign In to Vote
    0

    What does public folders have to do with email address policy?

    Anand_N

     
  • Friday, March 02, 2012 7:04 PM
     
     
    Sign In to Vote
    0

    Public folders, especially for Exchange 2003, is where Outlook get OAB information.  Usually the step you are attempting is done after all users are moved and all Public Folders are migrated.  If you still have your Exchange 2003 server you can modify things from there or if you want to use Exchange 2007, make sure all your Public Folder data is moved according to that link I attached.

    For a more detailed look at the Address List migration, refer to the Microsoft Exchange Team blog post - http://blogs.technet.com/b/exchange/archive/2007/01/11/3397719.aspx

    JAUCG

     
  • Friday, March 02, 2012 7:44 PM
     
     
    Sign In to Vote
    0
    what is the difference in pf replication vs pf move?

    Anand_N


    • Edited by Anand_N Friday, March 02, 2012 7:44 PM
    •  
     
  • Friday, March 02, 2012 10:07 PM
     
     
    Sign In to Vote
    0

    PF replication is when there are multiple PF databases on different Exchange servers regardless of Exchange version.  So you can have a copy on each Exchange 2003 server and one on each Exchange 2007 server.  This is done for availability of certain properties contained in the folders (OAB, Free Busy and Org Forms).

    PF move is when you are migrating to a new server version for Exchange.  This essentially moves the root of the folders from the old Exchange version to the new Exchange version.  This would be done after replication is successful for PF.

    JAUCG

     
  • Thursday, March 15, 2012 8:59 AM
     
     
    Sign In to Vote
    0
    I ran the MoveAllReplicas.ps1 script, however I still cannot edit the default email address policy afterward. so it did not work. I fail to see what moving pf replicas has to do with email address policy.

    Anand_N

     
  • Monday, March 19, 2012 10:09 AM
    Moderator
     
     
    Sign In to Vote
    1
     

    Hi Anand_N,

    Please run the following cmdlet and post the result here.

    Get-EmailAddressPolicy | Format-List Name,*RecipientFilter*,ExchangeVersion

    The following similar issue modify value of msExchPolicyOrder via ADSIEDIT for your reference.

    Default Policy not applying :<//span>

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/14c4d6a7-42a6-4c72-b84e-3eddd1654f3c

    Wendy Liu

    TechNet Community Support


     
  • Thursday, June 07, 2012 8:12 PM
     
     Proposed Answer
    Sign In to Vote
    1

    I ran into this issue and neither ESM nor PowerShell helped me.  What did it was opening ADSI Edit on one of the Domain Controllers and digging to:

    //Configuration//Services//Microsoft Exchange//MY-DOMAIN//Recipient Policies

    I then right-clicked on the Recipient Policy I wanted to delete (Default Policy) and selected "Delete".  Went back to EMS and refreshed the policies and voila! it was gone.

    I did create a new policy before I deleted the old one, but this has no effect in the solution.

    I hope this helps someone else.

    • Proposed As Answer by ceez38 Thursday, June 07, 2012 8:12 PM
    •