Deploying Server 2008 Terminal Services in a SBS 2003 environment.

[Guest XateEsix]

Hello,

I am working on deploying Server 2008 Terminal Services in a Small Business

Server 2003 environement. I have several questions I need assistance with.

 

1. As I understand it TS CALS are included as part of the SBS CAL. Can

someone confirm this?

 

2. I was told by a Microsoft Sales Support Rep that Server 2008 Terminal

Services could be deployed using the SBS 2003 CALs. Can anyone confirm this?

 

3. If the answers to questions 1 & 2 are both true then can someone help me

understand how it needs to be configured to work?

 

4. What version and on what server should the license server be running?

 

In testing the terminal services work fine on the 2008 Server until it is

switched to multiple user mode. When its in multiple user mode I can't even

get it to connect. The connection just seems to be refused. I have disabled

the firewall. I have gone over my configs and everything looks fine.

The license diagnosis says the SBS license server is incompatible and the

license server on Server 2008 doesn't see any licenses. Though in my

experience even when a terminal server doesn't see available licenses it will

issue temoporary ones until the expire before it starts to refuse

connections. Has this behavior in TS servers been changed?

 

Any asistance provided will be very much apreciated.

Thank you

John

[Guest Vera Noest [MVP]]

Re: Deploying Server 2008 Terminal Services in a SBS 2003 environment.

 

comments inline

 

=?Utf-8?B?WGF0ZUVzaXg=?= <XateEsix@discussions.microsoft.com>

wrote on 04 jul 2008 in

microsoft.public.windows.terminal_services:

> Hello,

> I am working on deploying Server 2008 Terminal Services in a

> Small Business Server 2003 environement. I have several

> questions I need assistance with.

 

Many things are special in an SBS environment. The best place for

SBS related questions is the SBS newsgroup. But read on...

> 1. As I understand it TS CALS are included as part of the SBS

> CAL. Can someone confirm this?

 

No. From the SBS Terminal Services FAQ (about a 2003 TS, but the

same applies to 2008 TS)

http://www.microsoft.com/windowsserver2003/sbs/evaluation/faq/term.

mspx

 

Q. I have another server running Windows Server 2003 on my network,

and Terminal Services is in application sharing mode. I am sharing

an application with users who don’t otherwise connect to SBS. How

many CALs are needed?

 

A. You still need an SBS 2003 R2 CAL for each user or device that

authenticates on the SBS 2003 R2 network. When you log on to a

Terminal Server session, you authenticate on the network, which

requires you to have an SBS 2003 R2 CAL.” In addition, you will

also need Terminal Server CALs for each Terminal Services user. See

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts200

3.mspx for more information on Terminal Services licensing

requirements. You do not require Windows Server CALs, as those are

covered by your SBS CALs.

> 2. I was told by a Microsoft Sales Support Rep that Server 2008

> Terminal Services could be deployed using the SBS 2003 CALs. Can

> anyone confirm this?

 

Partly. You can access the W2008 server (for example as a file

server), using the SBS CALs. But you will still need the TS CALs.

From the SBS Licensing FAQ

http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licen

sing.mspx

 

Q. Does the SBS 2003 R2 CAL allow me to access Windows Server 2008

connected to the SBS 2003 R2 domain?

 

A. Yes, until May 31, 2009, SBS 2003 R2 customers who buy a copy of

Windows Server 2008 and add it to the SBS 2003 R2 domain can use

their SBS 2003 R2 CALs to access the Server.

> 3. If the answers to questions 1 & 2 are both true then can

> someone help me understand how it needs to be configured to

> work?

 

1 is not true, 2 is partly true.

> 4. What version and on what server should the license server be

> running?

 

A Windows 2008 Terminal Server must connect to a Windows 2008 TS

Licensing Server. So you'll have to install the TS Licensing

Service on the 2008 server.

> In testing the terminal services work fine on the 2008 Server

> until it is switched to multiple user mode. When its in multiple

> user mode I can't even get it to connect. The connection just

> seems to be refused. I have disabled the firewall. I have gone

> over my configs and everything looks fine. The license diagnosis

> says the SBS license server is incompatible and the license

> server on Server 2008 doesn't see any licenses. Though in my

> experience even when a terminal server doesn't see available

> licenses it will issue temoporary ones until the expire before

> it starts to refuse connections. Has this behavior in TS servers

