2019 CAL User License Duplicates based upon case sensitivity

Question

Problem already mentioned in now dead forums...
The proposed solution (rebuilding the database) does not work

I have two CAL licences servers. My RDS servers refers to them through GPO.

The first one is loaded by duplicates base on case sensitivity.

Instead of rebuilding the database, I switched servers in the GPO. So the server with an empty database is now used.
Same problem.

Still no patch for that problem ?
I mean, I won't spend time to start rebuilding things for a problem that seems to be so simple to fix at Microsoft.
If Microsoft doesn't car about licensing accuracy, I won't either.

Answer 1

Hi, how are you doing?

Answer 2

Hi, haven't received your message a few days, was your issue resolved?

Answer 3

As far as I know, this can be happen if the license attributes are not able to be updated on the user account object due to lack of permission. What I would recommend is to first grant the necessary permissions in AD, and then you can rebuild the database to clean things up. When things are working properly, if a user logs on you should see their license issued as you do now in RD Licensing Manager, and you should see the RD licensing attributes on their user account object. You may use AD Users & Computers -- View Advanced Features -- right-click on the user -- Attributes tab -- look for several msTS* attributes such as msTSExpireDate, msTSManagingLS, etc. If these are blank and the user shows up in RD Licensing Manager it is likely the permissions issue. You can grant the permissions using Active Directory Users and Computers using below basic steps: 1. On the OU that contains your users, right-click and choose Delegate Control... , follow wizard![91622-annotation-2021-04-27-125948.png][1] 2. On Users and Groups page, click Add and then enter “SELF” ![91631-self.png][2] 3. On Tasks to Delegate page, select Create a custom task to delegate![91603-create-a-custom-task.png][3] 4. On Active Directory Object Type page select Only the following objects in the folder, then scroll down and select User objects![91614-user-objects.png][4] 5. On Permissions page, select General, then scroll down and select Read and write Terminal Server license server![91535-read-and-write-terminal-server-license-server.png][5]![91641-image.png][6] 6. Once you have updated the permissions, please log on with a user account that doesn't have their licensing attributes populated and then check after successfully logged on that the attributes now have values. In the meantime, please leave a description of your RDS deployments which will help me to involve what happened. If the answer is helpful, please click "Accept Answer" and upvote it. Best Regards [1]: /api/attachments/91622-annotation-2021-04-27-125948.png?platform=QnA [2]: /api/attachments/91631-self.png?platform=QnA [3]: /api/attachments/91603-create-a-custom-task.png?platform=QnA [4]: /api/attachments/91614-user-objects.png?platform=QnA [5]: /api/attachments/91535-read-and-write-terminal-server-license-server.png?platform=QnA [6]: /api/attachments/91641-image.png?platform=QnA