This is a four-part article I wrote for MSTerminalServices.org last year. Parts one and two focus on common server-related licensing issues. Part three covers more obscure server-related issues such as corrupt license server databases and activation issues. Part four looks at licensing-related issues from the client side.

The flow of this article series works best when read as one document, but the publishing guidelines for MSTerminalServices.org place restrictions on the length of a particular article, which is why they end up broken into several segments. The links to all four segments are below:

• Troubleshooting Terminal Server Licensing Issues (Part 1)
• Troubleshooting Terminal Server Licensing Issues (Part 2)
• Troubleshooting Terminal Server Licensing Issues (Part 3)
• Troubleshooting Terminal Server Licensing Issues (Part 4)

This two-part article that I wrote for MSTerminalServices.org discusses providing redundancy and high-availability for your Terminal Server License Servers.  Part one focuses on establishing redundancy for the licensing infrastructure while part two covers ensuring you have easy recovery in the event of a license server failure.  Both segments are available at the following links:

• Terminal Services License Server High-Availability and Recovery (Part 1)
• Terminal Services License Server High-Availability and Recovery (Part 2)
  

This is another article that I wrote for MSTerminalServices.org detailing the license server discovery process.  I have noticed through numerous forum posts that many administrators are still puzzled as to why their license servers are not found by terminal servers in their environment.  Part one describes the available roles for your license server and how the discovery process differs based on the role selected, including detailed flowcharts.  Part two offers advice on better-controlling the process and some troubleshooting tips when things don't go as planned.

• Terminal Services Discovery Process - Part 1
• Terminal Services Discovery Process - Part 2
  

In this two-part article that I wrote for MSTerminalServices.org, I cover the details of how the Terminal Services CAL allocation process functions in both per-device and per-user terminal server modes.  Part one covers the overview of CAL types and server licensing modes, while part two details the step-by-step process for allocating CALs, including in-depth flowcharts.  Check it out over on MSTerminalServices.org.

• Terminal Services CAL Allocation Process - Part 1
• Terminal Services CAL Allocation Process - Part 2
  

As I said before, I have been doing a lot of writing for msterminalservices.org.  I figured it was time for me to do some "cross promoting", or rather just let everyone know that these articles exist, so I will be linking to all of them as I go.

This article delves into using Windows Performance Monitor (or PerfMon) to create a baseline of your terminal servers/Citrix servers to refer back to when performance problems arise.  Too often, performance problems can be difficult to diagnose when issues crop up because no one bothered to examine what the performance stats looked like when things were running normally.  In this two-part article, you'll which counters are important and what they mean.

• Using Windows Performance Monitor to Baseline a Terminal Server (Part 1)
• Using Windows Performance Monitor to Baseline a Terminal Server (Part 2)