Exchange 2010 Best Practice in remote office
Hello. We have two offices. Each office has its own domain. We currently have a two way trust between the offices.
In the large office we run Exchange 2010. In the small office I want to install Exchange as well. What is the best way to do this. We have a strong connection between the two offices. Should I just create the 10 additional users in the large office domain and use outlook anywhere to connect them? Or should I install their own Exchange server for the small office? The issue is that they are two separate domains.
Thank you
In the large office we run Exchange 2010. In the small office I want to install Exchange as well. What is the best way to do this. We have a strong connection between the two offices. Should I just create the 10 additional users in the large office domain and use outlook anywhere to connect them? Or should I install their own Exchange server for the small office? The issue is that they are two separate domains.
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Amit
Apart from Will advise above, you can also create linked mailbox
You can host your other domain (add the second office's domain to the trusted domains list of the main office's exchange server).
Is there some element you arent explaining? From a cost perspective it is so cost prohibitive to setup a complete working exchange system that 10 users essentially means take the total cost (hardware and software) divide it by 10 and thats how much money it will cost per user. Even if you had 100 users...1000 users at the second location it would still make sense to add their domain to the main office's exchange server. Now what you could do is add redundancy to your main office's Exchange system (assuming you havent already), meaning implement a DAG for the back end mailboxes, add more than one CA server and add some edge servers. Load balance SMTP to the edge transport servers as well as HTTP/HTTPS to the CA servers.
Personally I use BIGIP LTMs and an irule on the HTTP/HTTPS virtual servers looking at the headers and split off the traffic that isnt OWA traffic to a different pool which serves up actual HTTP/HTTPS traffic.
Its a lot of work but far more effective of a solution.
Is there some element you arent explaining? From a cost perspective it is so cost prohibitive to setup a complete working exchange system that 10 users essentially means take the total cost (hardware and software) divide it by 10 and thats how much money it will cost per user. Even if you had 100 users...1000 users at the second location it would still make sense to add their domain to the main office's exchange server. Now what you could do is add redundancy to your main office's Exchange system (assuming you havent already), meaning implement a DAG for the back end mailboxes, add more than one CA server and add some edge servers. Load balance SMTP to the edge transport servers as well as HTTP/HTTPS to the CA servers.
Personally I use BIGIP LTMs and an irule on the HTTP/HTTPS virtual servers looking at the headers and split off the traffic that isnt OWA traffic to a different pool which serves up actual HTTP/HTTPS traffic.
Its a lot of work but far more effective of a solution.