 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Design / March 2006Two diffeent Forest sharing 1 Exchange Server
Here one that going to get your folks thinking. I am part of a company (abc.com), we recently purchase another company (123.com) although we have establish a trust between the 2 forest. I am face with an issue and want to know what is the best way to design the 2003 Exchange domain. Since we ABC.com own 123.com I would like to setup 1 Exchange Server to host both domains. The issue is that we like to keep emails address separate and the outbound email (header) to stay the same, so if someone from 123.com sends an email out the header has to say from 123.com and the same rule apply for abc.com. I have consider setting up a separate forest and setting up a forest to forest trust on both ends. But would that resolve the problem? Secondly both companies would like to share calendar info. I would also like to setup users on their domain and they also could setup users on our domain. I consider using Associated External Account to manage the users or MIIS 2003. But would either one satisfied my requirements. I told you this would be a tricky one. TIA any input is welcome I don't think this is too tricky. The hardest part is figuring out what makes sense to your business after this one merger. If you want to host a single Exchange 2003 org in your forest, you could either put it in ABC.com or put it in 123.com or you could be tricky and put it in a new forest called NewForest.com if that makes more sense. You can put all of the users in the same forest if you want or you could have two Exchange orgs if you wanted (in that case, why not one org in 123.com and one in abc.com). If I understand your requirement correctly, you want all email to look as if it were sent from 123.com but your system should receive for 123.com as well as ABC.com. You also want to share administration of the system. Is that correct? If so, put the ORG in ABC.COM forest, and create the users using the associated exernal right for 123.com users. Be sure to understand the trade-offs of this design so you can properly set expecations. I suggest reading up on the resource forest scenario to understand it better. As for email, you can specify that all users have a ABC.COM mail address as their primary. You can additionally add a secondary address type of 123.COM to all the users that need it or all of them, whichever is easier. Change your external mail flow to use this server as your inbound route, and you won't miss a message. Does that solve your problem? > Here one that going to get your folks thinking. I am part of a company > (abc.com), we recently purchase another company (123.com) although we have [quoted text clipped - 17 lines] > would > be a tricky one. TIA any input is welcome Al Thank you for reply, the issues is that both 123.com and ABC.com has to remain separate. Although there is a forest trust between both organizations. We would like to keep users from 123.com to be able to send out emails and when they do send out such emails to have 123.com in the header. The same would go for ABC.com, the header has to also say that it came from ABC.com. So as for the requirement go Users from123.com has to have 123.com in the header Users from abc.com has to have abc.com in the header Must have to share resources from both ABC.com and 123.com such as calendar. Must be able to administrator domain for each any domain. As far as setting up a separate forest I how can I setup current users already on AD on either 123.com or ABC.com since we have AD accounts setup. What steps would I take for setting up existing users, do I consider ADMT v2.0 . There is not plans in the near future the merge these domains together. I have consider setting up a separate forest but I also have consider setting up a cluster server one at 123.com and the other in ABC.com. Then run VMWare Server on each of these server and setting up an Exchange Server for 123.com and one for ABC.com? The bad point of that is I am relying on software to keep the exchange running which I don't care too much about. Let me know what are you thoughs. Thanks again. >I don't think this is too tricky. The hardest part is figuring out what >makes sense to your business after this one merger. [quoted text clipped - 42 lines] >> would >> be a tricky one. TIA any input is welcome I would look into the Galy Sync and inter org connector option. The other option you have is to host ABC.com on the current Exchange server and take over the namescpace and own both ABC.com and 123.com and have disabled accounts for 123.com user objects where the 123.com AD account has permissions to open the mailbox > Al > Thank you for reply, the issues is that both 123.com and ABC.com has to [quoted text clipped - 69 lines] >>> would >>> be a tricky one. TIA any input is welcome |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.