Good day to all, and thank you for any advice you might be able to give on this question!
I have a situation where we have SBS2008 hosting our e-mail, using the domain of (say) A.COM. We have A.COM externally hosted, and are using the SBS POP3 connector to receive mail, and this is working well.
The company has merged with other businesses, and now we need to change the main domain of the e-mail to B.COM, and at the same time, all users need to change their email address format from (assuming their name was John Smith) email@example.com to firstname.lastname@example.org.
The email for B.COM will also be externally hosted, and we can use POP3 Connector to get e-mail for this too. This aspect of how the email for B.COM is hosted and using the POP3 Connector cannot be changed, it is mandated by agreement of all offices involved in the merge.
The email for B.COM will now be shared among all offices, so this location's Exchange must be able to send mail to folks outside of this location using the B.COM e-mail addresses belonging to other offices.
The company have several mobile users using Outlook Anywhere which we have connected successfully and have a third party certificate for A.COM, and several users have phones synchronised to Exchange also using A.COM. This location will retain full rights to continue to use A.COM so this method of connection/certificate etc. can easily be maintained if needed.
Now that I hope I have explained background and requirements well enough (any questions please ask!), here is what I would like to know:
In order to achieve all these things, what is the best way of going about doing this? I have looked through much documentation already, and in fact, whilst I'm loathe to influence anyone's thinking, my idea was to simply create a new accepted domain on the Exchange server for B.COM, then manually enter everyone's new address via the Exchange Console, setting that new e-mail address as their primary. Then build the appropriate POP3 connectors to download the mail and bring it into Exchange.
I felt that by doing it this way - and "internally" for remote/phone/Outlook Anywhere connections, still using the email@example.com address would keep things as simple as possible.
Then I wondered - could it really be just that simple? I'd appreciate thoughts and advice on this - unfortunately, I don't have the chance to test these things first, and as it's a production environment that's quite crucial, I need to get it right from the get-go.
Many thanks in advance for any assistance folks may be able to offer!