Exchange 2003 RUS co-existance with 2010

Hi Experts,

A 3rd party has installed an Exchange 2010 server, in an organization that only had Exchange 2003 servers in it until recently.

If I create new users and place them on the Exchange 2003 clusters, the users don't appear to pick up recipient policies from the Exchange RUS anymore? Is that correct?

On another note with RUS, if there are no filtering rules for a policy, should that particular policy always be matched and associated address stamped on any new recipients?

If there is a match at priority 1, do all other policies stop getting processed for that user and it moves onto the next object?
LVL 15
MarkMichaelAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
RUS should still be stamping the user accounts, unless they have done something they shouldn't have done with the email address policy on Exchange 2010.

If a user matches all policies, then they will all be applied. The priority controls which address is made the default.

So if a user only matches a policy with priority 2, then that policy settings apply.
However if a user matches a policy with priority 2 and 1, then the policy of number 1 applies in any conflict.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alan CoxSr. Systems Engineer | Lead Microsoft CIE Qualified FacilitatorCommented:
As long as they didn't home RUS to the exchange 2010. To decommission 2003, this is a needed step (or remove via adsiedit.msc). so check to make sure the RUS is still pointing to the 2003 server.
0
MarkMichaelAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.