RDS CAL license showing already activated

Question

RDS CAL license showing already activated

Hans Ramiah 20

I am currently running Azure Virtual Desktop on Windows Server 2019 Datacenter since November 2024. The RDS stopped working and we found out that the RDS Cal License wasnt setup. We ordered new RDS CAL Licenses last week and while trying to activate same, the server run into some bug. We restored a previous image and only to find out that the newly purchased license was already activated. I guess the bug encountered activated the license and am no longer able to use the same key to activate the RDS CAL Licenses for my user. How can i resolve this?

Nikhil Duserla 6,630 Reputation points Microsoft External Staff

2025-03-31T10:55:40.29+00:00

Hi @Hans Ramiah ,

Could you please confirm if the VM is in a running state and if you are unable to access it?

Also, let me know if you activated the CAL license earlier or if it is still yet to be activated.

I would recommend taking this discussion to a private message for a more detailed conversation.

Thank you!
Hans Ramiah 20 Reputation points

2025-03-31T13:33:57.8033333+00:00

@Alex Burlachenko Since the setup was done during initial deployment, the roles/features were pre-installed by Microsoft Azure and was done via role-based and not RDS intallation. So am unable to use the command you mentioned.
Nikhil Duserla 6,630 Reputation points Microsoft External Staff

2025-03-31T16:17:25.9866667+00:00

Hi @Hans Ramiah,

Make sure that all the remote desktop servers have the latest updates installed.

Check the status of the Remote Desktop Licensing service. If the service isn't running, start it.

Make sure that the versions of the client access licenses (CALs) that you're using are compatible with both your RD Session Host versions and your RD Licensing server versions. For more information, see License your RDS deployment with client access licenses (CALs): RDS CAL version compatibility.

If you have any further queries, do let us know.
Hans Ramiah 20 Reputation points

2025-04-02T04:56:02.76+00:00

Dear All,

I managed to sort this out. In fact, I found a forum https://dae.me/blog/2533/windows-server-2019-remote-desktop-license-issue-with-user-cals/ that explained the issue.

From my understanding, I had to use device CAL instead of user CAL. From what is on the forum, the user CAL requires AD.

Thank you all for the support.

Accepted answer

1 additional answer

Your answer

Nikhil Duserla 6,630 Reputation points Microsoft External Staff

2025-03-31T10:55:40.29+00:00

Hi @Hans Ramiah ,

Could you please confirm if the VM is in a running state and if you are unable to access it?

Also, let me know if you activated the CAL license earlier or if it is still yet to be activated.

I would recommend taking this discussion to a private message for a more detailed conversation.

Thank you!
Hans Ramiah 20 Reputation points

2025-03-31T13:33:57.8033333+00:00

@Alex Burlachenko Since the setup was done during initial deployment, the roles/features were pre-installed by Microsoft Azure and was done via role-based and not RDS intallation. So am unable to use the command you mentioned.
Nikhil Duserla 6,630 Reputation points Microsoft External Staff

2025-03-31T16:17:25.9866667+00:00

Hi @Hans Ramiah,

Make sure that all the remote desktop servers have the latest updates installed.

Check the status of the Remote Desktop Licensing service. If the service isn't running, start it.

Make sure that the versions of the client access licenses (CALs) that you're using are compatible with both your RD Session Host versions and your RD Licensing server versions. For more information, see License your RDS deployment with client access licenses (CALs): RDS CAL version compatibility.

If you have any further queries, do let us know.
Hans Ramiah 20 Reputation points

2025-04-02T04:56:02.76+00:00

Dear All,

I managed to sort this out. In fact, I found a forum https://dae.me/blog/2533/windows-server-2019-remote-desktop-license-issue-with-user-cals/ that explained the issue.

From my understanding, I had to use device CAL instead of user CAL. From what is on the forum, the user CAL requires AD.

Thank you all for the support.

Answer 1

Hi @Hans Ramiah,

Good catch! Glad the issue is resolved for you finally. I will have this answer promoted by reposting it. As an Original Poster will not be able to accept your own answer. This is in the attempt to help others looking for a solution for a similar issue.

Answered by Hans Ramiah

I managed to sort this out. In fact, I found a forum https://dae.me/blog/2533/windows-server-2019-remote-desktop-license-issue-with-user-cals/ that explained the issue. From my understanding, I had to use device CAL instead of user CAL. From what is on the forum, the user CAL requires AD.

Thanks again for sharing the solution here. Have a good day!

User's image

Answer 2

Dear Hans,

Thank you for detailing your RDS CAL licensing issue heres at Q&A portal. First, confirm the license status by running

Get-RDLicenseConfiguration

Check activation history with

Get-WinEvent -LogName Microsoft-Windows-TerminalServices-Licensing/Operational

If your license server is accessible open Remote Desktop Licensing Manager. Right-click the server > Review Configuration, Navigate to Install Licenses to verify your CALs. If duplicates appear, rightclick > Deactivate License

If you dont implement regular license server backups it is good time to do that

wbadmin start backup -backupTarget:\backupserver\rdlicensing -include:C:\Windows\System32\LServer

Consider Azure-native Windows 10/11 Multi-user licensing to avoid CAL management you can temporarily (for up to 90 days) set the grace period

Set-RDLicenseConfiguration -Mode 2

Monitor remaining time (days)

(Get-WmiObject -Namespace root\cimv2\TerminalServices -Class Win32_TerminalServiceSetting).GracePeriodDays

Best regards,

Alex

P.S. If my answer help to you, please Accept my answer

Share via

RDS CAL license showing already activated

1 additional answer

Your answer