Tips For Troubleshooting Terminal Licensing Errors

Recommended: Fortect

Hopefully, if you encounter a terminal license error on your PC, this guide should help you.

protocol

• 3 while reading

This article guarantees a solution for event ID 4105 that occurs on an electronic device on whichm, licensing of remote desktops is performed (licensing of remote desktops).

Applies to: Windows Server R2
Original Knowledge Base Number: 2030310

Symptoms

You may see the following event alert for a computer running a Remote Desktop License, which was previously a Terminal Services (TS) license.

Protocol name: system
Source: Microsoft-Windows-TerminalServices-Licensing
Event ID: 4105
Level: Warning
User: N / A
Computer:
Description:
Upgrading a TS License Server can only use these license attributes for user in the Active Directory domain . Verify that the license server computer is a valid member of Terminal Server License Servers in the Active Directory group field.
If the license server is on a domain controller, the Network Service account must also be a member of the server’s license servers terminal group.
If the license placement server is installed on the regulatorre domain, after you add the appropriate accounts to the Terminal Server License Server group, you must restart the Terminal Services Licensing service to monitor or report usage. CAL TS for each user.
Win32 error code: 0x80070005

Reason

Case ID 4105 may be filed for one of the following reasons:

1. The license server is not a member of the Terminal Server License Server group in the domain where users often reside.
2. The license server is usually installed on a controller, the Network Service account is never a member of the Terminal Server License Server group.
3. If user files existed before the domain was extended to Windows Server 2003, the Terminal Server License Server group might try to be missing from the Active Directory user assignment list in the Discretionary Access Management (DACL) list. Or, the group is in the DACL, but the group does not have permission to update the Terminal Services licensing information on behalf of the employee.

Resolution

Scenario 1: 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 solution for your dog, see Event 4105 # .. – TS CAL Tracking and User Reports .

Scenario 2: The Terminal Server License Server Group almost certainly exists, but does not have permission to update the user account, while the Active Directory has attributes

At best, Windows Server 2003 License Server updates the TerminalServer attribute. Terminal Server license servers will later try to update additional attributes when they become available. To accommodate this, the Windows Server 09 upgrade schema defines a group of properties used to grant permissions for all required attributes.

Method 1. Use Dsacls.exe

Use dsacls.exe to make sure to add permissions to increase read / write permissions for your terminalServer attribute or a set of license server properties Our own user object’s terminal server through the license pool server’s terminal server.

• Windows Server 2003 Totals Schema

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

  When granting permissions for a large 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" 

• Recommended: Fortect

  Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

• 1. Download and install Fortect
• 2. Open the program and click "Scan"
• 3. Click "Repair" to start the repair process