Using old Server 2000 as terminal server with SBS 2003

[Guest OregonJohn]

Thanks to Meinolf Weber for the answer about removing SBS 2003...so I can't

do that. I'm so frustrated with Terminal Services. I know, I read all about

why it shouldn't be part of SBS2003, but it costs so much to implement this

way...2 servers, 2 server OSs, 2 sets of CALS, and then the CALS for the

terminal services...gads!

 

Anyway, so I have the old SBS2000. Can I use that? I'm only trying to run a

single specialty software package (Abacus for attorneys) remotely, so I don't

need full desktops.

 

You know, it is so amazing to me how people out there are willing to help. I

am so very appreciative. Thank you all for taking the time to read these

questions and answer them.

[Guest Vera Noest [MVP]]

Re: Using old Server 2000 as terminal server with SBS 2003

 

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 ___

 

=?Utf-8?B?T3JlZ29uSm9obg==?=

<OregonJohn@discussions.microsoft.com> wrote on 08 okt 2007 in

microsoft.public.windows.terminal_services:

> Thanks to Meinolf Weber for the answer about removing SBS

> 2003...so I can't do that. I'm so frustrated with Terminal

> Services. I know, I read all about why it shouldn't be part of

> SBS2003, but it costs so much to implement this way...2 servers,

> 2 server OSs, 2 sets of CALS, and then the CALS for the terminal

> services...gads!

>

> Anyway, so I have the old SBS2000. Can I use that? I'm only

> trying to run a single specialty software package (Abacus for

> attorneys) remotely, so I don't need full desktops.

>

> You know, it is so amazing to me how people out there are

> willing to help. I am so very appreciative. Thank you all for

> taking the time to read these questions and answer them.

[Guest OregonJohn]

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 ___

>

[Guest Vera Noest [MVP]]

Re: Using old Server 2000 as terminal server with SBS 2003

 

Regarding your licensing:

I *believe* that you don't need extra server CALs when you add a

2003 member server to your domain. Do do need TS CALs if the second

server runs TS. But I'm not sure, SBS is rather different from

Windows 2003, so I really recommend the sbs newsgroup.

 

About your plan to use the SBS2000 server as a Terminal Server: as

I wrote, I am pretty sure that SBS won't let you. A SBS2000 server

can be a TS for sure, but an SBS domain doesn't allow more then a

single SBS DC. So you cannot add the SBS2000 server to your SBS2003

domain. But again, the sbs newsgroup would be able to answer your

SBS questions much better.

 

The only real option when you need TS in an SBS2003 domain is to

add a Windows 2003 server as a member server and run TS on that

server.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

=?Utf-8?B?T3JlZ29uSm9obg==?=

<OregonJohn@discussions.microsoft.com> wrote on 09 okt 2007:

> 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 ___

>>

[Guest OregonJohn]

Re: Using old Server 2000 as terminal server with SBS 2003

 

Thank you Vera. I will contact the SBS group, and otherwise your answers

helped clarify several matters.

 

john in oregon