RD Licensing Manager Report resets license usage

Question

I'm experiencing this same problem with a 2019 RDS licensing server. As soon as you attempt to run a licensing report, all used CALs are reset to 0. Call me crazy, but I'm not a huge fan of changing AD permissions on all users in the directory without a little more information. Does anyone know why this is required and if it is a sanctioned Microsoft fix? This seems like a bug.

https://learn.microsoft.com/en-us/answers/questions/294955/rd-licensing-manager-shows-an-empty-report.html

Article suggests the following fix.
-On the OU that contains your users, right-click and choose Delegate Control... , follow wizard
-On Users and Groups page, click Add and then enter SELF
-On Tasks to Delegate page, select Create a custom task to delegate
-On Active Directory Object Type page select Only the following objects in the folder, then scroll down and select User objects
-On Permissions page, select General, then scroll down and select Read and write Terminal Server license server

Where other suggestions failed... For example this "tail chasing" advice.....
@Carl Fan
"In general ,I consider that the issue need to stop remote desktop licensing service and delete the "C:\Windows\System32\Lserver" folder, uninstall the RDS roles, reboot, and reinstall the RDS Licensing role. activate rdls server and reinstall rds cals again.
To immediately clear things out you could wipe the licensing database and reinstall your RDS CALs fresh
Before doing this please make sure you have the original license information
In RD Licensing Manager, Activate your server, and Install your licenses. If it blocks you from installing your licenses you may need to call the Clearinghouse, explain that you rebuilt the database due to corruption and they will assist in re-installing licenses.
I found you have rebuild the license server and service. Try to delete the Lserver folder to check.
Also you mentioned that the issue was occurred on multiple 2019 servers. So I suggest that you could check for update firstly. If any security update could be found, installing them then reinstall the licensing server to check."

Answer 1

Hello,

Does the licensing diagnoser show any issues?

RD Licensing Diagnoser to check for issues
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/cannot-connect-rds-no-license-server#extra1

You need to make sure the diagnoser shows no issues and shows all the correct information especially at the bottom where it lists the licensing server.

Also what could be connected if by any chance you did change the IP address on the machine which has the licensing manager?
Not sure if that is your problem but double check to make sure you have it set.

---------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Hello,

I have the exact same problem/behaviour in my Windows Server 2019 RDS Farm.

Everything is well configured, as soon as I attempt to generate a report, the licenses get reset (available/issued).

Has anyone figured a fix for this ? I also don't think it is a permission issues, since the list of issued get filled correctly and the report is generated (but empty), seems like a bug to me.

I only see this event after attempting to generate the report and it clearly shows the wrong values :

Answer 3

Hi,

Did you end up finding a fix? We have the same issue on a server 2019 VM. I tried the fix mentioned in the post linked in the OP and it did not work for us.

Regards,

Answer 4

Hello
I have the same issue, and even with the "Refresh" on the licence clear all Issued CAL
if I do "Refresh" on the server, it just refresh the count, but if I do Refresh on the licence itself, all the Issued CAL are cleared!

I did a report, it only reported data up to march 30 2022 (I'm on december 29 2022 as I write this) and I lost all the data, just when my client asked me a status of the licence consumption by users.. damn

also using Windows 2019, updated every month, and no error/problem in the logs or diagnostics I could find.

and the "Operational" Log is only 1MB so I just have 2 days of history. if you plan on using this log to get historical data, I suggest you increase its size ASAP

Answer 5

I have seen the issue also on Windows Server 2022. Did anyone fix this issue without modifying a lot of permissions in AD?

I agree with AdamTyler-3751 that this seems like a bug and also would like to get some additional information about why this manual intervention is required to get licensing reports working again.