1. Oracle Virtual Machine
2. Virtual Machine Windows 10
3. Azure Remote Desktop Client
4. Azure Virtual Desktops Download

I uploaded a hyper-v VHD file to storage. I then created a Windows VM from disk and specified that it contains the operating system. Azure says the machine is running and the remote desktop. The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. When you check the screenshot in the Boot diagnostics in the Azure portal, you see the VM boots normally and waits for credentials in the login screen.

Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016

You can install Remote Desktop Services components on physical servers or on virtual machines.

The first step is to create Windows Server virtual machines in Azure. You'll want to create three VMs: one for the RD Session Host, one for the Connection Broker, and one for the RD Web and RD Gateway. To ensure the availability of your RDS deployment, create an availability set (under High availablility in the VM creation process) and group multiple VMs in that availability set.

After you create your VMs, use the following steps to prepare them for RDS.

1. Connect to the virtual machine using the Remote Desktop Connection (RDC) client:
   1. In the Azure portal open the Resource groups view, and then click the resource group to use for the deployment.
   2. Select the new RDSH virtual machine (for example, Contoso-Sh1).
   3. Click Connect > Open to open the Remote Desktop client.
   4. In the client, click Connect, and then click Use another user account. Enter the user name and password for the local administrator account.
   5. Click Yes when warned about the certificate.
2. Enable remote management:
   1. In Server Manager, click Local Server > Remote management current setting (disabled).
   2. Select Enable remote management for this server.
   3. Click OK.
3. Optional: You can temporarily set Windows Update to not automatically download and install updates. This helps prevent changes and system restarts while you deploy the RDSH server.
   1. In Server Manager, click Local Server > Windows Update current setting.
   2. Select Advanced options > Defer upgrades.
4. Add the server to the domain:
   1. In Server Manager, click Local Server > Workgroup current setting.
   2. Click Change > Domain, and then enter the domain name (for example, Contoso.com).
   3. Enter the domain administrator credentials.
   4. Restart the virtual machine.
5. Repeat steps 1 through 4 for the RD Web and GW virtual machine.
6. Repeat steps 1 through 4 for the RD Connection Broker virtual machine.
7. Initialize and format the attached disk on the RD Connection Broker virtual machine:
   1. Connect to the RD Connection Broker virtual machine (step 1 above).
   2. In Server Manager, click Tools > Computer Management.
   3. Click Disk Management.
   4. Select the attached disk, then MBR (Master Boot Record), and then click OK.
   5. Right-click the new disk (marked as Unallocated) and click New Simple Volume.
   6. In the New Simple Volume wizard, accept the default values but provide a applicable name for the Volume label (like Shares).
8. On the RD Connection Broker virtual machine create file shares for the user profile disks and certificates:
   1. Open File Explorer, click This PC, and open the disk that you added for file shares.
   2. Click Home and New Folder.
   3. Enter a name for the user disks folder, for example, UserDisks.
   4. Right-click the new folder and click Properties > Sharing > Advanced Sharing.
   5. Select Share this folder and click Permissions.
   6. Select Everyone, and then click Remove. Now click Add, enter Domain Admins, and click OK.
   7. Select Allow Full Control, and then click OK > OK > Close.
   8. Repeat steps c. to g. to create a shared folder for certificates.

Since everyone started working remotely, I've personally needed to Remote Desktop into more computers lately than ever before. More this week than in the previous decade.

I wrote recently about to How to remote desktop fullscreen RDP with just SOME of your multiple monitors which is super useful if you have, say, 3 monitors, and you only want to use 2 and 3 for Remote Desktop and reserve #1 for your local machine, email, etc.

IMHO, the Remote Desktop Connection app is woefully old and kinda Windows XP-like in its style.

There is a Windows Store Remote Desktop app at https://aka.ms/urdc and even a Remote Desktop Assistant at https://aka.ms/RDSetup that can help set up older machines (earlier than Windows 10 version 1709 (I had no idea this existed!)

Oracle Virtual Machine

The Windows Store version is nicer looking and more modern, but I can't figure out how to get it to Remote into an Azure Active Directory (AzureAD) joined computer. I don't see if it's even possible with the Windows Store app. Let me know if you know how!

So, back to the old Remote Desktop Connection app. Turns out for whatever reason, you need to save the RDP file and open it in a text editor.

Add these two lines at the end (three if you want to save your username, then include the first line there)

Note that you have to use the style .AzureADemail@domain.com

The leading .AzureAD is needed - that was the magic in front of my email for login. Then enablecredsspsupport along with authentication level 2 (settings that aren't exposed in the UI) was the final missing piece.

Add those two lines to the RDP text file and then open it with Remote Desktop Connection and you're set! Again, make sure you have the email prefix.

The Future?

Given that the client is smart enough to show an error from the remote machine that it's Azure AD enabled, IMHO this should Just Work.

More over, so should the Microsoft Store Remote Desktop client. It's beyond time for a refresh of these apps.

NOTE: Oddly there is another app called the Windows Desktop Client that does some of these things, but not others. It allows you to access machines your administrators have given you access to but doesn't allow you (a Dev or Prosumer) to connect to arbitrary machine. So it's not useful to me.

There needs to be one Ultimate Remote Windows Desktop Client that lets me connect to all flavors of Windows machines from anywhere, is smart about DPI and 4k monitors, remotes my audio optionally, and works for everything from AzureAD to old school Domains.

Between these three apps there's a Venn Diagram of functionality but there's nothing with the Union of them all. Yet.

Until then, I'm editing RDP files which is a bummer, but I'm unblocked, which is awesome.

Sponsor: Couchbase gives developers the power of SQL with the flexibility of JSON. Start using it today for free with technologies including Kubernetes, Java, .NET, JavaScript, Go, and Python.

About Scott

Virtual Machine Windows 10

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

Azure Remote Desktop Client

Azure Virtual Desktops Download