Re: SBS with Branch Office

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for your reply, Larry.

I had already planned to use Outlook over HTTP for performance reasons. And
I know that the VPN performance will be poor with only a 1.5M T1. Our VPN
device does allow for connection bonding, so we'll be adding another cable
connection to improve the performance. Saying that, the TS option in the
main office is still our ultimate plan, but we just needed to get the office
up for a few users initially.

Ken

"Larry Struckmeyer" wrote:

Hi Shepcon:

Questions you did not ask, but may wish you had:

Since you are planning on purchasing a second Windows Server, I might
consider putting it in the main office as a Terminal Server and using RWW
for the remote office. Or, without hitting the RWW page, since the hardware
will create/maintain the tunnel, you will have one click RDP to the Terminal
Server.

In this way, no data ever leaves the main office, and your applications are
not dependent upon the connection. If it goes down, no data is corrupted,
you just pick up the session again when the connection comes back up.

Lastly, you might use "Outlook Anywhere", or Outlook over HTTP, which allows
remote Outlook users to connect to the Exchange Server in the same way as
local users.

For Exchange 2003
http://technet.microsoft.com/en-us/library/aa996922(EXCHG.80).aspx

For Exchange 2007
http://technet.microsoft.com/en-us/library/bb123741(EXCHG.80).aspx

--
Larry

Please post the resolution to
your issue so that all can benefit.




"shepcon" <shepcon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8DB98677-BF48-4634-BA0B-9CE8A14EE7D9@xxxxxxxxxxxxxxxx
Thanks for your reply, Cris.

I am running ISA 2004 on my SBS Premium server at my home office. My
branch
office will only have Windows 2003 Standard.

The remote office will be using my SBS Exchange server through Outlook,
SQL
databases on SBS using client/PC based applications and also data on my
NAS
device that is connected to my SBS server in the home office. For this
reason, I thought that the remote office should have the same IP
structure.
If the remote office is on a different subnet, what would you suggest and
how
does SBS know about this different subnet. Also, whould the remote server
use this different subnet as well?

Thanks.

Ken

"Cris Hanna [SBS-MVP]" wrote:

I think some clarification is needed

Your main office is running SBS Premium with ISA?
And the remote office will run Win2k3 Std?

No your remote office should be on a completely different subnet from the
SBS network, or users will not be able to browse

Are you expecting any users at the remote office to run applications that
are on the Main SBS Server?

--
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"shepcon" <shepcon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:442E0E8E-4225-422A-89BC-F14AB2B96B3F@xxxxxxxxxxxxxxxx
I'm running SBS 2003 Premium w/SP1 (not R2) and all is running well.
We're
in the process of setting-up a remote/branch office. We'll be using a
hardware VPN/firewall appliance at both ends by a company called Fiber
Logic.
The Fiber Logic 2120 device that's at our home office is outside of
our SBS
ISA2004 in somewhat of a DMZ. Our SBS server does have twin NICs with
the
standard 192.168.16.* internal subnet and the external NIC has a
valid/legal
IP.

My question is how do I correctly pass the VPN connection from my home
office VPN device into my internal SBS subnet through ISA2004? Also,
should
my branch office use the same 192.168.16.* subnet for those PCs? I do
plan
to setup a branch office BDC running Windows 2003 Server to help
improve
performance so that all of the authentication occurs locally to the
branch
office users. I'm guessing that the branch office server should use
192.168.16.3 and have DNS installed as well.

Thanks for any suggestions



.

Relevant Pages

  • RE: Update Outlook
    ... Thank you for posting in the SBS newsgroup. ... 2003 Server, an administrative installation of Outlook 2003 is installed at ... In addition, please don't install Outlook ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP
    ... So you're trying to migrate from an existing SBS 2003 to a new one? ... If you're just trying to move the mailboxes to a new server, ... have the users configure outlook to go through the http first. ... Outlook only uses RPC on slow connections. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS with Branch Office
    ... it will be less costly and more efficient to do the TS server from the get go. ... Cris Hanna [SBS - MVP] ... connection to improve the performance. ... >> The remote office will be using my SBS Exchange server through Outlook, ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing Outlook onto SBS2008 Server
    ... Jeff's kit for SBS 2008 is out. ... Cris Hanna [SBS - MVP] ... Windows Small Business Server 2008 Unleashed ... Have used Outlook 2003 on hundreds of SBS2003 servers ever since it came out without a single issue anywhere. ...
    (microsoft.public.windows.server.sbs)
  • Re: Application Publishing Server and Exchange
    ... through an Applications Publishing Server which uses Terminal ... And the mail will be stored in Exchange, also on SBS. ... I do not plan to install Outlook 2003 on each client, ... Worldwide customers can use the Guide to Worldwide Microsoft ...
    (microsoft.public.windows.server.sbs)