1. Use a DC at each location
2. Use/Create the AD "Sites" Object in AD that represents each location.
3. Associate each DC to the proper AD Site that corresponds to the physical
location it is in.
4. The AD Site Object is what controls and maintains the "replication" that
has to occur over the slow WAN links.
When this is done properly there probably is no need to upgrade the Internet
Service unless you just want to get rid of some extra money.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html
Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------
"Gene B." <(E-Mail Removed)> wrote in message
news

-KdnfH1D7fx6iDeRVn-(E-Mail Removed)...
> If a company has a DC at the main location running
> Windows 2003 Server Standard with DNS, WINS, DHCP, and Exchange 2003 and
> wants to put a BDC with Exchange at the remote location. Would anyone
> suggest
> upgrading their Internet service?
>
> Both locations have cable modems for theirs internet access
> Bandwidth test results are listed below.
>
> Main Office
> Your download speed : 1234 kbps or 154.3 KB/sec.
> Your upload speed : 685 kbps or 85.6 KB/sec.
>
> Remote Office.
> Your download speed : 1284 kbps or 160.5 KB/sec.
> Your upload speed : 581 kbps or 72.7 KB/sec.
>
> Main Office has 15 Users. Remote office will have 10.
>
> Thanks
>
>
>