Home licensing software licensing terminal services windows server

Streamline Licensing: Transfer Terminal Services CALs in Windows Server Effectively

Updated: • 0 • min read
Table of Contents

Moving Terminal Services Client Access Licenses (CALs) between license servers in a Windows Server environment is a crucial task for maintaining efficient and compliant remote desktop services. This process, while seemingly straightforward, requires careful execution to avoid licensing discrepancies and ensure uninterrupted access for users. Understanding the proper procedures for transferring CALs is essential for system administrators managing terminal services deployments. This article outlines the necessary steps and considerations for effectively moving Terminal Services CALs from one license server to another within your Windows Server infrastructure.

Understanding Terminal Services CALs

Client Access Licenses (CALs) are fundamental to the Microsoft server licensing model. They grant users and devices the legal right to access the services of a Windows Server. In the context of Terminal Services, now known as Remote Desktop Services (RDS), CALs are specifically required for users or devices connecting to the RDS server to access remote applications or desktops. Without valid CALs, users will not be able to connect to the RDS server, hindering productivity and potentially violating licensing agreements.

There are two primary types of RDS CALs:

  • Per-Device CALs: These licenses are assigned to a specific device, allowing any user to access the RDS server from that device. Per-device CALs are typically more cost-effective when multiple users share the same devices to access RDS.

  • Per-User CALs: These licenses are assigned to a specific user, allowing that user to access the RDS server from any device. Per-user CALs are generally preferred when users access RDS from multiple devices, such as a desktop at work and a laptop at home.

When migrating or upgrading server infrastructure, or when load balancing requirements change, administrators may need to transfer RDS CALs from one license server to another. This ensures that the licenses remain valid and accessible within the updated environment. Improperly managed CAL transfers can lead to licensing issues, including grace period expirations and potential service disruptions.

Understanding Terminal Services CALs

Prerequisites for CAL Transfer

Before initiating the transfer of Terminal Services CALs, it’s imperative to gather all necessary documentation and information. This preparation is crucial for a smooth and successful transfer process. Failing to have these documents readily available can lead to delays and complications during the license transfer procedure.

Essential Documents

The most critical document required for transferring CALs is the paper agreement received upon purchasing the licenses. This agreement contains vital information, specifically the agreement number or the enrollment number. This number is essential when contacting the Microsoft Clearinghouse to obtain the new CAL Key Pack ID, which is necessary to install the licenses on the new license server. Without this agreement number or enrollment number, the license transfer process cannot proceed.

It is highly recommended to locate and securely store this agreement document before starting the CAL transfer. Digital copies or scans of the agreement should also be kept as backups in case the physical document is misplaced or damaged. Having this information readily available will significantly expedite the transfer process and minimize potential issues.

Pre-Transfer Checklist

In addition to the agreement document, consider the following checklist before initiating the transfer:

  • Identify Source and Destination License Servers: Clearly determine the old license server (source) from which CALs are being moved and the new license server (destination) where CALs will be installed. Note down their server names and IP addresses for easy reference.
  • Verify License Server Roles: Ensure that both the source and destination servers are properly configured as Terminal Services (Remote Desktop Services) License Servers.
  • Administrative Privileges: Confirm that you have administrative privileges on both the source and destination license servers. This is necessary to perform the required licensing management tasks.
  • Network Connectivity: Verify that both license servers have network connectivity and can communicate with each other and with the internet (or Microsoft Clearinghouse, if online activation is used initially).
  • Backup Existing License Server (Optional but Recommended): Before making any changes to the source license server, consider performing a backup of its system state and licensing database. This provides a safety net in case of unexpected issues during the transfer process.

By meticulously preparing and gathering all necessary documents and verifying the pre-transfer checklist items, administrators can significantly reduce the risk of errors and ensure a more efficient and trouble-free CAL transfer process.

Step-by-Step Guide to Moving Terminal Services CALs

Transferring Terminal Services CALs requires a systematic approach. The following steps outline the procedure for moving CALs from an old license server to a new one. It is crucial to follow these steps in order to ensure a successful and compliant transfer.

Step 1: Install Terminal Services Licensing on the Target Server

The first step is to install the Remote Desktop Services Licensing role on the new server that will act as the license server. This can be done through the Server Manager.

  1. Open Server Manager on the target server.
  2. Click Add roles and features.
  3. Select Role-based or feature-based installation and click Next.
  4. Select the target server from the server pool and click Next.
  5. In the Server Roles list, select Remote Desktop Services and click Next.
  6. Click Next through the Features page.
  7. In the Role Services page, select Remote Desktop Licensing.
  8. Click Add Features when prompted.
  9. Click Next and then Install to begin the installation process.
  10. Click Close once the installation is complete.

Step 2: Activate the License Server

After installing the licensing role, the next step is to activate the license server. Activation associates the license server with Microsoft and prepares it to manage RDS CALs.

  1. Open Server Manager and click Tools, then select Remote Desktop Services, and then Remote Desktop Licensing Manager.
  2. In the RD Licensing Manager, right-click the license server name and select Activate Server.
  3. The Activate Server Wizard will appear. Click Next.
  4. Choose a connection method for activation. The recommended method is Automatic connection (recommended) if the server has internet access. If not, you can use Telephone or Web Browser.
  5. Follow the wizard prompts to complete the activation process based on your chosen connection method. For telephone activation, you will need to call the Microsoft Clearinghouse.

Step 3: Configure Installation Method to Telephone

