Announcement

Collapse
No announcement yet.

Recipient Policy Hell

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Recipient Policy Hell

    Hi,

    I have been admin of a 2K3 Enterprise Exchange server for quite some time, as is the case with most small businesses I had to make it up as I went along which is fine to a point, I stress I have had no formal training in Exchange.

    We were recently taken over by a group of small companies and the decision was made to utilise our messaging infrastructure groupwide.

    This need to be done fast and dirty so I just did the external DNS updates required and setup the new mail domains in the default recipient policy.

    I now have time to clean this all up and give each company it's own recipient policy using this tutorial as a basis for the cleanup exercise.

    I have split out 4 new recipient policies to cover the different business units and have configured filters to act on the correct LDAP Distinguished Name for the Group that users are a member of.

    It is all configured as the tutorial advises however when I apply the policies the only one that seems to be applying is the default one which now only has one domain in it and which also has lowest priority but sits at the top of the list if that is any indicator of a problem.

    Any help troubleshooting this very much appreciated.

    GD

  • #2
    Re: Recipient Policy Hell

    have you checked that your ldap filter is working correctly ?
    there should be a button that will enable you to see which objects the address will be applied to.

    Otherwise: as annoying as it might be, considering using custom-attributes, and using that to filter on.. IE if customattrib1 is company1, then use policy1
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Recipient Policy Hell

      Just discovered this in the server log

      Event Type: Error
      Event Source: MSExchangeAL
      Event Category: Address List Synchronization
      Event ID: 8325
      Date: 4/22/2010
      Time: 9:43:32 AM
      User: N/A
      Computer: SERVER
      Description:
      The service can't work properly because the Policy 'POLICY DISTINGUISHED NAME' has an invalid Filter Rule (purportedSearch). Use the Exchange System Management tool to correct this problem. While this error exist new users, contacts and groups won't receive mail information necessary to them to work properly.
      For more information, click http://www.microsoft.com/contentredirect.asp.

      Gaaaaaaaaah!!!!!!!!

      I used the same sodding filter as in the tutorial

      GD

      Comment


      • #4
        Re: Recipient Policy Hell

        just try a different filter
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment


        • #5
          Re: Recipient Policy Hell

          Originally posted by tehcamel View Post
          just try a different filter

          foudn this http://forums.petri.com/showthread.php?t=22829



          Now working as it should be YAY!!!!

          Comment


          • #6
            Re: Recipient Policy Hell

            congrats buddy thanks for letting us know what the solution was
            Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

            Comment

            Working...
            X