Improve company productivity with a Business Account.Sign Up

x
?
Solved

RUS and Mailbox Management policies when migrating to Exchange 2007

Posted on 2009-04-12
1
Medium Priority
?
340 Views
Last Modified: 2012-05-06
Hi All,

We are currently running Exchange 2003 SP2. We have four domains in our Active Directory - Florida, California, NY and Texas. Exchange is organized so that each domain is also a routing group/ Admin group in Exch. NY is the hub site which mails go to the Internet from/to.

FL will be migrated to Exchange 2007 first. The problem is, we have recipient update policies and mailbox management policies set for the entire 2003 organisation (although each domain has a seperate RUS server).

We have installed the FL CAS and Hub Transport server so far. From what I can see, the existing RUS policy has been copied over as an E-mail Address policy, but the 'Applied' status is False. The Mailbox Management policy from 2003 does not seem to have been copied over - although I'm not sure if this is because we don't have a 2007 Mailbox server as yet in the org.

Does anyone know what will happen to the Mailbox Management policy (delete Inbox emails after 70 days etc) when we co-exist? Will the 2003 policy be applied to any mailboxes on 2007? Is there the chance that a 2007 policy will affect mailboxes on 2003?

Secondly, is it possible to set Mailbox Management policies for only a subset of users (e.g. one domain) in the EMC?

And, thirdly, what will happen to the RUS/E-mail Address policy?

Thanks!
0
Comment
Question by:Joe_Budden
1 Comment
 
LVL 9

Accepted Solution

by:
Alan Cox earned 2000 total points
ID: 24127058
I believe the policies will have to be re-created. I've not done a transition where policies were involved. I do know that yes, you can setup policies based on domain or almost any schema attribute. The address policy will carry over to Exchange 2007. It doesn't use RUS but rather email address policies and accepted domains. To remove exchange 2003, you need to point your 2003 RUS to the 07 server (MS is supposed to fix this), even though it doesn't use it.
Hope that helps.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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.

Join & Write a Comment

In an Exchange Crossforest migration, the distribution groups can be a very complex operation that would cause loss of time, lots of issues and continued headaches if not solved in a timely manner. I had to do a similar project so I created a sc…
In a Cross Forest, the steps to migrate users are quite complicated and even in the official articles of Technet there is no clear recommendation on which approach to take .. From an experience, I mention and simplify which way to go and how to use …
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

589 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question