Resources For diagnosing TS Licensing Problems
Friday, 16 February 2007 by Michel Roth
The Terminal Services Team has written an article which summarizes the most common problem areas in the ever elusive landscape of Terminal Server licensing. I for one can't wait until Longhorn Terminal Server adds User TSCal tracking. That should make it even more fun.

"If you have deployed Terminal Server Licensing and are running into any issues with it, most likely they will be due to Client connection failures, license server activation failures, license issuance and upgrade problems. In this article, we discuss some of the categories of problems that could occur in your Windows Server 2003 Terminal Services deployment, and how you can diagnose or fix them. Some of the categories of problems that could occur in your Windows Server 2003 Terminal Services deployment are

1. Discovery Problems
2. Mode-mismatch Problems
3. Monitoring CALs
4. CAL Migration
5. Setting up for redundancy and fallback
6. Restricting which TSes can get a License from this License Server

Read it here.

Related Items:

What’s New In Terminal Services Licensing For Longhorn? (Part 4) (24 April 2007)
What’s new In Terminal Services Licensing for Longhorn? (Part 3) (19 April 2007)
Manually Publishing And Un-publishing Terminal Server License Servers (28 February 2007)
Tracking User TSCALS in Windows 2008 (7 August 2007)
What’s new in Terminal Services Licensing for Longhorn? (Part 5) (2 May 2007)
What’s New In Terminal Services Licensing For Longhorn? (5 April 2007)
What’s new in Terminal Services Licensing for Longhorn? (Part 2) (12 April 2007)
Control the Issuance of RDS CALs (18 September 2009)
Requesting Longhorn Beta TSCALs (10 May 2007)
Terminal Services License Server High-Availability and Recovery (Part I) (6 June 2007)
Comments (0)
Show/Hide comment form