[THIN] Re: TS Licensing issue
- From: Rob Beekmans <RobBeekmans@xxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Sun, 12 Feb 2006 08:56:51 +0100
Same here, I also thought the servers were running 2003.
I also support the idea Rick suggested, about the -nodc option...that's the
best option you have before building a 2003 licensing server.
greetz
rob
_____
Van: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] Namens
Rick Mack
Verzonden: zondag 12 februari 2006 6:52
Aan: thin@xxxxxxxxxxxxx
Onderwerp: [THIN] Re: TS Licensing issue
Hi James,
Nope, my mistake, I assumed the TS systems were running Server 2003. But I
suspect a 2000 TS license server may have issues in a 2003 domain, unless
running the 2000 licenses server with the -nodc switch works.
The relevant article is listed below:
How to install Terminal Services License Server on a Windows 2000 member
server in a Windows 2000 domain
This article was previously published under Q313923
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:
256986 Description of the Microsoft Windows Registry
SUMMARY
This article describes how to install the Windows 2000 Terminal Services
License Server service on a Windows 2000 member server in a Windows 2000
domain.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
You can modify the Windows 2000 Terminal Services License Server service so
that it will run on Windows 2000 member servers in a Windows 2000 domain. To
do so, use Registry Editor (Regedt32.exe) to locate the ImagePath value in
the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing
Modify the ImagePath value to %SystemRoot%\System32\lserver.exe -nodc, and
then quit Registry Editor.
The typical Windows 2000 Terminal Services Licensing Discovery process that
is used by Windows 2000 Terminal Servers does not detect member servers that
are configured to run Terminal Services Licensing with the -nodc switch.
The discovery process enumerates and queries domain controllers in the
enterprise, and does not query a member server to determine if Terminal
Services Licensing is installed.
regards,
Rick
Ulrich Mack
Volante Systems
_____
From: thin-bounce@xxxxxxxxxxxxx on behalf of James Hill
Sent: Sun 12/02/2006 9:37
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: TS Licensing issue
Sorry it was late and I wasn't very clear.
I have 2 x Windows 2000 terminal servers running Presentation Server 3.
They are now members of a 2003 domain.
From what I can tell I will need to install a 2003 terminal server licensing
server and forget about the old 2000 licensing server.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Rick Mack
Sent: Sunday, 12 February 2006 8:12 AM
To: thin@xxxxxxxxxxxxx
Subject: RE: [THIN] TS Licensing issue
Hi James,
You need a 2003 TS Licensing server for 2003 TS systems. It can be a member
server rather than a DC.
The DefaultLicenseServer value is for Windows 2000, and 2003 is different
and uses a LicesServers key with Server name keys under it. Check out the
Microsoft technote 279561 at:
http://support.microsoft.com/kb/279561/EN-US/
For the ultimate description of TS licensing see Brian Madden's article:
http://www.brianmadden.com/content/content.asp?id=154
Or if you want a nice, simple explanation:
http://blogs.technet.com/tristank/archive/2004/06/10/152371.aspx
regards,
Rick
Ulrich Mack
Volante Systems
Level 2, 30 Little Cribb Street
Coronation Drive Office Park
Milton Qld 4064
tel: +61 7 32431847
fax: +61 7 32431992
rick.mack@xxxxxxxxxxxxxx
_____
From: thin-bounce@xxxxxxxxxxxxx on behalf of James Hill
Sent: Sat 11/02/2006 19:54
To: thin@xxxxxxxxxxxxx
Subject: [THIN] TS Licensing issue
Hi All,
I have had a Citrix Presentation 3 farm running on Win2K boxes in an NT
domain for a while. Today I have moved these boxes to a 2003 domain and
made them members of it.
The Terminal Server Licensing server (also a Win2K server) was moved to the
same subnet as the Citrix Farm but is now just a member of a workgroup as
the licensing server service would not start if the server was a member of
the 2003 domain.
I can't get the Terminal Servers to find the Terminal Server licensing
server. They can resolve the NETBIOS name and I have specified the
Licensing Server via the DefalultLicenseServer reg key but it still doesn't
work.
It's been a very long day and even longer week and my brain is about to give
up. Help!
Thanks,
James.
############################################################################
#########
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has
been sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it
in error please notify the sender immediately by reply e-mail and destroy
all copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby
disclaimed to the extent permitted by law.
############################################################################
#########
############################################################################
#########
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has
been sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it
in error please notify the sender immediately by reply e-mail and destroy
all copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby
disclaimed to the extent permitted by law.
############################################################################
#########
############################################################################
#########
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has
been sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it
in error please notify the sender immediately by reply e-mail and destroy
all copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby
disclaimed to the extent permitted by law.
############################################################################
#########
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.2/251 - Release Date: 04-02-2006
Other related posts:
