Known Issues for TS Licensing Installation

  • Article

Applies To: Windows Server 2008

The following are known issues related to the installation of TS Licensing in Windows Server 2008.

Issue 1 Installing TS Licensing with insufficient AD DS privileges

Issue details

When you install the TS Licensing role service by using the Add Roles Wizard in Server Manager, the Installation Results page may show errors. These errors usually indicate a TS Licensing configuration issue, not an installation problem.

These errors can occur if you do not have the appropriate privileges when installing TS Licensing. For example:

  • If the computer on which you are installing TS Licensing is joined to a domain, you should perform the TS Licensing installation with an account that has Domain Admins privileges in Active Directory Domain Services (AD DS). If you do not install TS Licensing with an account that has Domain Admins privileges in AD DS, the TS Licensing installation may succeed, but you will see an error message on the Installation Results page because TS Licensing could not be properly configured after being installed.

  • If you want to configure the discovery scope for TS Licensing as Forest during the installation process, you should perform the TS Licensing installation with an account that has Enterprise Admins privileges in AD DS. If you do not install TS Licensing with an account that has Enterprise Admins privileges in AD DS, the TS Licensing installation may succeed, but you will see an error message on the Installation Results page because TS Licensing could not be properly configured after being installed.

Workaround

(how you can fix the problem if you encounter it)

If you see error messages on the Installation Results page:

  • Determine if the Terminal Services Licensing service is running. If it is running, the Installation Results page will confirm that TS Licensing installation succeeded but some configuration steps failed.

After confirming that some configuration steps failed, you can do the following to correct the issues noted:

  • Correct these problems, if you have the required privileges in AD DS, by using Review Configuration in the TS Licensing Manager tool. For more information, see Troubleshooting TS Licensing Installation.

  • Contact someone with Domain Admins privileges in AD DS to manually add the computer account for the license server to the Terminal Server License Servers group in AD DS.

  • Contact someone with Enterprise Admins privileges in AD DS to publish the license server in AD DS by using the instructions at https://go.microsoft.com/fwlink/?LinkId=107406.
Issue 2 Specifying an invalid database path during TS Licensing installation

Issue details

While installing TS Licensing on Windows Server 2008 by using the Add Roles Wizard in Server Manager, you can specify an invalid database path for the TS Licensing database and you will be allowed to proceed through installation. You will not be alerted to the invalid TS Licensing database path because the Add Roles Wizard does not validate the path. At the end of the installation, the TS Licensing installation may succeed, but you will see an error message on the Installation Results page.

Workaround

The TS Licensing database path must be a local folder on the computer on which TS Licensing is being installed.

If you enter an invalid TS Licensing database path, the database will automatically be installed to the default database path location (system32\lserver).

The database path cannot be changed after TS Licensing has been installed.

To avoid this issue, on the Configure Discovery Scope for TS Licensing page in the Add Roles Wizard in Server Manager, use the Browse button and select the appropriate folder on the local computer.
Issue 3 Unattended installation limits database and discovery scope options

Issue details

If you install TS Licensing by using unattended installation, the following limitations exist:

  • TS Licensing will be installed with the default database path. It is not possible to specify another database path.

  • The discovery scope of TS Licensing cannot be specified. The discovery scope will be either Domain or Workgroup, depending on whether the computer is joined to a domain. Because the discovery scope cannot be set to Forest, the license server will not be published in AD DS, which will limit which terminal servers will be able to automatically discover the license server.

  • The computer account for the license server will not be automatically added to the Terminal Server License Servers group in AD DS if the computer is joined to a domain. This will prevent the license server from being able to track and report on Terminal Services Per User client access licenses (TS Per User CALs).

Workaround

To avoid these issues, we highly recommend that you use the Add Roles Wizard in Server Manager to install TS Licensing.

If you have done an unattended installation of TS Licensing, you can do the following to correct the issues noted:

  • The database path cannot be changed after TS Licensing has been installed.

  • If you do not have the required privileges, contact someone with Enterprise Admins privileges in AD DS to publish the license server in AD DS by using the instructions at https://go.microsoft.com/fwlink/?LinkId=107406.

  • If you do not have the required privileges, contact someone with Domain Admins privileges in AD DS to manually add the computer account for the license server to the Terminal Server License Servers group in AD DS.
Issue 4 Uninstalling TS Licensing with insufficient AD DS privileges

Issue details

If you uninstall TS Licensing by using the Remove Roles Wizard in Server Manager by using an account with insufficient AD DS privileges, the following issues will occur:

  • The license server is not unpublished from AD DS.

  • The computer account for the license server is not removed from the Terminal Server License Servers group in AD DS.

  • The folder for the TS Licensing database is not removed.

Workaround

To avoid these issues, uninstall TS Licensing by using an account with sufficient AD DS privileges.

Otherwise, you can do the following to correct the issues noted:

  • If you do not have the required privileges, contact someone with Enterprise Admins privileges in AD DS to unpublish the license server in AD DS by using the instructions at https://go.microsoft.com/fwlink/?LinkId=107407.

  • If you do not have the required privileges, contact someone with Domain Admins privileges in AD DS to manually remove the computer account for the license server from the Terminal Server License Servers group in AD DS.

  • Manually delete the folder that contains the TS Licensing database.