SBS 2003 - Server 2003 - Terminal Services

Discussion in 'Windows Small Business Server' started by Steve LLG, Nov 11, 2004.

  1. Steve LLG

    Steve LLG Guest

    I have a client with an existing SBS 2003 installation/domain running on
    some older hardware (starting to show it's age/limitations). We are
    implementing a resource hungry Line of Business application and it needs to
    be remotely accessed via TS. We are ordering new hardware and would love to
    install SBS and the new application together on the new hardware. Trouble
    being, not having TS Application mode on SBS.

    My questions is this: Can I install the line of business application and SBS
    2003 on the new hardware, install Server 2003 as a member server and TS on
    the old hardware and access remotely the application on the SBS box through
    TS on the Server 2003 box (Can TS be used to access an application running
    on another server) ?
    Steve LLG, Nov 11, 2004
    1. Advertisements

  2. Steve LLG

    Wes Guest

    Hi Steve,

    Yes. As long as you are using Windows 2000 Professional or XP Professional
    clients to connect to your Terminal Server, you will not need to purchase
    any additional TS CALs (they are included with the product.) Your Terminal
    Service will use up one of your SBS CAL's..

    Kind regards,

    Wes, Nov 11, 2004
    1. Advertisements

  3. If the application is running on the SBS box... then no. However, if the
    client part of the program can be run on the TS box then there is no

    Think about Terminal Server as a bunch of Windows XP machines in the same
    box. If you can install the program on a stand alone machine then there is a
    great probability that you can do the same on TS.
    Javier Gomez [SBS MVP], Nov 11, 2004
  4. Steve LLG

    Steve LLG Guest

    Hmmm,... I'm starting to like the sound of this,... So:

    I could install sbs2003, the data server and application server on the new
    hardware - then install WIN SVR 2003 and the client application on the older
    hardware - sounds like a great plan as all that will be running on the old
    hardware is TS and the client application - Sounds quite simple and logical
    and I won't even need to worry about backing up the older server

    has anyone else tried anything similar????


    Steve LLG, Nov 11, 2004
  5. Hi Steve,

    it's running here in your constellation (SBS2003 + Windows Server 2003
    Terminal Services) for about a year without any problems and ease of
    administration (Compaq Evo T20/30 as Thin-Clients for Terminal Server).

    Tobias Redelberger

    StarNET Services (HomeOffice)
    Schoenbornstr. 57
    D-97440 Werneck

    Tel: +49-(0)9722-4835
    Mobil: +49-(0)179-25 98 341
    Tobias Redelberger, Nov 11, 2004
  6. Hi Wes,

    that's wrong ... almost wrong.

    With Windows 2003 there is only a TS CALs "included" (you have to get one
    here: with the Windows XP
    Professional if you bought and activated Windows XP Professional before
    24.April 2003 (). And no, there isn't that option for Windows 2000
    Professional at all.

    If you're using Windows 2000 Server as your Terminal Server (with the
    drawbacks of RDP5 (e.g. 256 colors)), then you are right, Windows 2000
    Professional or XP Professional will not need any additional TS CALs (they
    are included with the product.)

    More Info:
    Frequently Asked Questions About Terminal Services
    -> Licensing

    Q. Do Windows XP and Windows 2000 Professional have built-in Terminal
    Services CALs?

    A. No, Microsoft desktop operating systems (including Windows XP and Windows
    2000 Professional) do not have a "built-in" Terminal Services CAL.

    For Windows 2000 Terminal Servers, the license server issues machines
    running Windows 2000/Windows XP Professional with a "free" Terminal Services
    CAL from its built-in pool (and its use is permitted under the Windows 2000
    Server EULA). Windows XP Professional is a successor to Windows 2000
    Professional, and as a result does not need a Terminal Services CAL to
    access a Windows 2000 Server running Terminal Services. However, Windows XP
    Home Edition is not a successor to Windows 2000 Professional (rather, it is
    a successor to Windows Millennium Edition) and therefore does require a
    Terminal Services CAL in order to access Windows 2000 Terminal Services.

    For Windows Server 2003 Terminal Servers, all clients need installed CALs
    assigned to them in order for them to connect to Windows Server Terminal
    Servers. (There is no "built-in" pool.) Owners of Windows XP Professional
    desktop licenses are eligible for free TS CALs, however. For more
    information, see Terminal Server Licensing Transition Plan.

    Tobias Redelberger

    StarNET Services (HomeOffice)
    Schoenbornstr. 57
    D-97440 Werneck

    Tel: +49-(0)9722-4835
    Mobil: +49-(0)179-25 98 341
    Tobias Redelberger, Nov 11, 2004
  7. Steve LLG

    Wes Guest

    Hi Tobias,

    Your information has been really helpful. I was thinking of a Windows 2000
    Terminal Server when I posted but I wasn't aware that how Windows 2003
    changes things.

    Many thanks,

    Wes, Nov 11, 2004
  8. I agree with Tobias... I have a client with a hefty SBS box that host the
    program data and databases and a TS box that host the users desktops (both
    boxes have gigabit cards). I use a mix of thin clients and XP boxes (as the
    TS clients) and works very well (and little internet bandwidth is consumed).

    My only concern would be to make sure the app is compatible with Terminal
    Javier Gomez [SBS MVP], Nov 11, 2004
  9. Steve LLG

    Ron Gabaree Guest

    Hi Steve,

    I have implemented a new installation just like what you are proposing. SBS
    Standard as the server and Win2003 TS.

    I would ask yourself two questions:

    1) Are your application(s) compatible with TS? It will be important to ask
    this for any and all applications you forsee using. Keep in mind that some
    of the most simply programs (like Quickbooks) are not supported on TS.
    2) How many users to you forsee using this? As one posted indicated...think
    of TS2003 as a bunch of Windows XP Boxes. Following on that same
    vein.....will your older server have the horsepower?
    3) I would atleast take a long look at the memory in the old server. An
    upgrade might be money well spent.
    4) I am not sure what you will be using for a router/firewall. If you are
    using what comes with should be fine. If you will be using a
    hardware unit I STRONGLY reccomend not cheaping out. My experience with the
    cheaper routers have not been good with RDP connections. Routers in the
    $100-$200 range (and up) minimally are the best bet.

    Good Luck.

    I hope this helps.


    Ron Gabaree, Nov 12, 2004
  10. Steve LLG

    Steve LLG Guest

    Well, I'll tell you what I've discovered, decided to do and ordered. When
    everything is up and running about 10 days from now I'll tell you how it is

    First of all, The client hasn't skimped on router/firewalls modems and ADSL
    connections. In fact, we have a dedicated ADSL connection (at head office
    just to handle remote TS clients) and hardware VPN boxes at both ends and a
    separate ADSL account to handle browsing traffic and external email. The
    application as it turns out is TS compatible and according to the vendor,
    about half of the existing installations around the World utilise TS either
    for thin clients locally or remote clients via VPN.

    I'm going to go ahead and install SBS2003, the Database layer and
    application server layer components on the robust new hardware. I'm going
    to install SVR 2003 w/TS and the client application on the old server plus
    add some memory. There shouldn't ever be more than two client machine using
    the app on the TS box. The client is running a Gigabit network, so I'm not
    to worried about latency between the SBS and SVR boxes.

    Like I said, I'll let everyone know how it all goes.


    Steve LLG, Nov 12, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.