TS License Server Discovery Part 2
Friday, 30 June 2006 by Michel Roth
This is an article by Rob Leitman,a member on the Microsoft Terminal Services team. he talks about the evolution of license Server discovery. This part discusses Windows 2003 and beyond.

Windows 2003
With Win2003, it was pretty easy for us to get started. We fixed the registry-based discovery to allow multiple license servers and to be applied in the admin tools too.

We also reduced network traffic a few ways:
1. First check the registry – if we’ve been told what LS to use, why look anywhere else?
2. Next try discovery via Active Directory – one LDAP query is faster than many RPCs to domain controllers.
3. For Domain discovery, first try local (on-site) DCs. Only if everything else fails should we try contacting off-site DCs.
4. Stop the discovery process as soon as we find the first LS. Don’t do any further discovery unless the LS we’ve found is no longer available.

Finally, we allowed LSs to be installed on any server, not just DCs.
Windows 2003 SP1

After Win2003 shipped we had some time to sit down and look at customer data, to try to fix the top issues that were causing customers to have to call in.

Read it all here.

Related Items:

Microsoft Terminal Services Team On TS Licensing Discovery (28 June 2006)
Terminal Server License Service Discovery – Part 1: This Discovery Process (28 March 2007)
Terminal Server License Service Discovery Part 2 (19 April 2007)
Manually Publishing And Un-publishing Terminal Server License Servers (28 February 2007)
Control the Issuance of RDS CALs (18 September 2009)
Resources For diagnosing TS Licensing Problems (16 February 2007)
Microsoft Windows Server 2000/2003 Terminal Services Management Pack (1 May 2007)
Provision NetworksVirtual Access Suite 5.8 (3 April 2007)
Hyperic Delivers Open Source Management Solution for VMware (19 December 2006)
What’s new In Terminal Services Licensing for Longhorn? (Part 3) (19 April 2007)
Comments (0)