> been changed?

 

No, you should still be able to first use the Terminal Server's

grace period, and then receive temporary licenses.

Are you getting any error messages when you try to connect?

Is there anything in the EventLog on the TS?

> Any asistance provided will be very much apreciated.

> Thank you

> John

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

[Guest Todd Woodyatt]

Re: Deploying Server 2008 Terminal Services in a SBS 2003 environm

 

Re: Deploying Server 2008 Terminal Services in a SBS 2003 environm

 

Vera,

 

I did this, but (and the TS Server always appear in the list) but it says

when I try to connect: the server is unavailable... please meake sure it is

on and connected to the network... which it is.

 

Any ideas?

 

"Vera Noest [MVP]" wrote:

> comments inline

>

> =?Utf-8?B?WGF0ZUVzaXg=?= <XateEsix@discussions.microsoft.com>

> wrote on 04 jul 2008 in

> microsoft.public.windows.terminal_services:

>

> > Hello,

> > I am working on deploying Server 2008 Terminal Services in a

> > Small Business Server 2003 environement. I have several

> > questions I need assistance with.

>

> Many things are special in an SBS environment. The best place for

> SBS related questions is the SBS newsgroup. But read on...

>

> > 1. As I understand it TS CALS are included as part of the SBS

> > CAL. Can someone confirm this?

>

> No. From the SBS Terminal Services FAQ (about a 2003 TS, but the

> same applies to 2008 TS)

> http://www.microsoft.com/windowsserver2003/sbs/evaluation/faq/term.

> mspx

>

> Q. I have another server running Windows Server 2003 on my network,

> and Terminal Services is in application sharing mode. I am sharing

> an application with users who don’t otherwise connect to SBS. How

> many CALs are needed?

>

> A. You still need an SBS 2003 R2 CAL for each user or device that

> authenticates on the SBS 2003 R2 network. When you log on to a

> Terminal Server session, you authenticate on the network, which

> requires you to have an SBS 2003 R2 CAL.” In addition, you will

> also need Terminal Server CALs for each Terminal Services user. See

> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts200

> 3.mspx for more information on Terminal Services licensing

> requirements. You do not require Windows Server CALs, as those are

> covered by your SBS CALs.

>

> > 2. I was told by a Microsoft Sales Support Rep that Server 2008

> > Terminal Services could be deployed using the SBS 2003 CALs. Can

> > anyone confirm this?

>

> Partly. You can access the W2008 server (for example as a file

> server), using the SBS CALs. But you will still need the TS CALs.

> From the SBS Licensing FAQ

> http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licen

> sing.mspx

>

> Q. Does the SBS 2003 R2 CAL allow me to access Windows Server 2008

> connected to the SBS 2003 R2 domain?

>

> A. Yes, until May 31, 2009, SBS 2003 R2 customers who buy a copy of

> Windows Server 2008 and add it to the SBS 2003 R2 domain can use

> their SBS 2003 R2 CALs to access the Server.

>

> > 3. If the answers to questions 1 & 2 are both true then can

> > someone help me understand how it needs to be configured to

> > work?

>

> 1 is not true, 2 is partly true.

>

> > 4. What version and on what server should the license server be

> > running?

>

> A Windows 2008 Terminal Server must connect to a Windows 2008 TS

> Licensing Server. So you'll have to install the TS Licensing

> Service on the 2008 server.

>

> > In testing the terminal services work fine on the 2008 Server

> > until it is switched to multiple user mode. When its in multiple

> > user mode I can't even get it to connect. The connection just

> > seems to be refused. I have disabled the firewall. I have gone

> > over my configs and everything looks fine. The license diagnosis

> > says the SBS license server is incompatible and the license

> > server on Server 2008 doesn't see any licenses. Though in my

> > experience even when a terminal server doesn't see available

> > licenses it will issue temoporary ones until the expire before

> > it starts to refuse connections. Has this behavior in TS servers

> > been changed?

>

> No, you should still be able to first use the Terminal Server's

> grace period, and then receive temporary licenses.

> Are you getting any error messages when you try to connect?

> Is there anything in the EventLog on the TS?

>

> > Any asistance provided will be very much apreciated.

> > Thank you

> > John

>

> _________________________________________________________

> 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: Deploying Server 2008 Terminal Services in a SBS 2003 environm

 

