Implementing Exchange 2003 server at remote site

[Paul318]

Hi
I will be implementing an Exchange 2003 server at a remote site, the remote site currently has no server. I am building the server at the main site, then it will be shipped to the remote site, there are only 2 users there that will need to connect to get their mail. The server is not a Domain Controller, so I can't put it in a different site in Sites and Services.
The main objective or implementing a server at the remote site is that there Outlook currently goes over the WAN to connect to their mailboxes.
The main site holds the 2003 DC's and MS recommends you don't install Exc on a DC, and there is a budget for only 1 server.
I'm not sure if this will cause issues with regards to, slow mailbox access (since it has to go over the WAN to authenticate. Can anyone see any issues with the setup?

 

[skialta]

Be prepared for everyone to question why you'd install an exchange server for 2 people. You're much better off upgrading the bandwidth or something else.

 

[ntinlin]

Why is Outlook going over the WAN a problem when you can use Outlook 2003 cached mode?

An exchange server will cost you a lot of money in budget and administration time that could be better spent.

Your WAN bandwidth will not decrease because you don't have a local Global Catalog server so any time Exchange needs to do anything it is going to have to connect to your primary site anyway.

If WAN bandwidth is an issue you'd be better spending the money on a better connection.

Neill

 

[Paul318]

Unfortunately this isn't an option, they are currently on a Satellite broadband link due to the location being so remote.

 

[markdmac]

I would say you are hosed up no matter what. Satellite connections are OK for web surfing but terrible for any kind of real time communication as the connections constantly drop. Your Exchange server WILL stop working constantly as it will loose connectivity with the Global Catalog.

Your other option is to first load this server as a DC/GC then install Exchange on it.

I would recommend you abandon using Exchange on this new server. Just make it a DC for your users so they can authenticate locally. Then configure their Outlook for Outlook over HTTP.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[Paul318]

Thanks Neill
That is my concern, that it is not entirely going to overcome the lag problem.
They are using Outlook in Cached mode, but when they send an email it locks their PC's up. If an Exchange server is there, that will do all the work of sending/rec from the main office. But like you say, it will have to refer to the GC server before doing so, but hopefully, this will be quicker (due to less going through the pipe) and be seamless to the end user?

 

[markdmac]

Paul, I think our posts crossed. Refer to mine above yours. The info stroe is going to stop on you all the time. I am speaking from experience with Satellite connections. They are not sufficient for this application.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[58sniper]

I'm with Mark. You're not going to be happy with an Exchange server in that office.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)