For the CAL transfer process, it’s necessary to configure the installation method on the new license server to Telephone. This is because the transfer typically involves obtaining a CAL Key Pack ID via phone from the Microsoft Clearinghouse.

  1. In the Remote Desktop Licensing Manager, right-click the license server name and select Properties.
  2. In the Installation method list, select Telephone.
  3. Click OK.

Step 4: Initiate the Install Licenses Wizard

Now, you are ready to start the process of installing the transferred CALs. This is done through the Install Licenses Wizard.

  1. In the Remote Desktop Licensing Manager, right-click the license server name and select Install Licenses.
  2. The Welcome to the Install Licenses Wizard dialog box will appear. Click Next.

Step 5: Obtain License Server ID

The wizard will display the License Server ID. This ID is crucial for contacting the Microsoft Clearinghouse to obtain the CAL Key Pack ID. Note down this License Server ID.

Step 6: Contact Microsoft Clearinghouse or Use Web Activation

To obtain the CAL Key Pack ID, you need to contact the Microsoft Clearinghouse. The wizard may provide a phone number to call. Alternatively, you might be directed to a Microsoft website (like the Remote Desktop Services activation website) to perform the activation online, depending on the specific circumstances and licensing program.

  • Telephone Activation: Call the Microsoft Clearinghouse number provided in the wizard or in Microsoft documentation. You will need to provide the License Server ID obtained in the previous step and the agreement number or enrollment number from your licensing agreement. The representative will then provide you with a CAL Key Pack ID.
  • Web Activation: If directed to a website, follow the online prompts. You will likely need to enter the License Server ID and your licensing agreement information on the website. The website will then generate a CAL Key Pack ID.

Step 7: Enter the CAL Key Pack ID

Once you have obtained the CAL Key Pack ID from the Microsoft Clearinghouse or the website, enter it into the Install Licenses Wizard.

  1. In the Obtain Client License Key Pack dialog box of the Install Licenses Wizard, type the CAL Key Pack ID in the provided fields.
  2. Click Next.

Step 8: Verify Successful CAL Installation

After entering the CAL Key Pack ID, the wizard will process the information and install the licenses. You should receive a confirmation message indicating that the CALs have been installed successfully.

Step 9: Deactivate the Old License Server

After confirming that the new license server is functioning correctly and issuing licenses, it is crucial to deactivate the old license server. This prevents licensing conflicts and ensures compliance. Deactivation typically involves uninstalling the Remote Desktop Licensing role service from the old server.

  1. Open Server Manager on the old license server.
  2. Click Manage and then Remove Roles and Features.
  3. Select the server and click Next.
  4. In the Server Roles list, uncheck Remote Desktop Services.
  5. Click Remove Features when prompted to remove dependent features.
  6. Click Next and then Remove to uninstall the Remote Desktop Licensing role service.
  7. Click Close once the uninstallation is complete.

By following these steps meticulously, you can successfully move Terminal Services CALs to a new license server, ensuring continued access to remote desktop services and maintaining licensing compliance within your Windows Server environment.

Step-by-Step CAL Transfer

Best Practices for Backup and License Information Management

Maintaining the integrity and availability of your Terminal Services licensing data is paramount. Regular backups and proper management of license information are essential for preventing data loss and ensuring smooth operation of your RDS infrastructure.

Regular Backups

Implementing a routine backup schedule for your Terminal Services license server is a critical best practice. Backups protect against data loss due to hardware failures, storage corruption, or accidental system errors. Windows Server provides built-in tools like Windows Server Backup that can be used for this purpose.

When backing up a Terminal Services license server, it is imperative to back up both:

  • System State Data: This includes the operating system configuration, registry settings, and crucial system files. The licensing configuration is deeply integrated with the system state.
  • Terminal Services License Server Database Folder: This folder contains the database where the actual license information is stored. The default location of this database folder should be included in your backup scope.

By backing up both the system state and the database folder, you ensure that all critical licensing data is captured and can be restored in case of a disaster. The frequency of backups should be determined based on your organization’s recovery point objectives (RPO) and data change rate. Daily backups are generally recommended for production environments.

License Restoration Scenarios

Understanding license restoration scenarios is crucial for disaster recovery planning. The behavior of license restoration depends on whether the operating system on the license server has been replaced.

  • Restoring to the Original Server (No OS Replacement): If you restore the system state data and the database to the original Terminal Services license server without replacing the operating system, any unissued licenses will be restored correctly. The system will recognize its identity and reinstate the licenses.

  • Restoring to a Different Server or After OS Replacement: If you restore the system state and database to a different server, or if you have replaced the operating system on the original server, the unissued licenses may not be automatically restored. In such cases, an event will be logged in the System log indicating the unissued license count. However, you can still restore these unissued licenses by using the telephone activation option in the Remote Desktop Licensing Manager tool. By switching to telephone activation and contacting the Microsoft Clearinghouse, you can reactivate and restore the licenses on the restored server.

Proactive License Management

Beyond backups, proactive license management involves:

  • License Tracking: Maintain a clear record of all purchased RDS CALs, including the agreement numbers, quantities, and license types (Per-Device or Per-User).
  • License Monitoring: Regularly monitor the license usage on your RDS license servers to ensure you have sufficient licenses and to proactively identify any potential licensing shortages. The Remote Desktop Licensing Manager provides tools for monitoring license usage.
  • Periodic Audits: Conduct periodic internal audits of your RDS licensing to verify compliance and identify any discrepancies.

By implementing these backup and license management best practices, organizations can safeguard their RDS investments, minimize the risk of licensing issues, and ensure the continuous availability of remote desktop services for their users.

Do you have any questions about transferring Terminal Services CALs or managing your Windows Server licensing? Feel free to leave a comment below!

Post a Comment