<div>
Sounds good, thanks for the info.
</div>


<div>
<div class="content wysiwyg-content">
We are extending our domain to a data center that will house Exchange. &nbsp;Our initial design is to create a VPN and have THREE servers total. &nbsp;Server1 will be a domain controller and global catalog server, Server2 will be an Exchange front-end box with GFI MailEssentials, and Server3 will be an Exchange back-end server. &nbsp;We will NAT a public IP to the front-end server for HTTP, HTTPS, SMTP, RPC over HTTP, etc...<br />
<br />
One random thought I had was the possibility of installing the front-end server(Server2) as a virtual server on Server1 to save hardware costs. &nbsp;Plus, since it is on the front lines, we can save an image as a backup and reload it quickly if an issue arises. &nbsp;I look forward to your insight...
</div>
</div>


We are extending our domain to a data center that will house Exchange.  Our initial design is to create a VPN and have THREE servers total.  Server1 will be a domain controller and global catalog server, Server2 will be an Exchange front-end box with GFI MailEssentials, and Server3 will be an Exchange back-end server.  We will NAT a public IP to the front-end server for HTTP, HTTPS, SMTP, RPC over HTTP, etc...

One random thought I had was the possibility of installing the front-end server(Server2) as a virtual server on Server1 to save hardware costs.  Plus, since it is on the front lines, we can save an image as a backup and reload it quickly if an issue arises.  I look forward to your insight...

Exchange install scenarios at data center

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.