Re: Deploying Server 2008 Terminal Services in a SBS 2003 environm

 

Again, you'd better ask in the dbs newsgroup. You might have to run

dcpromo /adprep and /forestprep on your DC before joining the 2008

TS LS to the domain, but I'm not sure.

 

_________________________________________________________

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?VG9kZCBXb29keWF0dA==?=

<ToddWoodyatt@discussions.microsoft.com> wrote on 25 aug 2008 in

microsoft.public.windows.terminal_services:

> Vera,

>

> I did this, but (and the TS Server always appear in the list)

> but it says when I try to connect: the server is unavailable...

> please meake sure it is on and connected to the network... which

> it is.

>

> Any ideas?

>

> "Vera Noest [MVP]" wrote:

>

>> comments inline

>>

>> =?Utf-8?B?WGF0ZUVzaXg=?= <XateEsix@discussions.microsoft.com>

>> wrote on 04 jul 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Hello,

>> > I am working on deploying Server 2008 Terminal Services in a

>> > Small Business Server 2003 environement. I have several

>> > questions I need assistance with.

>>

>> Many things are special in an SBS environment. The best place

>> for SBS related questions is the SBS newsgroup. But read on...

>>

>> > 1. As I understand it TS CALS are included as part of the SBS

>> > CAL. Can someone confirm this?

>>

>> No. From the SBS Terminal Services FAQ (about a 2003 TS, but

>> the same applies to 2008 TS)

>> http://www.microsoft.com/windowsserver2003/sbs/evaluation/faq/te

>> rm. mspx

>>

>> Q. I have another server running Windows Server 2003 on my

>> network, and Terminal Services is in application sharing mode.

>> I am sharing an application with users who don’t otherwise

>> connect to SBS. How many CALs are needed?

>>

>> A. You still need an SBS 2003 R2 CAL for each user or device

>> that authenticates on the SBS 2003 R2 network. When you log on

>> to a Terminal Server session, you authenticate on the network,

>> which requires you to have an SBS 2003 R2 CAL.” In addition,

>> you will also need Terminal Server CALs for each Terminal

>> Services user. See

>> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts

>> 200 3.mspx for more information on Terminal Services licensing

>> requirements. You do not require Windows Server CALs, as those

>> are covered by your SBS CALs.

>>

>> > 2. I was told by a Microsoft Sales Support Rep that Server

>> > 2008 Terminal Services could be deployed using the SBS 2003

>> > CALs. Can anyone confirm this?

>>

>> Partly. You can access the W2008 server (for example as a file

>> server), using the SBS CALs. But you will still need the TS

>> CALs. From the SBS Licensing FAQ

>> http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/li

>> cen sing.mspx

>>

>> Q. Does the SBS 2003 R2 CAL allow me to access Windows Server

>> 2008 connected to the SBS 2003 R2 domain?

>>

>> A. Yes, until May 31, 2009, SBS 2003 R2 customers who buy a

>> copy of Windows Server 2008 and add it to the SBS 2003 R2

>> domain can use their SBS 2003 R2 CALs to access the Server.

>>

>> > 3. If the answers to questions 1 & 2 are both true then can

>> > someone help me understand how it needs to be configured to

>> > work?

>>

>> 1 is not true, 2 is partly true.

>>

>> > 4. What version and on what server should the license server

>> > be running?

>>

>> A Windows 2008 Terminal Server must connect to a Windows 2008

>> TS Licensing Server. So you'll have to install the TS Licensing

>> Service on the 2008 server.

>>

>> > In testing the terminal services work fine on the 2008 Server

>> > until it is switched to multiple user mode. When its in

>> > multiple user mode I can't even get it to connect. The

>> > connection just seems to be refused. I have disabled the

>> > firewall. I have gone over my configs and everything looks

>> > fine. The license diagnosis says the SBS license server is

>> > incompatible and the license server on Server 2008 doesn't

>> > see any licenses. Though in my experience even when a

>> > terminal server doesn't see available licenses it will issue

>> > temoporary ones until the expire before it starts to refuse

>> > connections. Has this behavior in TS servers been changed?

>>

>> No, you should still be able to first use the Terminal Server's

>> grace period, and then receive temporary licenses.

>> Are you getting any error messages when you try to connect?

>> Is there anything in the EventLog on the TS?

>>

>> > Any asistance provided will be very much apreciated.

>> > Thank you

>> > John