HQ and remote site - how to configure exchange 1

[scriggs]

I am looking to setup a fairly permanent connection between two sites. The sites will be connected over a VPN.

We use Exchange at HQ and want access from the remote site:
- can I access exchange over VPN or do I need to setup Exchange on the remote server?
- is there a benefit to setting up a front end server for the remote site?

Any advice welcome.

 

[sharper]

Alot depends on the available bandwidth on the VPN. If you're using aDSL with small uplinks I wouldn't advise using Outlook clients connecting to the HQ Exchange server over the VPN. A second exchange server works well but your domain should be extended to the remote site too (put a DC in the remote site and setup AD sites and services with the IP range of the remote site and all that). Your users in the remote site will have their mailboxes stored there so access will be quick, mail between sites will be a bit slow but won't impact on users experience.
If you have a small number of users in the remote site you could deliver their mailbox using OWA over the VPN straight to the Exchange Mailbox server - this is a nice cheap solution if your users are happy with OWA.
Use a front-end server if you have a lot of users in both remote and HQ sites. You could then use RPC over HTTPS and Exchange Cached mode on the PCs in the remote site - Your users will have a local copy of their mailbox and will be able to collect mail from any internet connection.

Hope this helps

S.

 

[scriggs]

Thanks for the quick reply.

We have a HQ with 20 users, connected to the internet by 2MB leased line (2mb u/l and 2mb d/l).

The remote site has 4 users, connected to the internet by 2MB SDSL line (2mb u/l and 2mb d/l).

So a fairly quick connection, do you think Exchange would be OK over VPN? Else I will look at exchange both ends, but have never configured more than 1 site.

 

[sharper]

Putting Exchange in the remote site for 4 users is not cost effective - it's alot of hardware and work (all the extra AntiVirus and Backups and all that). It will be easy to try straight Outlook to Exchange over the VPN - this won't cost you anything and may well work with your links. Putting the Outlook clients in Exchange Cached mode should result in a better user experience. If your users can't stand it let them use OWA to your Exchange in HQ and then if they hate that... then you might go for a remote exchange server.

Installing a remote exchange server is not much different than installing you first Exchange - except that you chose the option to join an existing org. You will need to setup routing groups but they are easy in Exch2003.

Try this

http://www.microsoft.com/technet/pr...367-4032-47be-b334-bf3fed9ea539.mspx?mfr=true

and read the whole doc if you can't sleep at night....

 

[scriggs]

Cheers for the advice, soooo useful.

 

[Zelandakh]

Use Outlook 2003 in cached mode using RPC over HTTPs without a VPN. Then they can surf without tying the line and the security is easier.

 

[twwabw]

We have a client w/Exch at HQ, and remote office w/9 users connected via VPN. We have a DC at the remote site, and all users connect to Exch with no issues. All clients running Outlook 2003 in cached mode, and remote site is commercial cable connection, 2Mb/512 link, w/HQ having 1.5/1.5 connection. Everything works great- been running this way for almost 2 years. My only adivce would be to have a quality VPN (read: not Windows). We use Sonicwalls at both sites, and the tunnel works flawlessly.