She remote sessions as server and then after a couple of seconds gets booted out, with this error found in the computer log:

'The Remote Desktop license server cannot update the license attributes for user "danielle.eglin" in the Active Directory Domain "adsnet.pri". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "adsnet.pri".

If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.

If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.

Win32 error code: 0x80070005'

Looked on google but some instructions suggested werent clear, may refer to no licences left ?

Dani AI

Generated

The event you posted maps to the well-known Event ID 4105 (Win32 0x80070005) — it usually means the RD Licensing service is being denied permission to write per-user licensing attributes in Active Directory, not that you necessarily ran out of CALs. Microsoft documents the causes (group membership, missing DACL rights on user objects after older schema upgrades) and the supported fixes. (learn.microsoft.com)

If basic checks (license server is activated, RD Licensing service running, and the server is in the domain) do not fix it, the most common remediation is to give the Terminal Server License Servers group the correct write permission on user objects. Do that either with the Active Directory Users and Computers "Delegate Control" wizard (choose a custom task on User objects and grant the Read and Write Terminal Server license server permission) or with dsacls. Examples (replace the DN placeholders with your domain/OU and run from a domain admin session):

dsacls "CN=jsmith,OU=Users,DC=contoso,DC=local" /G "BUILTIN\Terminal Server License Servers:WPRP;terminalServer"

dsacls "OU=Users,DC=contoso,DC=local" /I:S /G "BUILTIN\Terminal Server License Servers:WPRP;Terminal Server License Server;user"

Those command forms are documented by Microsoft and are the supported approach when the Terminal Server License Servers group exists but lacks the needed DACL rights. After changing permissions, restart the Remote Desktop Licensing service. (learn.microsoft.com)

Because already suggested checking the license server membership, tie that in: if membership and activation are OK but the error persists, apply the AD permission fix above. Since resolved things by switching PCs, also verify client-side causes before doing server changes: test the problematic user from another client, test another user from the same client, check local firewall/AV, RDP client version, and confirm AD replication is healthy (replication latency can leave attributes out of sync). If the problem continues, collect the Event ID 4105 entries and licensing logs before escalating to Microsoft support.

Recommended Answers

All 2 Replies

Have you ensured that your terminal server(s) are part of the group "Terminal server License Servers"?

If so, yes, you can check the available licenses by launcing the License Manager from the Admin tools. I assume that you installed the appropriate licenses? Terminal services in application mode does require additional licenses.

If you are only interested in RDP for two connections, you do not require a full installation of Terminal Services. You can just enable RDP administration.

I ended up switching PC's, as we went through all options possible. thanks anyway.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.