Re: exchange recipient policy

• Previous message: Anil: "Re: Outlook Access from Remote Site"
• In reply to: paulh: "Re: exchange recipient policy"
• Messages sorted by: [ date ] [ thread ]

Date: Fri, 27 Aug 2004 21:35:07 -0400
To:  joe@joeware.net

The answer is that the RUS doesn't work that way. It doesn't do an LDAP query
against AD, it either goes through all objects (for initial stamping) or it
looks at objects with specific changed attributes. Then it applies the query
logic to that object and if it matches, it does what it needs to do. Again, this
isn't done by OU based on how they designed it.

And an OU isn't an attribute of the object, it is simply the parent that the
object resides in. Something that has worked for other companies I have spoken
with is to make an addition to AD of a special attribute specifically for
specifying what policy group you want to be in. Doesn't matter what it is
called, what matters is what is populated in it and you set the recip policies
up to key on it. This way if you use Dept or something and later decide that you
want to use dept for something else or get more granular with your dept settings
you don't have to worry about your recip policies going to hell on you.

Once you have an attribute and specific values set up and configured in the
recipient policies, you can set up a script that checks all users in a given OU
to see if they have that value and attribute set for them, if they don't, the
script sets in and bam on the next RUS pass, the recip policy updates that user
object.

I think one day unless MS fixes this I am just going to set up a service to
handle this because it is getting to be a pretty popular request.

   joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
paulh wrote:
> So OU is not an AD attribute?  So in this case, I need to go into each user 
> account and add the Department name in their profile?  Just curious since I 
> have a quite a few to do and do not want to do it again.  Why does the 
> recipient policy give you OU option on the filter?  (no need to answer that, 
> just a frustrating thing)
> Thanks
> Paul
> 
> "Mark Fugatt [MVP]" wrote:
> 
> 
>>You cannot create a Recipient Policy based on the OU, you will have to use 
>>one of the other AD attributes, i.e. Department, Company etc
>>
>>-- 
>>Mark Fugatt
>>"paulh" <paulh@discussions.microsoft.com> wrote in message 
>>news:EB8BAEB5-4732-4EA2-9F6A-2E1137A90DD0@microsoft.com...
>>
>>>We have recently separated a division of our company who wants their own
>>>established domain.  jdoe@xyz.com where the parent company is widgets.com.
>>>Users currently have a widgets.com address, in this case jdoe@widgets.com
>>>
>>>We have every division of the company in their own OU including this 
>>>group.
>>>I would like to generate the new domain specific email addresses (xyz.com)
>>>for this group based upon their OU.  So what I thought we could do is 
>>>create
>>>a recipient policy in exchange 2000 that would generate the new smtp
>>>addresses only to those people in the OU via a filter.
>>>So if you belong to new OU, you @xyz.com smtp address.  This doesn't seem 
>>>to
>>>work, any ideas?  I really do not want to create 100 email addresses. 
>>
>>
>>

• Previous message: Anil: "Re: Outlook Access from Remote Site"
• In reply to: paulh: "Re: exchange recipient policy"
• Messages sorted by: [ date ] [ thread ]