Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > Windows 2003 Server (TECHNET) > Multiple TS license servers in the same domain
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 13th July 16:45
darrenzwbh
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


My current setup is a Windows 2003 DC with TS licensing installed in
enterprise and per device mode. We have several departments that share the
same license pool, but not budgets.....I have additional departments that
have not purchased TS licenses, so I use the domain Terminal Server Computers
security group to limit the servers that can request licenses.

One of the departments would like to breakaway from the shared pool and
create their own TS license server in per-user mode. I would expect that
they will use the local Terminal Server Computers security group to limit the
terminal servers that can request licenses from their server.

My question then would be.....How much of a headache will this cause me?
Will all the TS licensing servers get along?
  Reply With Quote


  sponsored links


2 13th July 16:45
jeff pitsch mvp
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


Considering that licensing is controlled by the terminal server (a server
can only be per device or per user), I would expect lots of headaches.
Unless they are buying their own terminal servers as well.

Jeff Pitsch
Microsoft MVP - Terminal Services
http://www.sbcgatekeeper.com
Your Terminal Services Security Website
  Reply With Quote
3 13th July 16:45
darrenzwbh
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


Sorry,

Yes, they are have thier own terminal server farm. All in all there is 15
terminal servers in the domain, 9 would like to stay with the enterprise TS
licensing server and 6 would like to go to thier own licensing server and
switch to per-user.
  Reply With Quote
4 13th July 16:45
tp
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


No headaches.

As long as they have their TS servers in Per User mode, it
doesn't really matter. They do not even need to install their
own TS licensing servers, because per user will not utilize
them (or your current enterprise ts licensing server either).

To summarize, the departments that want to switch to per
user should simply switch their terminal servers to per
user mode using Terminal Services Configuration.
That's ALL!

For legal purposes, they need to purchase the correct
amount of per user licenses.

There is a bug in 2003 RTM that will switch the TS server
to per device mode when using add/remove windows
components. You can fix this by installing SP1 or
contacting MS for the hotfix.

Thanks.

-TP
  Reply With Quote
5 13th July 16:45
jeff pitsch mvp
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


then you shouldn't have any headaches at all.

Jeff Pitsch
Microsoft MVP - Terminal Services
http://www.sbcgatekeeper.com
Your Terminal Services Security Website
  Reply With Quote
6 13th July 17:10
bruce sanderson
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


I've got a related question. Everything re TS Licensing appears to be
working, but I've encountered a puzzle.

We're in a very large domain (> 20 domain controllers, >30,000 computers).
We're a small agency that uses some services provided by that domain.

We have our own Windows 2003 Terminal Servers (30 of them), which are Domain
members of the large domain. When we first started with Windows 2003
Terminal Services, there was no Windows 2003 Terminal Services License
Server in the domain and we set up our own TS License server and added the
Per User TS CAL Tokens. We configured the Terminal Servers to use this
License Server as a "preferred" TS License server and controlled which TS
Servers could get licenses by using the "License Server Security Group"
Group Policy setting and a Global Group which is a member of the local group
"Terminal Server Computers" (as described in the "Microsoft Windows Server
2003 Terminal Server Licensing" do***ent ). All of the Terminal Servers are
configured to use "Per User" licensing (we have the hotfix from
http://support.microsoft.com/?kbid=834651 installed on all the Terminal
Servers). All of this works fine.

Some time later, a Windows 2003 Terminal Services License Server was added
to the domain (we don't manage the Domain per se, just our own computers,
OUs etc.). This new "Enterprise" TS License server shows up in the Terminal
Services Licensing tool, as do our own License Servers. This (new)
"Enterprise" License server has some Windows 2003 Terminal Services CAL
Tokens (per user).

I see the System Event Log entries several times per day that our License
server has refused to issue a license to this new "Enterprise" TS License
Server because it is not a member of the local Terminal Server Computers
group. This is fine with me - that computer is NOT one of our Terminal
Servers and we don't want to issue licenses to it. Why it is asking for
licenses in the first place is a mystery, but I'm not too concerned about
that.

Subsequently, we added some additional Terminal Servers. The "preffered" TS
License server was set on these servers using the WMI scripts from the
"Microsoft Windows Server 2003 Terminal Server Licensing" do***ent as had
been done for all of the Terminal Servers.

I'm beta testing Longhorn and was going to add that server to the Global
Group that lists all of the Terminal Servers that are permitted to use our
TS License server and noticed that the Terminal Servers that were recently
added are not listed in that Group. I checked these servers and they indeed
have our License Servers set as the "Preffered" license server
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\TermService\Parameters\LicenseServers
has the appropriate sub-keys).

