Share this post:This content is for the Fall 2019 version of Windows Virtual Desktop (Daas), which runs on Azure. It supports both desktop virtualization (VDI), as well as app virtualization. You’re lucky if you haven’t had the opportunity to work with an on-premises VDI solution like Microsoft RDS. You are in for a pleasant surprise if you have. You will be amazed at how easy it can be to set up and manage, whether you want to virtualize a complete desktop experience, individual apps, or both. Users can also connect securely to published Windows desktops from any device using either the Windows Virtual Desktop HTML5 HTML5 web client or a native client.
Here’s what Microsoft has to say about Windows Virtual Desktop.
You can set up a multi-session Windows 10 deployment to deliver a full Windows 10 with scalability.
Virtualize Office 365 ProPlus to optimize it for multi-user virtual scenarios
Windows 7 virtual desktops are provided with Extended Security Updates for free
Your existing Remote Desktop Services (RDS), Windows Server desktops, and apps can be brought to any computer
Virtualize desktops and apps
A unified management experience allows you to manage Windows 10, Windows Server, Windows 7 desktops and apps.
These are some impressive capabilities, especially when you consider that you can set them up with just a few PowerShell cmdlets. You might be thinking, “Great…PowerShell”, but it really isn’t that bad. As you read this series of articles, I hope you’ll agree. You don’t have to be afraid if PowerShell is not your favorite program. It’s currently in preview and is very user-friendly. We’ll be covering more of this in future articles.
Let’s first go over the requirements for setting up Windows Virtual Desktop. This will allow you to connect your users to their Windows desktops, and applications.
You must ensure that you have the correct licenses for your users. You will experience errors in different places that do not indicate that licensing is an issue. Before you start pulling your hair out wondering why it’s not working, make sure you have the correct licenses for the users who access Windows Virtual Desktop.
OSRequired licenseWindows 10 EnterpriseMicrosoft 365 E3, E5, A3, A5, F1, BusinessWindows E3, E5, A3, A5Windows 10 Enterprise multi-sessionMicrosoft 365 E3, E5, A3, A5, F1, BusinessWindows E3, E5, A3, A5Windows 7 EnterpriseMicrosoft 365 E3, E5, A3, A5, F1, BusinessWindows E3, E5, A3, A5Windows Server 2012 R2, 2016, 2019RDS Client Access License (CAL) with Software AssuranceThere are some infrastructure requirements to support Windows Virtual Desktop as well. From Microsoft
An Azure Active Directory
A Windows Server Active Directory that syncs with Azure Active Directory. This can be configured with one of these: Azure AD Connect (for hybrid organisations)
Azure AD Domain Services (for hybrid and cloud organizations)
Azure subscription that includes a virtual network that either contains the Windows Server Active Directory or is connected to it
You must also make sure that the Azure virtual machines you create to support Windows Virtual Desktop are:
Hybrid AD-joined and standard domain-joined. Azure AD-joined virtual machines are not possible.
One of the supported x64 OS images. Windows 10 Enterprise multi-session version 1809 or later
Windows 10 Enterprise version 1809 or later
Windows 7 Enterprise
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
This series of articles will teach you how to:
Install Windows Virtual Desktop
Publish and grant full access to the Windows 10 desktop
Remote applications can be published and granted access
Configure persistent user profiles using FSLogix
I will use a hybrid configuration to deploy Windows Virtual Desktop. Azure AD Connect is used to sync with Azure AD. I have an Active Directory domain on my premises. My on-premises Active Directory domain is connected to Azure via a site-to–site VPN.
You can find Part 2 of this Step by Step guide here.
Two webinars have also been held on Windows Virtual Desktop. These webinars can be viewed on demand at no cost.
Are you ready for DaaS Part 1?
Are you ready for DaaS Part 2?