Re: 2nd Branch Office
- From: "Kenneth A. Weade" <kweade@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Apr 2005 14:54:03 -0700
What are the bandwith requirments for the DC Solution? I am in the same boat
with one of my clients. Remote office users are connecting to corp server
via VPN but working on file is SLOW SLOW SLOW. I have Business class 1.5 up
and down at corp and 1 up and down at remote site. Would a copy of the share
files be cached localy and the the changes replicated at night? How does
this work?
"SuperGumby [SBS MVP]" wrote:
> This is a fair call and I know a couple of smart people who do it this way.
> Need to offer an alternative though.
>
> Having a second DC at the remote site can also work, with either it or a
> hardware device establishing a VPN into the SBS. The 2nd DC must be plain
> W2k3, not SBS.
>
> There is also a way to run two seperate AD's, therefore two seperate SBS's,
> two seperate Exchanges, everything seperate as far as the sites are
> concerned, but operating as the same internet domain.
>
> <tmccull2@xxxxxxxxxxx> wrote in message
> news:1105395431.682455.25300@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >I suggest a separate Terminal Server in the main office in application
> > sharing mode. This would be accessible through RWW. Have the branch
> > offce users connect to the T/S for their regular apps including office
> > plus the accounts system.
> >
> > No need for a VPN in the branch office.
> >
> > Benefits:
> >
> > Centralized admin
> > Reduced security vulnerability (only 1 port is open)
> > Increased performance of apps
> > Easier to back up if everything is in the main office.
> >
>
>
>
.
- Follow-Ups:
- Re: 2nd Branch Office
- From: Kenneth A. Weade
- Re: 2nd Branch Office
- Prev by Date: Re: Web Security Certificate Keeps Popping Up
- Next by Date: Re: RDT on LAN takes 15 min to close
- Previous by thread: Is Action Pack an option for a client?
- Next by thread: Re: 2nd Branch Office
- Index(es):
Relevant Pages
|
