Windows Vista Forums

Seeking suggestions / solutions for SBS situation
  1. #1


    rjskelton Guest

    Seeking suggestions / solutions for SBS situation

    I have a pretty good idea on what path to take, but I would like to see how
    other professionals would handle this situation. The objective is to
    increase remote user’s performance and plan for future growth.

    The problem is the site to site VPN for a remote office isn’t sufficient.
    My overall plan is to use Remote Desktop. Below is the environment and some
    solutions I came up with.

    SBS Server 2003
    Power Edge 1900
    1 Quad Core Xeon E5310 @ 1.60 GHz
    6 GB Ram
    1 Perc 5i with a 250 GB RAID 1 Volume
    1 Adaptec 2045 with 200 GB RAID 10 Volume
    20 SBS Cals
    5 Terminal Server cals

    Services
    Exchange 2003
    File and Print
    Business apps(Access Database, BestCase, PM TABS)
    VPN

    Jacksonville location
    Cable internet
    VOIP
    Server
    18 employees



    Dayton location
    Cable internet
    POTS
    2 employees, planning to expand

    We purchased 5 TS cals and some hardware upgrades because my plan was to
    enable Application mode for the Remote Users. Unfortunately, I forgot this
    isn’t possible on the SBS Server. So I am looking for suggestions.

    Solution A
    Purchase Windows 2003 Standard, the remaining CPU, and upgrade to 8 GB of
    RAM. Then using ESXi, create two virtual servers, one SBS Server and one
    Terminal Server. Sell the remaining hardware.

    Windows Server 2003($600)
    Processor Xeon E5310($300)
    RAM 2GB kit ($400)

    Advantages
    Lower cost
    Low bandwidth requirement
    Expandability via VPN\RDP
    Centralized
    One Physical Server

    Disadvantages
    Internet dependant
    Remote Desktop
    Legacy software


    Solution B
    Purchase SBS 2008, the remaining CPU, and upgrade to 8 GB of RAM. Then using
    ESXi, create two virtual servers, one SBS Server and one Terminal Server.
    Sell the remaining hardware and software.

    Wndows Server 2008 with cals($3500)
    Pocessor Xeon E5310 ($300)
    RAM 2GB kit ($400)

    Advantages
    Low bandwidth requirement
    Expandability via VPN\RDP
    Centralized
    One Physical Server

    Disadvantages
    Higher cost
    Internet dependant
    Remote Desktop

    Solution C
    Purchase a small Windows Server with enough storage to setup DFS to
    replicate data between Jacksonville and Daytona.

    Server with 2003 and 600 GB storage($3000)

    Advantages
    Moderate cost

    Disadvantages
    High bandwidth requirement
    Legacy software
    Two physical servers
    Decentralized
    Limited expandability

    Thanks in advance for any input,

    Raymond


      My System SpecsSystem Spec

  2. #2


    Charlie Russel - MVP Guest

    Re: Seeking suggestions / solutions for SBS situation

    You'll find that option B simply doesn't have enough RAM. SBS 2008 needs a
    _minimum_ of about 6 GB to function well. Depending on your apps, your
    Terminal Server will be OK at 2 GB of RAM only if it's not heavily used at
    all. But in either case, you'd need something for the hypervisor parent. And
    for 23 users, I'd bump it up beyond that, for sure. Say to at least 12 to 16
    GB.

    I wouldn't choose ESXi for virtualiztion, simply because I prefer to put all
    my horses in the same barn and simplify the finger pointing.

    You don't specify what version your TS CALs are. This is a solution that
    cries out for TS RemoteApps, but that will require Server 2k8 or Server 2k8
    R2 TS CALs. (Both can be used interchangeably with either Server 2k8 or R2
    servers)

    --
    Charlie.
    http://msmvps.com/blogs/russel




    "rjskelton" <rjskelton@newsgroup> wrote in message
    news:E47997B5-F297-4EA9-A6E8-99B360C716D2@newsgroup

    >I have a pretty good idea on what path to take, but I would like to see how
    > other professionals would handle this situation. The objective is to
    > increase remote user’s performance and plan for future growth.
    >
    > The problem is the site to site VPN for a remote office isn’t sufficient.
    > My overall plan is to use Remote Desktop. Below is the environment and
    > some
    > solutions I came up with.
    >
    > SBS Server 2003
    > Power Edge 1900
    > 1 Quad Core Xeon E5310 @ 1.60 GHz
    > 6 GB Ram
    > 1 Perc 5i with a 250 GB RAID 1 Volume
    > 1 Adaptec 2045 with 200 GB RAID 10 Volume
    > 20 SBS Cals
    > 5 Terminal Server cals
    >
    > Services
    > Exchange 2003
    > File and Print
    > Business apps(Access Database, BestCase, PM TABS)
    > VPN
    >
    > Jacksonville location
    > Cable internet
    > VOIP
    > Server
    > 18 employees
    >
    > Dayton location
    > Cable internet
    > POTS
    > 2 employees, planning to expand
    >
    > We purchased 5 TS cals and some hardware upgrades because my plan was to
    > enable Application mode for the Remote Users. Unfortunately, I forgot
    > this
    > isn’t possible on the SBS Server. So I am looking for suggestions.
    >
    > Solution A
    > Purchase Windows 2003 Standard, the remaining CPU, and upgrade to 8 GB of
    > RAM. Then using ESXi, create two virtual servers, one SBS Server and one
    > Terminal Server. Sell the remaining hardware.
    >
    > Windows Server 2003($600)
    > Processor Xeon E5310($300)
    > RAM 2GB kit ($400)
    >
    > Advantages
    > Lower cost
    > Low bandwidth requirement
    > Expandability via VPN\RDP
    > Centralized
    > One Physical Server
    >
    > Disadvantages
    > Internet dependant
    > Remote Desktop
    > Legacy software
    >
    >
    > Solution B
    > Purchase SBS 2008, the remaining CPU, and upgrade to 8 GB of RAM. Then
    > using
    > ESXi, create two virtual servers, one SBS Server and one Terminal Server.
    > Sell the remaining hardware and software.
    >
    > Wndows Server 2008 with cals($3500)
    > Pocessor Xeon E5310 ($300)
    > RAM 2GB kit ($400)
    >
    > Advantages
    > Low bandwidth requirement
    > Expandability via VPN\RDP
    > Centralized
    > One Physical Server
    >
    > Disadvantages
    > Higher cost
    > Internet dependant
    > Remote Desktop
    >
    > Solution C
    > Purchase a small Windows Server with enough storage to setup DFS to
    > replicate data between Jacksonville and Daytona.
    >
    > Server with 2003 and 600 GB storage($3000)
    >
    > Advantages
    > Moderate cost
    >
    > Disadvantages
    > High bandwidth requirement
    > Legacy software
    > Two physical servers
    > Decentralized
    > Limited expandability
    >
    > Thanks in advance for any input,
    >
    > Raymond
    >

      My System SpecsSystem Spec

  3. #3


    rjskelton Guest

    Re: Seeking suggestions / solutions for SBS situation

    Thanks Charlie, your input is much appreciated.

    Would anyone else like to input?

    "Charlie Russel - MVP" wrote:

    > You'll find that option B simply doesn't have enough RAM. SBS 2008 needs a
    > _minimum_ of about 6 GB to function well. Depending on your apps, your
    > Terminal Server will be OK at 2 GB of RAM only if it's not heavily used at
    > all. But in either case, you'd need something for the hypervisor parent. And
    > for 23 users, I'd bump it up beyond that, for sure. Say to at least 12 to 16
    > GB.
    >
    > I wouldn't choose ESXi for virtualiztion, simply because I prefer to put all
    > my horses in the same barn and simplify the finger pointing.
    >
    > You don't specify what version your TS CALs are. This is a solution that
    > cries out for TS RemoteApps, but that will require Server 2k8 or Server 2k8
    > R2 TS CALs. (Both can be used interchangeably with either Server 2k8 or R2
    > servers)
    >
    > --
    > Charlie.
    > http://msmvps.com/blogs/russel
    >
    >
    >
    >
    > "rjskelton" <rjskelton@newsgroup> wrote in message
    > news:E47997B5-F297-4EA9-A6E8-99B360C716D2@newsgroup

    > >I have a pretty good idea on what path to take, but I would like to see how
    > > other professionals would handle this situation. The objective is to
    > > increase remote user’s performance and plan for future growth.
    > >
    > > The problem is the site to site VPN for a remote office isn’t sufficient.
    > > My overall plan is to use Remote Desktop. Below is the environment and
    > > some
    > > solutions I came up with.
    > >
    > > SBS Server 2003
    > > Power Edge 1900
    > > 1 Quad Core Xeon E5310 @ 1.60 GHz
    > > 6 GB Ram
    > > 1 Perc 5i with a 250 GB RAID 1 Volume
    > > 1 Adaptec 2045 with 200 GB RAID 10 Volume
    > > 20 SBS Cals
    > > 5 Terminal Server cals
    > >
    > > Services
    > > Exchange 2003
    > > File and Print
    > > Business apps(Access Database, BestCase, PM TABS)
    > > VPN
    > >
    > > Jacksonville location
    > > Cable internet
    > > VOIP
    > > Server
    > > 18 employees
    > >
    > > Dayton location
    > > Cable internet
    > > POTS
    > > 2 employees, planning to expand
    > >
    > > We purchased 5 TS cals and some hardware upgrades because my plan was to
    > > enable Application mode for the Remote Users. Unfortunately, I forgot
    > > this
    > > isn’t possible on the SBS Server. So I am looking for suggestions.
    > >
    > > Solution A
    > > Purchase Windows 2003 Standard, the remaining CPU, and upgrade to 8 GB of
    > > RAM. Then using ESXi, create two virtual servers, one SBS Server and one
    > > Terminal Server. Sell the remaining hardware.
    > >
    > > Windows Server 2003($600)
    > > Processor Xeon E5310($300)
    > > RAM 2GB kit ($400)
    > >
    > > Advantages
    > > Lower cost
    > > Low bandwidth requirement
    > > Expandability via VPN\RDP
    > > Centralized
    > > One Physical Server
    > >
    > > Disadvantages
    > > Internet dependant
    > > Remote Desktop
    > > Legacy software
    > >
    > >
    > > Solution B
    > > Purchase SBS 2008, the remaining CPU, and upgrade to 8 GB of RAM. Then
    > > using
    > > ESXi, create two virtual servers, one SBS Server and one Terminal Server.
    > > Sell the remaining hardware and software.
    > >
    > > Wndows Server 2008 with cals($3500)
    > > Pocessor Xeon E5310 ($300)
    > > RAM 2GB kit ($400)
    > >
    > > Advantages
    > > Low bandwidth requirement
    > > Expandability via VPN\RDP
    > > Centralized
    > > One Physical Server
    > >
    > > Disadvantages
    > > Higher cost
    > > Internet dependant
    > > Remote Desktop
    > >
    > > Solution C
    > > Purchase a small Windows Server with enough storage to setup DFS to
    > > replicate data between Jacksonville and Daytona.
    > >
    > > Server with 2003 and 600 GB storage($3000)
    > >
    > > Advantages
    > > Moderate cost
    > >
    > > Disadvantages
    > > High bandwidth requirement
    > > Legacy software
    > > Two physical servers
    > > Decentralized
    > > Limited expandability
    > >
    > > Thanks in advance for any input,
    > >
    > > Raymond
    > >
    >
    > .
    >

      My System SpecsSystem Spec

  4. #4


    Boon Tee [SBS-MVP] Guest

    Re: Seeking suggestions / solutions for SBS situation

    There isn't much more to add to Charlie's advice.

    Option B is a good way to go, IF you are happy to go through all the added
    work of buying and selling hardware.
    1. Buy SBS2008 Premium.
    2. Use HyperV with the second license (you get a 2nd Win2008 license with
    Premium) and vitualize both the SBS and TS
    3. Definitely need at least 16GB RAM, and more if you can afford it.

    --
    Regards,
    Boon



    "rjskelton" <rjskelton@newsgroup> wrote in message
    news:E651A1A7-E0E9-4F6F-A5D2-0C0389E3A58F@newsgroup

    > Thanks Charlie, your input is much appreciated.
    >
    > Would anyone else like to input?
    >
    > "Charlie Russel - MVP" wrote:
    >

    >> You'll find that option B simply doesn't have enough RAM. SBS 2008 needs
    >> a
    >> _minimum_ of about 6 GB to function well. Depending on your apps, your
    >> Terminal Server will be OK at 2 GB of RAM only if it's not heavily used
    >> at
    >> all. But in either case, you'd need something for the hypervisor parent.
    >> And
    >> for 23 users, I'd bump it up beyond that, for sure. Say to at least 12 to
    >> 16
    >> GB.
    >>
    >> I wouldn't choose ESXi for virtualiztion, simply because I prefer to put
    >> all
    >> my horses in the same barn and simplify the finger pointing.
    >>
    >> You don't specify what version your TS CALs are. This is a solution that
    >> cries out for TS RemoteApps, but that will require Server 2k8 or Server
    >> 2k8
    >> R2 TS CALs. (Both can be used interchangeably with either Server 2k8 or
    >> R2
    >> servers)
    >>
    >> --
    >> Charlie.
    >> http://msmvps.com/blogs/russel
    >>
    >>
    >>
    >>
    >> "rjskelton" <rjskelton@newsgroup> wrote in message
    >> news:E47997B5-F297-4EA9-A6E8-99B360C716D2@newsgroup

    >> >I have a pretty good idea on what path to take, but I would like to see
    >> >how
    >> > other professionals would handle this situation. The objective is to
    >> > increase remote user’s performance and plan for future growth.
    >> >
    >> > The problem is the site to site VPN for a remote office isn’t
    >> > sufficient.
    >> > My overall plan is to use Remote Desktop. Below is the environment and
    >> > some
    >> > solutions I came up with.
    >> >
    >> > SBS Server 2003
    >> > Power Edge 1900
    >> > 1 Quad Core Xeon E5310 @ 1.60 GHz
    >> > 6 GB Ram
    >> > 1 Perc 5i with a 250 GB RAID 1 Volume
    >> > 1 Adaptec 2045 with 200 GB RAID 10 Volume
    >> > 20 SBS Cals
    >> > 5 Terminal Server cals
    >> >
    >> > Services
    >> > Exchange 2003
    >> > File and Print
    >> > Business apps(Access Database, BestCase, PM TABS)
    >> > VPN
    >> >
    >> > Jacksonville location
    >> > Cable internet
    >> > VOIP
    >> > Server
    >> > 18 employees
    >> >
    >> > Dayton location
    >> > Cable internet
    >> > POTS
    >> > 2 employees, planning to expand
    >> >
    >> > We purchased 5 TS cals and some hardware upgrades because my plan was
    >> > to
    >> > enable Application mode for the Remote Users. Unfortunately, I forgot
    >> > this
    >> > isn’t possible on the SBS Server. So I am looking for suggestions.
    >> >
    >> > Solution A
    >> > Purchase Windows 2003 Standard, the remaining CPU, and upgrade to 8 GB
    >> > of
    >> > RAM. Then using ESXi, create two virtual servers, one SBS Server and
    >> > one
    >> > Terminal Server. Sell the remaining hardware.
    >> >
    >> > Windows Server 2003($600)
    >> > Processor Xeon E5310($300)
    >> > RAM 2GB kit ($400)
    >> >
    >> > Advantages
    >> > Lower cost
    >> > Low bandwidth requirement
    >> > Expandability via VPN\RDP
    >> > Centralized
    >> > One Physical Server
    >> >
    >> > Disadvantages
    >> > Internet dependant
    >> > Remote Desktop
    >> > Legacy software
    >> >
    >> >
    >> > Solution B
    >> > Purchase SBS 2008, the remaining CPU, and upgrade to 8 GB of RAM. Then
    >> > using
    >> > ESXi, create two virtual servers, one SBS Server and one Terminal
    >> > Server.
    >> > Sell the remaining hardware and software.
    >> >
    >> > Wndows Server 2008 with cals($3500)
    >> > Pocessor Xeon E5310 ($300)
    >> > RAM 2GB kit ($400)
    >> >
    >> > Advantages
    >> > Low bandwidth requirement
    >> > Expandability via VPN\RDP
    >> > Centralized
    >> > One Physical Server
    >> >
    >> > Disadvantages
    >> > Higher cost
    >> > Internet dependant
    >> > Remote Desktop
    >> >
    >> > Solution C
    >> > Purchase a small Windows Server with enough storage to setup DFS to
    >> > replicate data between Jacksonville and Daytona.
    >> >
    >> > Server with 2003 and 600 GB storage($3000)
    >> >
    >> > Advantages
    >> > Moderate cost
    >> >
    >> > Disadvantages
    >> > High bandwidth requirement
    >> > Legacy software
    >> > Two physical servers
    >> > Decentralized
    >> > Limited expandability
    >> >
    >> > Thanks in advance for any input,
    >> >
    >> > Raymond
    >> >
    >>
    >> .
    >>

      My System SpecsSystem Spec

Seeking suggestions / solutions for SBS situation problems?

Similar Threads
Thread Thread Starter Forum Replies Last Post
Suggestions / Solutions required gapsinger Software 0 14 Oct 2009
Re: 32 bit or 64 bit in this situation? Al Romanosky Vista performance & maintenance 1 29 Jun 2009
Newbie seeking suggestions on Live Messenger bot plugin Liming Live Messenger 0 14 Jan 2008
OT: Seeking webinar solutions..... jim Vista General 1 07 Jan 2008
Can any one seriously solve this situation? Inick06 Vista General 0 20 Aug 2007