I've checked the System Event Logs on those new Terminal Servers and there
are no licensing related entries. I've checked the System Event Log on the
TS License server computer and there are NO entries about refusing to issue
a license to the new Terminal Servers. Also, users can logon to Terminal
Services (either via RDP or the Citrix client) just like they do on the the
others and have been now for several months.

So, the puzzle is, why don't we have a problem? It would seem that the
"preffered" License server setting on the new Terminal Servers is being
ignored and the Domain provided Windows 2003 Terminal Services License
Server is being used instead.

Is this the way its supposed to work?

Is there a way to configure things on our Terminal Servers so that the
Domain supplied Windows 2003 Terminal Server License Server is NEVER used by
our Terminal Servers? I don't manage that server, but do manage all of our
Terminal Servers and License Servers.

--
Bruce Sanderson MVP
http://members.shaw.ca/bsanders/
It's perfectly useless to know the right answer to the wrong question.
  Reply With Quote
7 13th July 17:10
tp
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


Hi Bruce,

You don't have a problem because Per User licenses are
unmanaged. When TS server is set to Per User mode, it
will check to see if a TS Licensing server is available.

If it is unable to discover one, it will nag you with error
events in the log, and balloons on the taskbar if you have
"Show Tooltips for Licensing problems on the Terminal
Server" group policy set to either Enabled or Not configured.

It does not request licenses on behalf of connecting clients
(like it would in Per Device mode), because it is in
Per User mode. Therefore, it does not refuse a connecting
client when a license server is not available, or in your case,
not in the Terminal Server Computers group.

If it was attempting to request licenses, you would see
errors in the TS server's log from Source TermService, ID
1043 saying that it is not able to communicate with the LS
and to please make sure it is in the Terminal Server Computers
group.

-TP
  Reply With Quote
8 13th July 17:10
bruce sanderson
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


Hmm. When we first started with Windows 2003 Terminal Services there was no
"Enterprise" TS License server. If I recall correctly, unless the Terminal
Server was in the Group that listed all of the Terminal Servers permitted to
use the License Server, we would get Licensing "complaints".

So, it seems to me that the new Terminal Servers must be communicating with
the (relatavely new) Enterprise TS License server.

I appreciate that in per User mode, there is no license management per se,
but there must be a TS License server that the Terminal Server can
commmunicate with.

So, I'm still wondering if there is any way to tell our Terminal Servers to
NOT communicate with the Enterprise License server.

--
Bruce Sanderson MVP
http://members.shaw.ca/bsanders/
It's perfectly useless to know the right answer to the wrong question.
  Reply With Quote
9 13th July 17:11
tp
External User
 
Posts: 1
Default Multiple TS license servers in the same domain


I don't think your new TSs care much about the Enterprise
TS License server.

Have you checked your event log archives to see if the
servers actually were complaining about licensing when
in Per User mode, pre-Ent LS? I do not think they
would have complained if they were able to contact
your LS.

The do***entation says that if you have overrided TS
Licensing via the registry, the TS will only attempt auto
discovery if it is unsuccessful at contacting the servers
in the registry. In theory, this means that in your case
as long as your preferred TS Licensing servers are
reachable your TS servers will not contact the Enterprise
LS.

Now, I have not done a packet trace to verify that
the do***entation is correct, so who knows. Have
you checked the registry on your TSs to see if they
have cached the name of the enterprise LS?

HKLM\SOFTWARE\Microsoft\MSLicensing\Parameters\Ent erpriseServerMulti

As to the licensing complaints, I went ahead and tested
this in my lab.

I implemented the Terminal Server Computers Security
group on the TS Licensing server, and made certain that
the TS was not a member. Next I restarted the TS,
connected to it via RDP, and examined the event log.

No TS licensing complaints. To make sure the security
option was in effect, I switched the server to Per Device
mode, and attempted a connection from a non-licensed
client.

Sure enough, on the TS server it logged event id
1043 (Unable to communicate with the LS...), and on
the TS Licensing server it logged event id 45 (A license
could not be issued to xx.xx.xx.xx because it is not
a member of the Terminal Server Computers group.)

-TP
  Reply With Quote


  sponsored links


Reply


Thread Tools
Display Modes




Copyright 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666