Solved

remote desktop services RemoteApp error on some users after licensing Remote Desktop Services

Posted on 2014-11-13
2
511 Views
Last Modified: 2014-11-15
Prior to purchasing licenses for Remote Desktop Services (server 2008 R2) we tested an application using the "create windows installer" function in Remote Desktop Services .  All worked fine.  Now that we have purchased and installed Remote Desktop Services licenses, the app fails to open for some users.  The trouble follows the user, not the workstation.

The one and only server acts as both Domain Controller and Remote Desktop Services.



When opening the RemoteApp, the server records the following error for the failing users:

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          11/13/2014 10:35:22 PM
Event ID:      4105
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server1.xxxxxx.local
Description:
The Remote Desktop license server cannot update the license attributes for user "username" in the Active Directory Domain "xxxxxx.local". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "xxxxxx.local".
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
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-Licensing" Guid="{4D99F017-0EB1-4B52-8419-14AEBD13D770}" EventSourceName="TermServLicensing" />
    <EventID Qualifiers="51456">4105</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-14T05:35:22.000000000Z" />
    <EventRecordID>23891</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>server1.xxxxxx.local</Computer>
    <Security />
  </System>
  <UserData>
    <EventXML xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="Event_NS">
      <param1>rana</param1>
      <param2>xxxxxx.local</param2>
      <param3>0x80070005</param3>
    </EventXML>
  </UserData>
</Event>

Open in new window


I have verified the membership of the DC is a member of the TS Group and Network Service is also a member, and restarted the services.

What completely baffles me is that it works fine on all workstations for one of the users, and not for the other four users on any workstation.

The users are all members of the same 3 groups - Domain Users, Office Staff, and Remote Desktop Users.
0
Comment
Question by:leonvan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 15

Accepted Solution

by:
joharder earned 500 total points
ID: 40443872
It sounds like the licensing info in the registry may not have updated properly.  Please see http://support.microsoft.com/kb/187614.
0
 

Author Closing Comment

by:leonvan
ID: 40444684
For future readers, the server also needed to be rebooted.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question