We currently have 1 Exchange 2003 server at HQ for ~60 users. Management has decided to open a remote office and move 12 users off to remote location. The location will be linked T1 using ipsec VPN betweeen HQ and Remote using ASA 5505's. I plan on setting up a DC at remote location. The remote users will need access to shared public folders. Should I setup a Exchange 2003 server at the remote location for 12 users? Or should I just have traffic go through VPN back to HQ SMTP? Will this cause a bottleneck? Any sugesstions on how to best configure this setup? Dave Santel

What is the bandwidth like? Saying it is a T1 doesn't really mean a great deal. For 12 users I would be looking at using RPC over HTTPS back to the main Exchange server. That will avoid having to licence another server (which would have to be an Exchange 2010 licence downgraded), plus backups, AV etc etc. Although if the cash is there for a second office server, I would use it to upgrade your main office to Exchange 2010, and get off the out of support version of Exchange. That will still allow you to use RPC over HTTPS (called Outlook Anywhere in the later versions of Exchange), but the configuration is fully automated rather than a manual configuration in Outlook. It would also give you access to the enhaced OWA as a fall back. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

It will be a MPLS 1.5 MB T1. 10 voip phones will be riding off this MPLS circuit as well but no heavy phone usage.Dave Santel

My answer still stands - I wouldn't think of putting an additional Exchange 2003 server in that location - although I wouldn't deploy Exchange 2003 now full stop. Sharing with voice though can be interesting and it doesn't always work as people expect. Therefore you might want to consider starting off on the same server and then looking at alternatives, such as using a second server, or simply putting a second standard internet connection in and bring the traffic for Outlook across that, leaving the MPLS line for telephony traffic and other network content that doesn't go across HTTPS like RPC over HTTPS to Exchange. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hello, I also recommend to use Outlook Anywhere for these users. Thanks, Simon