Networking Forums

Networking Forums > Computer Networking > Windows Networking > New office accessing Windows Server/apps at old location?

Reply
Thread Tools Display Modes

New office accessing Windows Server/apps at old location?

 
 
Jeff
Guest
Posts: n/a

 
      09-10-2009, 01:28 PM
Hello,

Our firm currently has a Windows 2003 domain setup (two domain controllers)
and a MS Exchange 2003 server.

We will be opening another location about 20 miles away.

What is the best method the new location can connect to our existing
location and access files/resources?

Our phone company says a point to point T-1 line. Will this be enough
bandwidth?

Do I need to install a new server or Exchange server at this new location? I
would like these users to be on the same mail system.

Any info would be appreciated

Jeff
 
Reply With Quote
 
 
 
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      09-10-2009, 01:40 PM
Hello Jeff,

As a starting point:
http://www.microsoft.com/downloads/d...displaylang=en

With deploying a branch office 1MBit line should be ok. You don;t have the
need for an own exchange server, they can use the server in the main site.

For data it depends on the amount and also if they must have the data accessable
always, then you should think about a DFS solution where multiple servers
replicate the data automatically.

Also you have to think about an additional DC with DNS and GC enabled in
the site, also not a must, but without this they can only logon locally to
the computers if the connection is dropped for whatever reason.

With server 2008/2008R2 you have additional options:
http://technet.microsoft.com/en-us/l...44(WS.10).aspx

http://technet.microsoft.com/en-us/l...55(WS.10).aspx

http://technet.microsoft.com/en-us/n.../dd425028.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello,
>
> Our firm currently has a Windows 2003 domain setup (two domain
> controllers) and a MS Exchange 2003 server.
>
> We will be opening another location about 20 miles away.
>
> What is the best method the new location can connect to our existing
> location and access files/resources?
>
> Our phone company says a point to point T-1 line. Will this be enough
> bandwidth?
>
> Do I need to install a new server or Exchange server at this new
> location? I would like these users to be on the same mail system.
>
> Any info would be appreciated
>
> Jeff
>



 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      09-10-2009, 10:38 PM
Jeff <(E-Mail Removed)> wrote:
> Hello,
>
> Our firm currently has a Windows 2003 domain setup (two domain
> controllers) and a MS Exchange 2003 server.
>
> We will be opening another location about 20 miles away.
>
> What is the best method the new location can connect to our existing
> location and access files/resources?
>
> Our phone company says a point to point T-1 line. Will this be enough
> bandwidth?
>
> Do I need to install a new server or Exchange server at this new
> location? I would like these users to be on the same mail system.
>
> Any info would be appreciated
>
> Jeff


I would suggest a Terminal Services box in the main office - thin clients
(or full ones if you wish) at the new location - a T1 to the Internet and
VPN to your office through a hardware VPN solution.

Bandwidth and data storage become pretty much of a non-issue at that point.


 
Reply With Quote
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      09-13-2009, 03:22 AM
Bill Kearney <(E-Mail Removed)> wrote:
>> I would suggest a Terminal Services box in the main office - thin
>> clients (or full ones if you wish) at the new location - a T1 to the
>> Internet and VPN to your office through a hardware VPN solution.
>>
>> Bandwidth and data storage become pretty much of a non-issue at that
>> point.

>
> Not a bad idea but you have to factor in how many users will be
> running active sessions and what they need to do. That and you get
> into real trouble dealing with people being unable to do their work
> if the terminal server or it's link goes down.


Redundant internet connections become a big deal here.

> You don't want to
> grind work to a halt because the link died. Backhoes happen.


LOL - yes they do.

>
> How many users will be at the new remote location? What are their
> computer requirements?
>
> -Bill Kearney




 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Best way to connect remote windows 2003 server to main office Ryan Windows Networking 4 12-10-2007 03:17 PM
WTB: WINDOWS XP PRO, WIN2K PRO, HOME, 98SE, 98, 95, NT 4.0, OFFICE, SERVER Mike Windows Networking 0 01-28-2007 04:27 PM
Machintosh accessing Windows Server 2003 Rubens Luque Sanches Jr. Windows Networking 1 09-19-2006 05:17 PM
Accessing Shares on a Windows 2003 Server =?Utf-8?B?TWFyaw==?= Windows Networking 6 03-08-2005 07:06 PM
Accessing Mac Shares on a Windows Server =?Utf-8?B?Q3lwaGVy?= Windows Networking 0 12-15-2004 09:27 PM



1 2 3 4 5 6 7 8 9 10 11