I'll offer that I've noticed in situations where I've upgraded from
Exchange 5.5 to 2000 or 2003 the recipient policies that are
automatically created in the process use a filter rules format something
like this:
(&(mailNickname=*)(legacyExchangeDN=/O=OrgName/OU=SiteName/*))

Where OrgName is your Exchange Organization name and
Where SiteName is your Exchange Administrative Group Name (which is
linked to the Exchange 5.5 site being upgraded)

Both being the actual names, which may or may not match their
corresponding display names.

As far as I can tell using this filter rules format would exactly fit
your request to scope policies to specific AGs.


Jim Collins
Sr. Systems Engineer
Competitive Computing, Inc.
www.competitive.com
 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Larry
Wahlers
Sent: Thursday, June 30, 2005 10:34 AM
To: Exchange Discussions
Subject: Recipient Policies questions

Hello colleagues,

In Exchange 2003, I have created a separate Recipient Policy for each of
our organizations, and each organization is on its own Exchange server
in its own Administrative Group so they can admin their own stuff. The
recipient policies have addresses like [EMAIL PROTECTED] so we can
automagically get our [EMAIL PROTECTED] addresses created.

I have two questions. The first one is important; the second one is just
odd:

1. Can a particular Recipient Policy be applied to one Administrative
Group and not another? So, could I have the LHM Recipient Policy apply
to the LHM Administrative Group, or even to their particular Exchange
server, and not to others? And the STL Recipient Policy apply to the STL
Administrative Group and not to the LHM Administrative Group?

2. When I created the LHM Recipient Policy, it came up in the list with
a priority of 1 instead of a priority of Highest. Why is that? The only
two things different about it are:
1. It is the only server in its Administrative Group, and it's 2003,
whereas the other Administrative Groups have a 2003 and a 5.5 server in
them.
2. It's in a different domain in the forest from the other Exchange
servers - but there's a 2-way trust.

Thanks, all. You continue to be the greatest!

-- 
Larry Wahlers
Concordia Technologies
The Lutheran Church - Missouri Synod 

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to