本文发表在 rolia.net 枫下论坛As I understand, you don't have to keep domain "aaa.com". In another words, you will use ccc.com login identity instead of aaa.com. (Just assuming, there are 140 new employee)
and
Domain "aaa.com" exist just as email domain.
If I'm right, what I'll do :
1, Backup exchange at ccc.com
2, Using Exmerge utility retrives all mailboxes at aaa.com
3, Creating new users at ccc.com
4, Loading mailboxes to ccc.com, using Exmerge.
5, Mapping mailbox to user
6, Config exchange at ccc.com receiving aaa.com email
7, Point aaa.com MX record to new exchange server
The pfmigrate utility can be used in moving public folders to the new servers. (But I haven't use this utility in my production env.)
This is a very straightforward method to merge exchange server as I know. I am sure you can find others doing the same job. No matter what method you will use, always make a backup and test it in your testing envirement before touching your prodution.
If you find any other better way to do it, please share it with us.更多精彩文章及讨论,请光临枫下论坛 rolia.net
and
Domain "aaa.com" exist just as email domain.
If I'm right, what I'll do :
1, Backup exchange at ccc.com
2, Using Exmerge utility retrives all mailboxes at aaa.com
3, Creating new users at ccc.com
4, Loading mailboxes to ccc.com, using Exmerge.
5, Mapping mailbox to user
6, Config exchange at ccc.com receiving aaa.com email
7, Point aaa.com MX record to new exchange server
The pfmigrate utility can be used in moving public folders to the new servers. (But I haven't use this utility in my production env.)
This is a very straightforward method to merge exchange server as I know. I am sure you can find others doing the same job. No matter what method you will use, always make a backup and test it in your testing envirement before touching your prodution.
If you find any other better way to do it, please share it with us.更多精彩文章及讨论,请光临枫下论坛 rolia.net