Edit

Child Sessions

  • Article

Beginning with Windows Server 2012 and Windows 8, Remote Desktop supports the concept of a child session, which is a special loopback Remote Desktop session that is tied to a user's existing session.

Child sessions are not supported on the following operating systems:

  • Windows RT
  • Windows Server 2012 Server Core installation option
  • Microsoft Hyper-V Server 2012

A system can only have one active and connected child session at any given time.

The child session can be terminated by logging off directly from it, or it will be terminated when its parent session terminates.

Before child sessions can be used on a system, you must enable the child session functionality by calling the WTSEnableChildSessions function. You can also determine if child sessions have been enabled by using the WTSIsChildSessionsEnabled function.

A child session can only be created from within an existing user's session by using the Remote Desktop ActiveX control and setting the "ConnectToChildSession" property with IMsRdpExtendedSettings.Property prior to connecting. When the IMsTscAx.Connect method is called, the Remote Desktop ActiveX control will automatically log on to the child session without prompting for credentials, except when the user is logged into the parent session using a smart card or before child sessions are enabled. Unlike a regular Remote Desktop session, a user does not need the Remote Interactive right to log on to the child session because this is a loopback session.

A child session cannot be locked. It will have no screen saver and no logon screen. Also, unlike a regular session, if the WinLogon logon text policy is set, the logon text will not be displayed in this child session. Also, there will be no effect of Remote Desktop Connection Timeout Group policies on the child session if these policies are set.

The following APIs are used in conjunction with child sessions: