Remote Desktop Services Default Connection

Posted on by admin



-->

Applies To: Windows Server 2016, Windows Server 2019

  1. Better approach is to fix this on the server side so there is no need to configure individual clients: Login to the Remote Desktop Web Access server and open IIS Manager Navigate to Sites Default Web Site RDWeb Double click on HTTP Response Headers.
  2. The section for Remote Desktop port shows the default port to listen for and accept a remote connection. Click the back arrow to return to the previous screen and scroll through the Remote Desktop.
  3. We have added a new Group Policy container under “Remote Desktop Services” called “RemoteApp and Desktop Connections,” and within that container have defined a new policy setting called “Specify default connection URL.” Enabling this policy setting causes users to be subscribed to RemoteApp and Desktop Connection at the specified URL.

Apr 23, 2012 For remote desktop config options greyed out issue. According to your description, I understand that you right-click Computer icon, choose Properties and click the Remote tab, the option 'Allow users to remotely connect to this computer' may be dimmed or greyed out. This may happens due to a Policy setting. Please double check it.

When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability. Most environments include multiple versions of Windows Server - for example, you may have an existing Windows Server 2012 R2 RDS deployment but want to upgrade to Windows Server 2016 to take advantage of the new features (like support for OpenGLOpenCL, Discrete Device Assignment, or Storage Spaces Direct). The question then becomes, which RDS components can work with different versions and which need to be the same?

Connection url for remote desktop

So with that in mind, here are basic guidelines for supported configurations of Remote Desktop Services in Windows Server.

Note

Remote desktop services default connection windows

Make sure to review the system requirements for Windows Server 2016 and system requirements for Windows Server 2019.

Best practices

  • Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.

  • For RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2019 Session Hosts.

  • If you upgrade your RD Session Host to Windows Server 2019, also upgrade the license server. Remember that a 2019 license server can process CALs from all previous versions of Windows Server, down to Windows Server 2003.

  • Follow the upgrade order recommended in Upgrading your Remote Desktop Services environment.

  • If you are creating a highly available environment, all of your Connection Brokers need to be at the same OS level.

RD Connection Brokers

Windows Server 2016 removes the restriction for the number of Connection Brokers you can have in a deployment when using Remote Desktop Session Hosts (RDSH) and Remote Desktop Virtualization Hosts (RDVH) that also run Windows Server 2016. The following table shows which versions of RDS components work with the 2016 and 2012 R2 versions of the Connection Broker in a highly available deployment with three or more Connection Brokers.

3+ Connection Brokers in HARDSH or RDVH 2019RDSH or RDVH 2016RDSH or RDVH 2012 R2
Windows Server 2019 Connection BrokerSupportedSupportedSupported
Windows Server 2016 Connection BrokerN/ASupportedSupported
Windows Server 2012 R2 Connection BrokerN/AN/ANot Supported

Support for graphics processing unit (GPU) acceleration

Remote Desktop Services support systems equipped with GPUs. Applications that require a GPU can be used over the remote connection. Additionally, GPU-accelerated rendering and encoding can be enabled for improved app performance and scalability.

Remote Desktop Services Session Hosts and single-session client operating systems can take advantage of the physical or virtual GPUs presented to the operating system in many ways, including the Azure GPU optimized virtual machine sizes, GPUs available to the physical RDSH server, and GPUs presented to the VMs by supported hypervisors.

See Which graphics virtualization technology is right for you? for help figuring out what you need. For specific information about DDA, check out Plan for deploying Discrete Device Assignment.

GPU vendors may have a separate licensing scheme for RDSH scenarios or restrict GPU use on the server OS, verify the requirements with your favorite vendor.

GPUs presented by a non-Microsoft hypervisor or Cloud Platform must have drivers digitally-signed by WHQL and supplied by the GPU vendor.

Remote Desktop Session Host support for GPUs

The following table shows the scenarios supported by different versions of RDSH hosts.

FeatureWindows Server 2008 R2Windows Server 2012 R2Windows Server 2016Windows Server 2019
Use of hardware GPU for all RDP sessionsNoYesYesYes
H.264/AVC hardware encoding (if suppported by the GPU)NoNoYesYes
Load balancing between multiple GPUs presented to the OSNoNoNoYes
H.264/AVC encoding optimizations for minimizing bandwidth usageNoNoNoYes
H.264/AVC support for 4K resolutionNoNoNoYes

VDI support for GPUs

The following table shows support for GPU scenarios in the client OS.

FeatureWindows 7 SP1Windows 8.1Windows 10
Use of hardware GPU for all RDP sessionsNoYesYes
H.264/AVC hardware encoding (if suppported by the GPU)NoNoWindows 10 1703 and later
Load balancing between multiple GPUs presented to the OSNoNoWindows 10 1803 and later
H.264/AVC encoding optimizations for minimizing bandwidth usageNoNoWindows 10 1803 and later
H.264/AVC support for 4K resolutionNoNoWindows 10 1803 and later

RemoteFX 3D Video Adapter (vGPU) support

Note

Because of security concerns, RemoteFX vGPU is disabled by default on all versions of Windows starting with the July 14, 2020 Security Update and removed starting with the April 13, 2021 Security Update. To learn more, see KB 4570006.

Remote Desktop Services supports RemoteFX vGPUs when VM is running as a Hyper-V guest on Windows Server 2012 R2 or Windows Server 2016. The following guest operating systems have RemoteFX vGPU support:

  • Windows 7 SP1
  • Windows 8.1
  • Windows 10 1703 or later
  • Windows Server 2016 in a single-session deployment only

