10.2. Procedure – Creating and editing protocol-level RDP settings

Purpose: 

RDP settings determine the parameters of the connection on the protocol level, including timeout value, the version of RDP permitted in the connection, and display parameters. Complete the following procedure to create a new RDP settings profile or edit an existing one:

Figure 10.1. RDP Control > Settings — RDP settings

RDP Control > Settings — RDP settings
Warning

Modifying the RDP settings is recommended only to advanced users. Do not modify these settings unless you exactly know what you are doing.

Steps: 

  1. Navigate to RDP Control > Settings and click to create an RDP setting profile. Enter a name for the profile (for example rdp5only).

  2. Click to display the parameters of the RDP connection.

  3. Modify the parameters as needed. The following parameters are available:

    • Idle timeout: Timeout value for the connection in seconds. To avoid early timeout, set it to a larger value, for example a week (604800 seconds).

      Warning

      Determining if a connection is idle is based on the network traffic generated by the connection, not the activity of the user. For example, if an application or the taskbar of a graphical desktop displays the time which is updated every minute, it generates network traffic every minute, negating the effects of timeout values greater than one minute and preventing PSM from closing the connection.

      Warning

      If the value is set below 31 seconds, MSTSC can fail and prevent new connections if Act as a Remote Desktop Gateway is enabled in RDP Control > Connections. To prevent this, set the Idle timeout value to at least 31 seconds.

    • Maximum display width: The maximum allowed width of the remote desktop in pixels (for example 1024).

      Note

      The Maximum display width and Maximum display height options should be high enough to cover the combined resolution of the client monitor setup. Connections that exceed these limits will automatically fail. Make sure to adjust these settings if your clients use multiple monitors. For example, if your clients use two monitors that have a resolution of 1920x1080 pixels each, set Maximum display width to 4000, and Maximum display height to 2200.

    • Maximum display height: The maximum allowed height of the remote desktop in pixels (for example 768).

      Note

      The Maximum display width and Maximum display height options should be high enough to cover the combined resolution of the client monitor setup. Connections that exceed these limits will automatically fail. Make sure to adjust these settings if your clients use multiple monitors. For example, if your clients use two monitors that have a resolution of 1920x1080 pixels each, set Maximum display width to 4000, and Maximum display height to 2200.

    • Maximum display depth: The maximum allowed color depth the remote desktop in bits (for example 24). The following values are valid: 8, 15, 16, 24.

      Warning
      • Using 32-bit color depth is currently not supported: client connections requesting 32-bit color depth automatically revert to 24-bit.

      • Certain Windows versions do not support 24-bit color depth. In this case, those versions can only be displayed in 16-bit color depth. PSM automatically changes its settings to 16-bit.

    • Enable Network Level Authentication: Select this option to enable the use of Network Level Authentication (NLA, also called Credential Security Service Provider or CredSSP).

      Note the following points:

      • SSL-encrypted connections do not require this option, it is only needed for Network Level Authentication (NLA).

      • Smartcard authentication cannot be used when the Enable Network Level Authentication option is enabled.

      Warning
      • To access hosts running Windows 2008 Server R2 using Network Level Authentication (NLA), select the Enable RDP4 style authentication option as well.

      • To access servers from Windows XP SP3 clients using Network Level Authentication (NLA), you have to turn CredSSP on. For details, see Description of the CredSSP in Windows XP SP3.

    • Enable RDP4 style authentication: Select this option to enable RDP4 authentication within the RDP5 protocol. This might be needed for compatibility reasons with certain client applications.

    • Enable pre channel check: Select this option to evaluate the connection and channel policies before establishing the server-side connection. That way if the connection is not permitted at all, PSM does not establish the server-side connection.

    • Permit unreliable usernames: PSM automatically terminates RDP connections if it cannot reliably extract the username from the RDP connection. Enable this option to permit connections with unreliable usernames. For details on ensuring that the usernames in RDP connections are reliable, see Section 10.10, Usernames in RDP connections.

      Known issue: When a accessing a Windows Server 2003 R2 host, the Permit unreliable usernames option is disabled, and the username is unreliable, PSM terminates the connection, but only after the user logs in. As a result, the session is not closed on the server-side.

    • Autologon domain suffix: Enter the suffix that the client will append to the domain when using autologon in conjunction with Network Level Authentication (CredSSP).

  4. Click .

  5. Select this settings profile in the RDP settings field of your connections.