Domain Member Licensing

[Guest Brett Chapman]

I am trying to understand the licensing for Terminal Server Services.

I have a Server 2003 server with some applications on that I would like

people to be able to run remote desktop on.

The user's machines are all in different domains, but they have accounts in

the domain the server resides in.

Will these users be able to connect to the RDP server in my domain, or will

the licensing prevent this unless it is in an enterprise role?

[Guest Vera Noest [MVP]]

Re: Domain Member Licensing

 

It doesn't matter where the clients or the users are, since they

never communicate directly with the TS Licensing Server. It's the

Terminal Server who contacts the licensing server on behalf of the

clients and requests a license.

So the only requirement is that your TS and your LS can communicate.

Even they don't have to be in the same domain or forest, but there

must be a trust relationship between the domains they are a member

of.

_________________________________________________________

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

<BrettChapman@discussions.microsoft.com> wrote on 24 nov 2007 in

microsoft.public.windows.terminal_services:

> I am trying to understand the licensing for Terminal Server

> Services. I have a Server 2003 server with some applications on

> that I would like people to be able to run remote desktop on.

> The user's machines are all in different domains, but they have

> accounts in the domain the server resides in.

> Will these users be able to connect to the RDP server in my

> domain, or will the licensing prevent this unless it is in an

> enterprise role?