Re: Using old Server 2000 as terminal server with SBS 2003
Thanks for the response Vera. I'm a very clever trouble shooter, but this
terminal services issue really has me stumped. Please let me turn this into
two questions.
===========
First, just so I'm clear on the normal way to set up terminal services:
Primary server like SBS2003
CALS for each device or user connected to the primary server
Secondary server like Server 2003, as terminal server
CALs for each device or user connected to the secondary server
CALs for each device or user accessing terminal services on the secondary
server.
Is that correct? Or am I over licensing?
===========
Now, more correctly about my immediate problem:
I have the company's old SBS 2000. Can I make that be the terminal server,
while using the new SBS2003 machine as the license server?
As I understand it, SBS2003 won't function as a terminal server at all. So,
the only other advice I've read says to have a different server act as the
terminal server, though SBS2003 can be the license server.
If that's so, can I use SBS2000 as the terminal server? I would put in into
VMware on the SBS2003 server's machine, or just use the old box. I would have
folks use the IP address of the SBS2000 server to connect to terminal
services, then SBS2000 would check with SBS2003 to see if there is a license.
Background: I'm not trying to use a full desktop enviornment in terminal
services sessions. There is only one application I want to run and that one
is very low demand. This is to facilitate remote connections to the office.
Usually the attorneys only access documents from the server for review and
that is very basic VPN access. But there is a special calendar program that
needs to be accessed while running on the server, because as you probably
know databases don't do well over the internet (we tried and it took up to 5
minutes for the program to be ready for use).
Background: The office doesn't use any of the features of SBS. The SBS2003
server only functions as a file server, with the exception of one legal
office application being served to the workstations. Otherwise, no Exchange,
no web services, no IIS at all. If the office had known this would be a
problem they wouldn't have purchased SBS, just Server 2003. But they didn't
know that at the time.
Background: The old SBS 2000 licenses are complete with 20 user CALS. The
new machine was purchased complete with new licenses.
Background: Not knowing all the limitations to terminal services on SBS2003,
I had the company purchase 5 open terminal services user CALs.
==========
Well, if nothing else I'm clearer on my questions for having written this.
If you got this far I really appreciate your attention to my problems.
John in Oregon
"Vera Noest [MVP]" wrote:
> I'm not getting the whole picture, John.
> Do you mean that you currently have a SBS2003 domain and want to
> add a SBS2000, because you are still allowed to install Terminal
> Services on SBS2000?
> I believe that this is impossible, since you can only have a single
> SBS server in a domain, and it must be the forest root domain.
>
> But you'd better ask in the sbs newsgroup, to get a authorative
> answer.
>
> microsoft.public.windows.server.sbs
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>