Registered users    
MembershipMembership:
Latest New UserLatest:Ron Ang
New TodayNew Today:9
New YesterdayNew Yesterday:6
User CountOverall:23401

Private messaging    
You must be logged in to use this module.
Top 10 posters    
NamePosts
Mariette Knap12949
Marina Roos12626
Eriq Neale2117
Stan Guinn1917
Michael Patrick1914
Robert Pearman1784
Nick Pieters1425
william warren634
Stewart Brown620
Kevin D.579
Welcome unauthorized visitor    
If you want to join us in the discussions on this forum you need to register first. Registration is free! If you are already a registered user please login to join the forum.
Small Business Server Support Forum    
Subject: Branch Office Setup
Prev Next
You are not authorized to post a reply.

Author Messages
Jonathan Edwards User is Offline
United Kingdom
Member since
8/31/2006

Platinum Membership
Posts: 113

8/26/2008 09:01 AM  
Hi,
We are opening a new office for one of our clients.
 
At the moment, we have one office with 7 users running a SBS 2003 Std. We use Exchange/SMTP to email.
 
The plan was to connect the office by two VPN boxes.
 
The new office is to hold 5 users.
 
We aren't going to be installing an additional server at the branch office. File storage/access is going to be local.
 
A couple of questions with this..
1) Is it best to add the remote PC's to the domain?
2) If we do, will logon be quite slow?
 
Thanks
Jonathan
Mick Malloy User is Offline
Australia
Member since
4/6/2007

Microsoft MVP
Posts: 309

8/26/2008 01:10 PM  
the login process itself is an insignificant amount of traffic but things such as Profile or Document redirection can cause significant delay. The default SBSLogin script will also transfer the SBS setup.exe across the VPN, it ain't big but it also ain't tiny.

A bigger problem concerning remote offices with no local server share is transfer of 'working data' across the VPN, dbl-clk a reasonable sized flat file database and you can go get coffee before it opens (only bosses seem to think this is bad :-), but more importantly any interruption to the VPN is _likely_ to corrupt the database. A Word doc with a couple of images in it, an Excel spreadsheet with graphs, decent size PDFs are all similarly afflicted at least as far as the data transfer is considered.

The better solution is to implement a TS at HQ. People from the remote office can either directly access the TS or through RWW (your choice, I would use RWW). This means any data transfer between the calling app and the file happens at HQ network speed, it is only screen updates that go across the link.

TS is not however a 'panacea', it does not solve all your problems because there are considerations about apps either working or 'being supported' in a TS environment.

There are though 'management advantages' to operation via TS. Consistent application version by various users and such unexpected things as 'OK, I don't need a hulking great PC as a workstation in order to run Vista+Office, I can use either a thin client or very basic PC to establish the TS session then my experience is same whether I am in the office, at home, or on holidays'. 5 very basic PCs with no software installed, other than OS, would allow your remote office to connect to RWW then TS.
Jonathan Edwards User is Offline
United Kingdom
Member since
8/31/2006

Platinum Membership
Posts: 113

8/26/2008 01:30 PM  
I think that's why we have opted to keep the storage of files local for now.

We've been asked how much dedicated bandwidth we require.

How much would be sufficent for this connection?

Obviously the more we get, the more it costs!
Mick Malloy User is Offline
Australia
Member since
4/6/2007

Microsoft MVP
Posts: 309

8/26/2008 01:37 PM  
for older TS it's about 24K per TS Session (upload from TS, download to client). This increased when they made TS 32(or is it 15/16) bit graphics, rather than the old 8bit, but if you're doing word processing or using most apps you can limit the connection demands.
You are not authorized to post a reply.



ActiveForums 3.7
Forum policy    
These Discussion Forums are dedicated to the discussion of the Small Business Server and related server and client software. For the benefit of the community please observe the following posting guidelines:
  1. No Advertising. This includes promotion of commercial products and non-commercial products which are not directly related to Small Business Server and related server and client software.
  2. No Flaming or Trolling.
  3. No Profanity, Racism, or Prejudice.
  4. Site Moderators have the final word on approving/removing a thread or post or comment.