How to setup a recipient policy using group membership

My goal is to setup a recipient policy (mailbox mgr) to delete emails from certain accts based on group membership - However when creating the filter, filtering group memebership never works - I can get filter and recipient policy to work using OU and single users - AD is structured in a way where I dont want to move accts to a spefiic OU and I dont want to create multiple policies to achieve (1) goal -

Can someone please inform me the correct steps to achieve this goal

I read something about "memberof" was not an attribute and is only discovered "on the fly" when queired which if true would be a reason but there has to be a way -



SHAXAsked:
Who is Participating?
 
Michael B. SmithConnect With a Mentor Exchange & Active Directory ExpertCommented:
As the KB says:

[1]  set your Recipient Update Service for the active directory to point to a group catalog server.

[2] build a recipient policy from the Advanced tab and specify the full distinguishedName of the group

[3] each time you update the group rebuild the recipient policy.

That's really it.
0
 
Michael B. SmithExchange & Active Directory ExpertCommented:
This issue, the problems, and solutions are discussed here: http://support.microsoft.com/kb/304516

This is a feature of Exchange 2007/2010, by the way. It's easy to do there.
0
 
sunnyc7Commented:
ok - what version of exchange are you using ?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
SHAXAuthor Commented:
Exchange 2003
0
 
SHAXAuthor Commented:
Yes, Michael B - that is the same link I referenced in my original post - It appears the only way to have this work is to query the GC - I am not sure how to query GC - Any help is greatly appreciated -
0
 
Michael B. SmithExchange & Active Directory ExpertCommented:
Sorry, your original post must be a different question. Your question above doesn't reference the KB article I listed.

I think the KB article is very clear. If you are going to use a group in your filter, then every time that the group membership changes, you must force a rebuild of that Recipient Policy.

I suspect you may be misinterpreting the statement "you must query against a group catalog". It doesn't alter my statement above. The "you must query against a group catalog" means that the server hosting the Recipient Update Service for a particular Active Directory domain must be a GC server. And, of course, if you only have a single Active Directory domain in your forest (like 99%+ of the world), then it doesn't matter whether you query a regular DC or a GC.
0
 
SHAXAuthor Commented:
I think we are saying the same thing - but your right i did not list the KB but was referring to the same article when I spoke of "memberof was not an attribute and is only discovered "on the fly" when queried" in orginal post -

At this point I'll need to research on how one goes about querying the GC in order to achieve goal -
0
 
Michael B. SmithExchange & Active Directory ExpertCommented:
As I said above: The "you must query against a group catalog" means that the server hosting the Recipient Update Service for a particular Active Directory domain must be a GC server.
0
 
SHAXAuthor Commented:
can you offer any help where to find help on how I can query against the group??
0
 
SHAXAuthor Commented:
Thank you Michael b smith

Question 1 - recipient update services are already in place pointed to a group catalog server (our PDC), if I rebuild, do I rebuild both and does a rebuild cause issues if done during business hours?

Question 2 - attached is a screenshot of the recipient policy using the advanced tab, my question is how or what is easiest way to write an ldap query to show members of the security group users are apart? -

Sorry for the confusion
Ldap.doc
0
 
SHAXAuthor Commented:
I got the ldap query to work w/ nested OU's but even after altering the group it does appear a rebuild of the recipient policy is needed - although running the query returns new members, the report generated from the system attendant does not reflect the newest memebers mailbox - I even ran "update now" on the recipient update service w/ no luck -

I am somewhat hesitant about "rebuilding" the RUS not knowing which of the (2) to run or what the implications are when doing this like exchange performance, etc
0
 
SHAXAuthor Commented:
i have recipient policy set to update constantly - a litte slow but avoids the rebuld -
0
 
SHAXAuthor Commented:
rebuild is not necessary and found ldap query myself -
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.