Remote Desktop Services Default Connection Download

Remote Desktop Services Default Connection

Discrete Device Assignment support

Remote Desktop Services supports Physical GPUs presented with Discrete Device Assignment from Windows Server 2016 or Windows Server 2019 Hyper-V hosts. See Plan for deploying Discrete Device Assignment for more details.

VDI deployment – supported guest OSes

Windows Server 2016 and Windows Server 2019 RD Virtualization Host servers support the following guest OSes:

  • Windows 10 Enterprise
  • Windows 8.1 Enterprise
  • Windows 7 SP1 Enterprise

Note

  • Remote Desktop Services doesn't support heterogeneous session collections. The OSes of all VMs in a collection must be the same version.
  • You can have separate homogeneous collections with different guest OS versions on the same host.
  • The Hyper-V host used to run VMs must be the same version as the Hyper-V host used to create the original VM templates.

Single sign-on

Windows Server 2016 and Windows Server 2019 RDS supports two main SSO experiences:

Remote Desktop Services Default Connection
  • In-app (Remote Desktop application on Windows, iOS, Android, and Mac)
  • Web SSO

Using the Remote Desktop application, you can store credentials either as part of the connection info (Mac) or as part of managed accounts (iOS, Android, Windows) securely through the mechanisms unique to each OS.

To connect to desktops and RemoteApps with SSO through the inbox Remote Desktop Connection client on Windows, you must connect to the RD Web page through Internet Explorer. The following configuration options are required on the server side. No other configurations are supported for Web SSO:

Remote Desktop Services Default Connection Browser Not Supported

  • RD Web set to Forms-Based Authentication (Default)
  • RD Gateway set to Password Authentication (Default)
  • RDS Deployment set to 'Use RD Gateway credentials for remote computers' (Default) in the RD Gateway properties

Note

Due to the required configuration options, Web SSO is not supported with smartcards. Users who login via smartcards might face multiple prompts to login.

For more information about creating VDI deployment of Remote Desktop Services, check out Supported Windows 10 security configurations for Remote Desktop Services VDI.

Using Remote Desktop Services with application proxy services

You can use Remote Desktop Services with Azure AD Application Proxy. Remote Desktop Services does not support using Web Application Proxy, which is included in Windows Server 2016 and earlier versions.

-->

If you can't connect to a Windows virtual machine (VM), you can reset your local administrator password or reset the Remote Desktop Services configuration (not supported on Windows domain controllers). To reset the password, use either the Azure portal or the VM Access extension in Azure PowerShell. After you've signed in to the VM, reset the password for that local administrator.
If you're using PowerShell, make sure that you have the latest PowerShell module installed and configured and are signed in to your Azure subscription. You can also perform these steps for VMs created with the classic deployment model.

You can reset Remote Desktop Services and credentials in the following ways:

Reset by using the Azure portal

First, sign in to the Azure portal and then select Virtual machines on the left menu.

Reset the local administrator account password

  1. Select your Windows VM and then select Reset password under Support + Troubleshooting. The Reset password window is displayed.

  2. Select Reset password, enter a username and a password, and then select Update.

  3. Try connecting to your VM again.

Reset the Remote Desktop Services configuration

This process will enable Remote Desktop service in the VM, and create a firewall rule for the default RDP port 3389.

  1. Select your Windows VM and then select Reset password under Support + Troubleshooting. The Reset password window is displayed.

  2. Select Reset configuration only and then select Update.

  3. Try connecting to your VM again.

Reset by using the VMAccess extension and PowerShell

First, make sure that you have the latest PowerShell module installed and configured and are signed in to your Azure subscription by using the Connect-AzAccount cmdlet.

Reset the local administrator account password

  • Reset the administrator password or user name with the Set-AzVMAccessExtension PowerShell cmdlet. The typeHandlerVersion setting must be 2.0 or greater, because version 1 is deprecated.

    Note

    If you enter a different name than the current local administrator account on your VM, the VMAccess extension will add a local administrator account with that name, and assign your specified password to that account. If the local administrator account on your VM exists, the VMAccess extension will reset the password. If the account is disabled, the VMAccess extension will enable it.

Remote Desktop Services Default Connection Free

Reset the Remote Desktop Services configuration

Remote Desktop Services Default Connection Windows 10

  1. Reset remote access to your VM with the Set-AzVMAccessExtension PowerShell cmdlet. The following example resets the access extension named myVMAccess on the VM named myVM in the myResourceGroup resource group:

    Tip

    At any point, a VM can have only a single VM access agent. To set the VM access agent properties, use the -ForceRerun option. When you use -ForceRerun, ensure you use the same name for the VM access agent that you might have used in any previous commands.

  2. If you still can't connect remotely to your virtual machine, see Troubleshoot Remote Desktop connections to a Windows-based Azure virtual machine. If you lose the connection to the Windows domain controller, you will need to restore it from a domain controller backup.

Va remote desktop services default connection

Remote Desktop Services Default Connection Mac

Next steps

  • If the Azure VM access extension fails to install you can troubleshoot VM extension issues.

  • If you're unable to reset the password using the VM access extension then you can reset the local Windows password offline. This method is more advanced and requires you to connect the virtual hard disk of the problematic VM to another VM. Follow the steps documented in this article first, and attempt the offline password reset method only if those steps don't work.

  • Learn about Azure VM extensions and features.

  • Connect to an Azure virtual machine with RDP or SSH.

  • Troubleshoot Remote Desktop connections to a Windows-based Azure virtual machine.