Remote Administrative Connections (“mstsc /admin”) to the XenApp Server Consumes a Terminal Service License

Remote Administrative Connections (“mstsc /admin”) to the XenApp Server Consumes a Terminal Service License

book

Article ID: CTX200945

calendar_today

Updated On:

Description

When you connect to the XenApp server using "mstsc /admin" option, RD license is consumed if XenApp is installed. If XenApp is not installed, you can connect to server (maximum two sessions) by "mstsc /admin" without consuming RD license.

Background

Terminal Service license is not required if creating remote administrative connections (“mstsc /admin”) for maximum two concurrent sessions. For more information, refer to Overview of Remote Desktop Licensing.
Important: Remote Desktop supports two concurrent connections to remotely administer a computer. You do not need a license server for these connections.

Refer to Command line parameters for Remote Desktop Connection.
Normal remote connection: “mstsc”         
Remote administrative connection: “mstsc /admin” 

Steps to reproduce
  1. Prepare a server (Windows2008R2) in the environment where you do not have RD license server.

  2. Ensure you can connect to server using mstsc /admin without RD license.

  3. Install XenApp on the server. 
    You cannot connect to the server using "mstsc /admin".

  4. Add RD license server in the environment.
    You can now connect to the server using "mstsc /admin".

Resolution

This issue is by design of Windows 2008 R2 or later.


Problem Cause

Windows Remote Desktop Service allows two concurrent remote administrative connections through the Windows built-in RDP which do not consume RD licenses.

Any connection through third party RDS procotol (for example, XenApp RDP proxy protocol extension) consumes a RD license, even though the connection is made using “mstsc /admin”.

Issue/Introduction

This article explains about remote administrative connections (“mstsc /admin”) to the XenApp server consuming a Terminal Service License.