RDS: The alternative server name must be specified for Remote Desktop Connection 6.1 and earlier

  • Article

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Remote Desktop Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

Operating System

Windows Server 2008 R2, Windows Server 2012

Product/Feature

Remote Desktop Services

Severity

Warning

Category

Configuration

Issue

The alternative server name is not specified.

Impact

The alternative server name must be specified if you are using Remote Desktop Connection (RDC) 6.1 and earlier. If it is not specified, RDC 6.1 and earlier clients will not be able to connect.

Resolution

The alternative server name is specified by using Remote Desktop Connection Manager on the Remote Desktop Connection Broker server.

An alternative server name must exist so that RDC 6.1 and earlier client computers can connect to the RD Session Host server running in redirection mode. You can specify the name of the alternative server name by using Remote Desktop Connection Manager on the Remote Desktop Connection Broker server.

Membership in the local Administrators group, or equivalent, on the RD Connection Broker server that you plan to configure, is the minimum required to complete this procedure.

To specify an alternative server name by using Remote Desktop Connection Manager

  1. On the RD Connection Broker server, open Remote Desktop Connection Manager. To open Remote Desktop Connection Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Connection Manager.

  2. In the left pane, click RD Virtualization Host Servers, and then on the Action menu, click Properties.

  3. In the Virtual Desktops Properties dialog box, on the Redirection Settings tab, in the Server name box, enter the NetBIOS name or the fully qualified domain name (FQDN) of the RD Session Host server that is configured to provide redirection.

  4. To provide redirection for clients that are using Remote Desktop Connection (RDC) 6.1 or earlier, select the Enable redirection for earlier RDC versions check box, and then enter an alternative server name in the Alternative server name box.

  5. When you are finished, click OK to close the Virtual Desktops Properties dialog box.

A DNS host record must also exist for the alternative server name. This maps the alternative server name to the IP address of the RD Session Host server that is configured to provide redirection to virtual desktops.

Membership in the Domain Admins, Enterprise Admins, or the DnsAdmins group, or equivalent, is required to complete this procedure.

To add a DNS host record for an alternative server name

  1. Open the DNS snap-in. To open the DNS snap-in, log on to a computer where the DNS snap-in has been installed, click Start, point to Administrative Tools, and then click DNS.

  2. Expand the server name of the DNS server that you want to configure, expand Forward Lookup Zones, and then expand the domain name.

  3. Right-click the appropriate zone, and then click New Host (A or AAAA).

  4. In the Name (uses parent domain name if blank) box, type the alternative server name.

  5. In the IP address box, type the IP address of the RD Session Host server that is configured to provide redirection to virtual desktops.

  6. Click Add Host.

  7. When you are finished, click Done.

See Also

Concepts

Best Practices Analyzer for Remote Desktop Services: Configuration
Best Practices Analyzer for Remote Desktop Services