I know this is easy, but I can't wrap my head around it. Please point me to some resources. SBS2008 Network with one Server 2008 R2 member. Exchange Server 2007 up-to-date. 2 mailbox stores (default install). We accept mail for one domain name, forwarded from public DNS. I have an internal domain, this will remain the same. My Exchange domain is changing from @solacehealthcare.org to something like @wellness.org. I need to do this for 50 mailboxes. I cant interrupt the flow of mail. I cant use PST files to copy all the old mail to new. I need to get the new domain running and run them side by side for a week while users notify contacts of the change. I need to then forward incoming mail to the new addresses. I need to move the old mail into the new mailboxes. I then wish to delete the old mail store. I would love it if all of my transport rules, forwarders, access, delivery restrictions, anti-spam, and retention remained in effect and applied to the new mail domain. Perfect situation: I add new mail domain @wellness.org. For one week I forware @solacehealthcare.org to @wellness.org I merge both domains and keep @wellness.org, which will make @solacehealthcare.org non-existant. Users keep contacts, rules, calendars, old mail, etc. All email prefix's remain the same (First.Last).Christopher Dill Network Engineer | Solace Healthcare Group, Inc. SBS 2008 | Exchange 2007 | WSS 3.0

Why the need for new mailbox store? This is as simple as just adding the new domain to Accepted Domains, then setting up an email address policy. No need to do anything about forwarding etc. Once you are happy that all email addresses are correct, make the new domain the default. Although if you think you will be able to drop the old domain after a week, you are very much mistaken. I wouldn't even consider dropping it for at least six months, preferably longer, unless it is being forced from you (ie someone else is taking the domain by legal means). Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thank you for your quick response. That is just what I was looking for, a simple solution, which was slightly outside of knowledgebase. It is not being forced from us, we switched company names and Solace is no longer legally ours, though that matter little in terms of email- which is purely a cosmetic move. Thank you very much!Christopher Dill Network Engineer | Solace Healthcare Group, Inc. SBS 2008 | Exchange 2007 | WSS 3.0