Resolution For Terminal Services Event ID 4105

Table of Contents

Occasionally, you might see a Terminal Services event ID 4105 message on your computer. There are a number of possible causes for this problem.

Approved

1. Download ASR Pro

2. Open the program and select "Scan your computer"

3. Click "Repair" to start the repair process

The software to fix your PC is just a click away - download it now.

This article covers a single target solution ID 4105 that is used on a mobile computer with a Remote Desktop license (Remote Desktop License).

Applies to: Windows Server 2009 R2
Part number: KB 2030310

Symptoms

The following warning may appear on a computer running a Remote Desktop license (formerly Terminal Services (TS) license).

Protocol name: system
Source: Microsoft-Windows-TerminalServices-Licensing
Event ID: 4105
Level: Warning
User: N / A
Computer:
Description:
Terminal Services Licensing typically cannot update the server license attributes for user through the Active Directory domain . Verify that the computer card for the server license is a member of the Terminal Server Licensing Servers group in the Active Directory space.
Often when the server license is on a domain controller, the accountThe network service must also be a member of the Terminal Server License Servers group.
If the licensing computer is installed on a domain controller, after adding the correct account type to the Terminal Server Licensing Server group, you will need to restart this Terminal Server Licensing service to validate or report use of TS CALs for each user.
Win32 error code: 0x80070005

Reason

Error ID 4105 can be filled for one of the following reasons:

The license server is not subscribed to the Terminal Server license server in the domain group that contains the users.
The license server is considered installed on the domain controller, and the Network Service account is no longer a member of the Terminal Server License Server group.
If user addresses existed before the domain was upgraded to Windows Server 2003, the Terminal Server License Server group may not be in the Discretionary Access Supervisor List (DACL) propertyuser in the Active Directory directory service. Or, the group is in the DACL, but does not need permission to update Terminal Licensing information for the custom account.

Resolution

Scenario 1: However, the license server is not added to the Terminal Server License Server group for the domain where the users are located

For more information on this scenario and its final solution, see Event ID. … … 4105 Terminal Services by user Client license monitoring and reporting .

Scenario 2: The Terminal Server License Server Group almost certainly exists, but does not have permission to update user accounts in Active Directory

The Windows Server 2003 License Server site updates the terminalServer attribute once. New terminal license servers try to update additional attributes if available. Be aware that the Windows Server 09 schema update defines a property customizer that is used to grant permissions for each of the required attributes.

Method 1. Use Dsacls.exe

terminal services event id 4105

Use dsacls.exe to add install permissions for read / write permissions for which the terminalServer attribute or terminal server license server properties of this custom object have been set by the terminal server license group.

Windows Server 2003 Aspects Diagram

  dsacls "CN = XXXX, OU = XXXX, OU = XXXX, OU = XXXX, DC = XXXX, DC = XXXX, DC = XXX" / G"BUILTIN  Terminal Server License Server: WPRP; terminalServer"

If you are granting permissions on a container, you must use the following command:

  dsacls "OU = XXXX, DC = XXXX, DC = XXXX, DC = XXX" / I: S / G"BUILTIN  Terminal Server License Server: WPRP; terminalServer; User"

Windows Server 2008 and newer
```
  dsacls "CN = XXXX, OU = XXXX, OU = XXXX, OU = XXXX, DC = XXXX, DC = XXXX, DC = XXX" / G"BUILTIN  Terminal Server License Server: WPRP; Terminal Server License Server" 
```
When granting read access to the container, use the following command:

Approved

The ASR Pro repair tool is the solution for a Windows PC that's running slowly, has registry issues, or is infected with malware. This powerful and easy-to-use tool can quickly diagnose and fix your PC, increasing performance, optimizing memory, and improving security in the process. Don't suffer from a sluggish computer any longer - try ASR Pro today!
```
  dsacls "OU = XXXX, DC = XXXX, DC = XXXX, DC = XXX" / I: S / G"BUILTIN  Terminal Server License Server: WPRP; Terminal Server License Server; User" 
```

Method 2: Use The Masterp Delegation Management

Use the Delegation of Control Wizard to add permissions to add read / write / write access to the terminalServer attribute, or currently to the Terminal Server License Server property of the user object, after the Terminal Server License Server group. To do this, follow these steps:

Right click, I would say Domain in Active Directory Users and Computers, then click Delegate.
Click “Add” in the user group and dialog box. Enter Terminal Server License Server and click OK. In the 18-meter field of the Users and Groups dialog box, click Next.
In the Tasks for Delegation dialog box, click Create Single Task for Delegation, and then click Next.
In the Active Directory Object Type dialog box, select Important Objects In Folder Only. In the main list, the user clicks “Objects” (entry for further execution in the main list), and then clicks “Next”.
For forests where a lot of Windows Server 2008 runs moreFor new diagrams, in the Permissions dialog box, make sure that only one new check box, Check Shared, is selected. In the list of permissions, select the Read and write Terminal Server License Server check box, and then immediately after that click Next.
In the Completing the Delegation of Control Wizard dialog box, click Finish.