Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


April 03, 2006

How can I install a Windows Server 2003 Terminal Services licensing server?

RSS
Subscribe to Windows IT Pro | See More Terminal Server and Services Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!

A. If you require full terminal server functionality beyond the basic two administrative sessions to a server, you must install the Windows 2003 Terminal Services Licensing service on a server in the environment before the 120-day grace period expires. After 120 days, users will no longer be able to connect to the terminal server.

In small environments, both the terminal server and the terminal server licensing server can be the same box, but for larger environments, this isn't advised. Windows 2003 terminal servers must communicate with a Windows 2003 licensing server; a Windows 2000 licensing server isn't suitable.

You can use most any machine to host the Terminal Services Licensing service because the overhead involved is minimal. The service uses only 10MB of memory and increments by only 5MB for each additional 6000 licenses added. In the case of a domain/workgroup terminal server licensing server, installing on a domain controller (DC) helps the terminal servers locate the licensing server. To install the Terminal Services Licensing service, perform the following steps:

  1. Start the Add or Remove Programs Control Panel applet (Start - Settings - Control Panel - Add or Remove Programs).
  2. Click the Add/Remove Windows Components button.
  3. Select the "Terminal Server Licensing" check box, as the figure shows, and click Next.
  4. You'll be prompted to enter the scope of the licensing server, enterprise, or domain/workgroup, as the figure shows. An enterprise licensing server will service any terminal server in the local Active Directory (AD) site, even from other domains (although the terminal servers must be a member of a domain and not a workgroup, and those domains must trust the domain that has the licensing server). A domain/workgroup licensing server will service only terminal servers from its local domain/workgroup but will service terminal servers in that domain from any site.
  5. Click Finish.

Next, start the Microsoft Management Server (MMC) Terminal Server Licensing snap-in (Start - Programs - Administrative Tools - Terminal Server Licensing). The local server will show as "Not activated." Right-click the server and select Activate, which will initiate the License Server Activation Wizard.

  1. Click Next to the wizard's welcome page.
  2. You'll be prompted to select the activation method. The options are Automatic connection, Web Browser, or Telephone. In this example, we'll select Automatic connection, as the figureshows. Click Next. Whichever method that you select will facilitate the connection to the Microsoft License Clearinghouse, allowing license server activation.
  3. Enter the company name and contact information, then click Next.
  4. You can add optional information such as email address and physical address. Click Next.
  5. You'll see a dialog box confirming activation, and by default, the licensing wizard will start when you click Next.

After the licensing service is installed for an enterprise server, a record is written to the sites container in the form of a TS-Enterprise-License-Server object, as the figure shows. The siteServer attribute identifies the name of the license server.

End of Article



Reader Comments

You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now




Top Viewed ArticlesView all articles
WinInfo Short Takes: Week of November 9, 2009

An often irreverent look at some of the week's other news, including some more Windows 7 sales momentum, some Sophos stupidity, Microsoft's cloud computing self-loathing, more whining from the browser makers, Zoho's "Fake Office," and much, much more ...

Command Prompt Tricks

One reader shares his tip for setting up the command prompt to reflect a remote path. ...

Understanding File-Size Limits on NTFS and FAT

A general confusion about files sizes on FAT seems to stem from FAT32's file-size limit of 4GB and partition-size limit of 2TB. ...


Related Events WinConnections and Microsoft® Exchange Connections

Deep Dive into Windows Server 2008 R2 presented by John Savill

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

A Guide to Windows Certification and Public Keys

SQL Server Administration for Oracle DBAs

Related Windows OSs Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement