While doing to some simple trouble shooting on what I thought would be a walk in the park, I ran into a few problems trying to update the terminal server license attributes for user.  My users were constantly getting an error 4105 (see below; Event Details).

After some digging, I ran across a very helpful Windows Server form (<a href="http://technet.microsoft.com/en-us/library/cc775179(v=ws.10).aspx">http://technet.microsoft.com/en-us/library/cc775179(v=ws.10).aspx</a>). Once the steps were correctly implemented and the restarting of the services, still no fix. Long story short, I later realized that this helpful form was missing a few important steps.

Event Details
<table border="0" cellpadding="0">
<tbody>
<tr>
<td><strong>Product:</strong></td>
<td>Windows Operating System</td>
</tr>
<tr>
<td><strong>ID:</strong></td>
<td>4105</td>
</tr>
<tr>
<td><strong>Source:</strong></td>
<td>Microsoft-Windows-TerminalServices-Licensing</td>
</tr>
<tr>
<td><strong>Version:</strong></td>
<td>6.0</td>
</tr>
<tr>
<td><strong>Symbolic Name:</strong></td>
<td>TLS_W_PU_AD_UPDATE</td>
</tr>
<tr>
<td><strong>Message:</strong></td>
<td>The Terminal Services license   server cannot update the license attributes for user "%1!s!" in the   Active Directory Domain "%2!s!". Ensure that the computer account   for the license server is a member of Terminal Server License Servers group   in Active Directory domain "%2!s!".
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 Terminal Services Licensing service to track or report   the usage of TS Per User CALs.
Win32 error code: %3!s!</td>
</tr>
</tbody>
</table>
<!--more-->

<strong>Resolve</strong>
<ul>
	<li>Add the license server to the Terminal Server License Servers group and restart the Terminal Services Licensing service</li>
</ul>
<strong>To resolve this issue, do the following:</strong>
<ul>
	<li>Add the computer account for the license server to the Terminal Server License Servers group in Active Directory Domain Services (AD DS).</li>
	<li>Restart the Terminal Services Licensing service on the Terminal Services license server.</li>
</ul>
<em>To perform these tasks, refer to the following sections.</em>

<strong>Note:</strong>  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.

<strong>Add the computer account by using Active Directory Users and Computers</strong>
<ul>
	<li>To perform this procedure, you must have membership in the Domain Admins group in AD DS, or you must have been delegated the appropriate authority.</li>
</ul>
<strong>To add the account to the group:</strong>
<ol>
	<li>Open Active Directory Users and Computers. To open Active Directory Users and Computers, log on to a computer where Active Directory Users and Computers is installed (for example, an AD DS domain controller), click Start, click Run, type dsa.msc, and then click OK.</li>
	<li>If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.</li>
	<li>Locate the Terminal Server License Servers group. By default, the Terminal Server License Servers group is located in the Builtin container.</li>
	<li>Right-click Terminal Server License Servers and then click Properties.</li>
	<li>On the Members tab, click Add.</li>
	<li>Click Object Types, select the Computers check box, and then click OK.</li>
	<li>In the Enter the object name to select box, type the name of the license server that you want to add to the Terminal Server License Servers group. If the license server is installed on a domain controller, add the Network Service account.</li>
	<li>Click OK, and then click OK.</li>
</ol>
<strong>To add new ACL to the root to allow the Terminal Server License Servers to read and write the following properties for all users in the domain:</strong>
<ol>
	<li>Right-click on the root of the domain and choose Properties and check out the security tab.</li>
	<li>Select the read and write permissions box for the following:</li>
<ol>
	<li>Read msTSExpireDate</li>
	<li>Write msTSExpireDate</li>
	<li>Read msTSLicenseVersion</li>
	<li>Write msTSLicenseVersion</li>
	<li>Make sure each user “Include inheritable permissions from this object’s parent” property checked.</li>
<ol>
	<li>(View -&gt; Advanced Features then right-click on user -&gt; Properties -&gt; Security tab -&gt; Advanced -&gt; “Include inheritable …” checkbox on the lower left)</li>
</ol>
</ol>
</ol>
<strong>Restart the Terminal Services Licensing service on the license server.</strong>

To restart the Terminal Services Licensing service, see the section titled "Restart the Terminal Services Licensing service." Refer to link for the correct steps to restart the Terminal Services Licensing Service. <a href="http://technet.microsoft.com/en-us/library/cc775179(v=ws.10).aspx">http://technet.microsoft.com/en-us/library/cc775179(v=ws.10).aspx</a>

Please test by having a standard user logon to your RDS.  After the user has logged on, check the event logs of the server, there should not be an event id 4105 Warning for the user in the System log, and there should be an event id 4143 Information entry for the user under Microsoft-Windows-TerminalServices-Licensing/Admin log.