Get Started with Azure Remote Desktop Services

Azure Remote Desktop Services is a powerful tool that allows you to access and manage remote desktops from anywhere.

To get started, you'll need to create an Azure account, which can be done in just a few minutes.

Next, you'll need to set up a virtual network, which will serve as the backbone of your remote desktop infrastructure.

Azure provides a wide range of virtual network options, including virtual network gateways and network security groups.

With your virtual network set up, you can then deploy a Remote Desktop Gateway, which will enable secure remote access to your virtual machines.

This is a crucial step, as it will allow you to connect to your remote desktops from any device, at any time.

Azure Remote Desktop Services also supports multiple protocols, including RDP, ICA, and HDX, giving you flexibility and choice.

As you get started, remember to configure your remote desktops with the necessary settings, including user authentication and authorization.

By following these simple steps, you'll be up and running with Azure Remote Desktop Services in no time.

Azure Virtual Desktop is a powerful tool for remote work. You can add a Workspace URL for Azure Virtual Desktop by entering the following URL: https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery.

To set it up, click on the Subscribe button. This will allow you to configure the workspace auto-discovery via email.

To manage your Azure Virtual Desktop, you'll need to remotely connect to the RD Connection Broker server using the RDP client (mstsc.exe) and log on with domain administrator credentials.

You can use Server Manager to view and manage Remote Desktop Services, which includes adding more users to your Active Directory, configuring Gateway and Single-Sign-On (SSO) certificates, and setting up Single-Sign-On for your new users.

To access Server Manager, select Manage and Add servers, then find and select all of the servers, including 'RDSbroker', 'RDSgateway', and all the RD Session Host servers.

Once you've added all the servers, you can select Remote Desktop Services in Server Manager to view and manage your deployment.

By following these steps, you'll be able to configure your Azure Virtual Desktop deployment and start using it with your new users.

Adding a workspace URL is a crucial step in setting up Azure Virtual Desktop. You'll need to enter the correct URL for ARM-based host pools, which is https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery.

To access this URL, click on the Subscribe button. This will help your workspace auto-discovery process.

Remote Access to Windows 10 is a game-changer for remote work. I've personally needed to Remote Desktop into more computers lately than ever before, more this week than in the previous decade.

Using the Remote Desktop Connection app, you can access your Windows 10 machine, but I found it woefully old and Windows XP-like in its style. The Windows Store Remote Desktop app is nicer looking and more modern, but I couldn't figure out how to get it to Remote into an Azure Active Directory joined computer.

To set up Remote Desktop on an Azure AD joined machine, you need to save the RDP file and open it in a text editor. You have to use the style .\AzureAD\[email protected], with the leading .\AzureAD\ needed for login.

Adding two specific lines to the RDP text file is the key to making it work. These lines are enablecredsspsupport and authentication level 2, which aren't exposed in the UI.

AVD offers a Windows 10 native experience, feeling like a desktop, whereas RDS provides a Windows 10 desktop experience on Microsoft Server OS.

AVD uses technology from FSLogic to store and manage user profiles, allowing for a consistent desktop experience even when the virtual machine changes or is reprovisioned.

AVD supports OneDrive and indexed search in pooled desktops, making it ideal for searching across multiple virtual machines.

Apps like OneDrive and Teams are integrated and optimized to work in AVD, whereas there can be challenges with these apps in RDS.

AVD is a Platform-as-a-Service (PaaS), meaning Microsoft manages all the infrastructure, including servers, data flows, storage, server maintenance, and IT tasks.

There are different methods of accessing Azure Virtual Desktop, but we recommend using the desktop client wherever possible. This is because the desktop client offers a more seamless experience.

The Windows App is a viable backup option, but it's not the primary recommended method. This is due to its slightly different functionality compared to the desktop client.

The desktop client is the preferred choice for accessing Azure Virtual Desktop because it provides a more streamlined experience. This makes it easier for users to navigate and get started with the service.

AVD provides a Windows 10 native experience, feeling like a desktop.

AVD uses technology from FSLogic to store and manage user profiles, allowing for a consistent desktop experience even when the virtual machine changes.

AVD supports OneDrive and indexed search in pooled desktops, making it easier to search across multiple virtual machines.

Apps like OneDrive and Teams have been integrated and optimized to work in AVD, reducing challenges often experienced in RDS.

AVD is a Platform-as-a-Service (PaaS), with Microsoft taking care of infrastructure management, including servers, data flows, storage, and server maintenance.

AVD easily scales as companies grow or shrink, eliminating the inefficiencies of purchasing physical servers for peak demand.

After deploying RDS in Azure, confirm the deployment has completed successfully, which normally takes just over an hour depending on the number of RDS Hosts selected.

Navigate to the Resource Group the RDS 2019 farm was deployed to and click on 'deployments'.

To get the RDS web URL address, click on cloud-infrastructure-services.rds-2019-basic-depl and then click on Output, where you'll find the URL to login to your RDS desktop collection.

You can now proceed with configuring your RDS setup.