Getting started with Windows Virtual Desktop
Published Mar 29 2019 01:38 PM 367K Views
Microsoft

Updated 12/20/2019

With the Windows Virtual Desktop now General Available (GA), we wanted to provide a quick overview of the steps required to get your environment up and running.

Before I begin; however, I’d like to take a few moments to explain what Windows Virtual Desktop is and how it can help you deploy and scale Windows and Office on Azure in minutes, with built-in security and compliance.

Windows Virtual Desktop is a comprehensive desktop and app virtualization service that runs in the cloud. Here is a quick list of some of the key features and functionality:

  • Infrastructure services like gateway, brokering, licensing, diagnostics are provided as a service in Azure. There’s no need to deploy and maintain any on-premises infrastructure.
  • Windows Virtual Desktop can leverage Azure Active Directory (Azure AD) as the identity provider, allowing you to leverage additional security controls like multi-factor authentication (MFA) or conditional access.
  • Once a user is connected to Windows Virtual Desktop service, access to Active Directory joined virtual machines (VMs) will be provided using Azure AD identities. In environments where Active Directory Federation Services (AD FS) is implemented for single sign-on (SSO), the user won’t be prompted for credentials when connecting to the VM, providing a seamless sign-on experience.
  • Reverse connect technology means your destination VM doesn’t need any inbound ports to be opened. Even the default RDP port, TCP/3389, doesn’t have to be open. Instead, an agent creates an outbound connection using TCP/443 into the Windows Virtual Desktop management plane. Azure is your reverse proxy for RDP traffic.
  • Virtual machines in Windows Virtual Desktop are not exposed to the Internet directly. They can run using a private IP address and run isolated from other workloads or even the Internet. (The reverse connect technology allows the VMs to be accessed.)
  • Windows Virtual Desktop introduces Windows 10 multi-session, allowing you to offer a Windows 10 Enterprise experience where multiple users can log into the same Windows client VM simultaneously via RDP. (multi-session was historically only possible on Windows Server operating systems.)
  • Access to FSLogix technology, making your Office experience in a non-persistent environment feel like you are using a traditional PC.
  • Windows Virtual Desktop supports full desktop, RemoteApp, and persistent or non-persistent, dedicated or multi-session experiences.
  • Organizations with “Windows 10 Enterprise E3 Per User” licenses or better (e.g. Windows 10 Enterprise E5 or Microsoft 365 E3, E5, F1, or Business) or RDS CALs can use Windows Virtual Desktop for no additional charge apart from Azure compute/storage and network usage billing. Reserved instances can be used to reduce Azure costs up to 80%.

Now let’s move on to the steps you need to take to get started.

Windows Virtual Desktop prerequisites

To set up Windows Virtual Desktop, you will need a few resources and to complete a few initial setup steps:

  • An Azure subscription with sufficient credit (needed to host resources).
  • Download and install the Windows Virtual Desktop cmdlets for Windows PowerShell on a device.
  • Make sure your virtual network in Azure is configured in such a way that new VMs have your Domain Controller or Azure AD Domain Services (Azure AD DS) set as the DNS (otherwise the domain join step will likely fail). For guidance on how to configure DNS when using Azure AD DS, see Enable Azure Active Director Domain Services. For guidance for using a Domain Controller, see Name resolution for resources in Azure virtual networks.
  • Make sure all Azure resources are in the same region.
  • If you require seamless SSO (HTML5 client excluded), you will need AD FS or users will have to authenticate when gaining access to the VM. (Steps on how to enable this with AD FS will follow at a later stage.)
  • An Active Directory to which you can join your VMs. For this, you have three options:

    Option

    Pros

    Cons

    Use Azure AD DS.

    Great for test or isolated environments that do not need connectivity to on-premises resources.

    Azure AD will be your leading source for identities.

    AD DS will always be running, resulting in a fixed charge per month.

    Spin up a DC in your Azure subscription.

    Can sync with on-premises DCs if VPN or ExpressRoute is configured.

    All familiar AD Group Policies can be used.

    Virtual machines can be paused or stopped when needed to reduce costs.

    Adds additional management of a VM and Active Directory in Azure.

    Use VPN or ExpressRoute and make sure your on-premises DCs can be found in Azure.

    No AD DS or Domain Controller required in Azure.

    Latency could be increased adding delays during user authentication to VMs.

    This assumes you have an on-premises environment, not suitable for cloud only tests.

In our test environment, we decided to spin up a new VM with Windows Server 2019 for our domain controller and install Azure AD Connect to sync identities to Azure AD.

Finally, you’ll also need to make sure you have the right credentials. Here’s an overview of the accounts being used throughout the deployment process:

1_accounts-used.png

Once the prerequisites have been met, you can move on to the initial setup of Windows Virtual Desktop. Once these steps have been completed, you will be ready to deploy your initial VMs:

  1. Allow the Windows Virtual Desktop service to access Azure AD.
  2. Assign the “TenantCreator” role to a user account.
  3. Create a Windows Virtual Desktop tenant.
  4. Deploy your first Windows Virtual Desktop host pool.
  5. Test if a user can access a full desktop session.

Allow the Windows Virtual Desktop service to access Azure AD

Before you can create a Windows Virtual Desktop tenant, you must allow Windows Virtual Desktop services to access your Azure AD tenant. The way Windows Virtual Desktop is designed requires explicit Azure AD consent. The process is much like how Azure requires you to enable non-standard resource providers before being able to use them.

  1. Navigate to https://rdweb.wvd.microsoft.com.
  2. Add your Azure AD tenant ID, also referred to as the Directory ID, and hit Submit. (Your Azure AD tenant ID can be found by visiting the Microsoft Azure Portal and navigating to Azure Active Directory > Properties > Directory ID, or by using whatismytenantid.com.)

    2_azure-ad-tenant-id.png

    3_wvd-consent-page.png
  1. Wait a moment for the consent options to refresh, then change Consent Option to Client App and enter the same Azure AD tenant ID to the field for AAD Tenant GUID or Name. Click Submit to continue.

Assign the “TenantCreator” role to a user account

Once you have granted access to Azure AD, you will need to grant permissions for a user to create a Windows Virtual Desktop tenant as follows:

  1. Log in to the Microsoft Azure Portal.
  2. Navigate to Azure Active Directory from the left menu.
  3. Under Manage, click on Enterprise applications.
  4. Search for and select Windows Virtual Desktop.
  5. Under Manage, select Users and groups.
  6. Select Add user, select Users and groups, and search for the user to whom you want to grant permissions to perform the Windows Virtual Desktop tenant creation.
  7. Select the user and hit Select, followed by Assign.

Your user should now have the role of “TenantCreator.”

5_tenantcreator.png

Create a Windows Virtual Desktop tenant

Now that you have a user with the right permissions to create a Windows Virtual Desktop tenant, let’s go ahead and create it. During this step, you will need two IDs:

  • Your Azure AD tenant ID (again).
  • Your Azure subscription ID, which can be found by visiting the Microsoft Azure Portal and doing a keyword search for “Subscriptions.” Select Subscriptions from the search results and your subscription ID, assuming you have an active subscription, will be displayed below.

    6_subscription-id.png

Once you have these two IDs, you can create the Windows Virtual Desktop tenant.

Note: Before proceeding, make sure you import the Windows Virtual Desktop cmdlets for Windows PowerShell as described in the prerequisites section above. If you haven’t completed this step yet, see these instructions.

Create a new PowerShell script, modifying the bold variables to reflect your tenant ID and subscription ID, and execute the following commands. When prompted, sign in using the admin account that was assigned to the TenantCreator role.

#Install PowerShell modules
Install-Module -Name Microsoft.RDInfra.RDPowerShell
Import-Module -Name Microsoft.RDInfra.RDPowerShell
 
# Setting Deployment context
$brokerurl = "https://rdbroker.wvd.microsoft.com"
$aadTenantId = "<value from #1 above>"
$azureSubscriptionId = "<value from #2 above>"
Add-RdsAccount -DeploymentUrl $brokerurl

Next, use the following command to create the Windows Virtual Desktop tenant. Make sure to change the bold variable to a name of your choosing.

New-RdsTenant -Name Contoso -AadTenantId $aadTenantId -AzureSubscriptionId $azureSubscriptionId

For our example, these were the commands I used:

# Setting Deployment context
$brokerurl = "https://rdbroker.wvd.microsoft.com"
$aadTenantId = “f59f09fb-51fe-4e7f-a510-984671d28231”
$azureSubscriptionId = “d4092f2e-5cd5-4d7d-ae58-9c328523828b”
Add-RdsAccount -DeploymentUrl $brokerurl

New-RdsTenant -Name CSPieter -AadTenantId $aadTenantId -AzureSubscriptionId $azureSubscriptionId


7_powershell-example.png

Deploy your first Windows Virtual Desktop host pool

A host pool is a collection of VMs that offer a similar service, such as a full desktop experience. When users connect, they can access a virtual desktop session on any of the hosts in the pool.

Step 1: Configure basic settings

To get started, visit the Microsoft Azure Portal, select Create a Resource and search for Windows Virtual Desktop. Select Windows Virtual Desktop – Provision a host pool.

8_provision-a-host-pool.png

Select Windows Virtual Desktop – Provision a host pool and click Create. Enter details as follows:

  • Host Pool name - Choose something descriptive for the pool of hosts, e.g. “FullDesktop”
  • Desktop type: Pooled or Personal - Choose Pooled unless you are deploying a virtual desktop infrastructure (VDI) configuration wherein every user has their own dedicated VM.
  • Default desktop users - Add a comma separated list of users. (group support will follow later.) You can also use PowerShell to add users to this host pool at a later point.
  • Subscription – Select Microsoft Azure.
  • Resource group - Use an empty Resource Group or enter a name to create a new one.
  • Location - Enter the location where the resources, such as the VMs. will be created. This can be any existing Azure region of your choice.

9_host-pool-settings.png

Step 2: Configure the virtual machines

Next, you’ll enter the VM size details:

  • Select a Usage Profile that matches your environment: Light, Medium, Heavy, or Custom.
  • Enter the number of Total users that will be using this host pool.
  • If desired, change the Virtual machine size. For your test environment, which will likely have very few users, you could opt for a smaller size. You can use the Azure Calculator to get an idea on costs, find "compute" and select "windows virtual desktop".
  • Add a prefix for the VMs. Note: make sure your prefix is unique; don’t reuse your prefixes. Also, don't use underscores.

MarketPlaceStep2.png

Step 3: Configure VM settings

To configure the VMs for Azure, you will need to:

  • Select a custom image from Blob storage, a Managed image in Azure, or one from the Gallery. Our recommendation would be to test “Windows 10 Enterprise multi-session with Office 365 ProPlus” from the Azure Gallery. Office 365 ProPlus has been preconfigured for the ideal state of Windows 10 multi-session.
  • Select the Image OS
  • Select the Disk Type. SSD is recommended.
  • Enter credentials that have permissions to join a VM to Active Directory.
    • Important: check out the username requirements, some usernames are not allowed (like administrator/admin and more) 
  • (Optional) Specify the domain and/or OU.
  • (Optional) Use managed disks.
  • Configure the virtual network and subnet. Pay close attention to this step as this wizard will spin up virtual machines and join them to AD. This means the virtual machine must be able to locate the Domain Controller. Consequently, we recommend opening a separate tab in your browser and validate that:
    • The DNS server IP address that is assigned to the VM points to the DC or AD DS; this can be configured in multiple locations including on your virtual network.
    • The DC, VM, and network resources are in the same Azure region. (Otherwise, your deployment is likely to fail.)

      11_dns-servers.png

Here an example of what step 3 of the wizard could look like:
12_wizard-example.png

The main reasons a deployment fails is due to: 

  • The VM is unable to locate the DC due to networking configuration
    • Troubleshoot this by connecting to your DC via RDP and then RDP to one of the hosts, see if you can manually domain join the VM. 
  • A blacklisted username is used to domain join the VM, see details here
  • Wrong credentials are supplied 

Step 4: Enter authentication details

Once you have configured your VM settings, you will need to enter details about your Windows Virtual Desktop tenant and Azure AD tenant. Unless otherwise directed, leave the Windows Virtual Desktop tenant group name as “Default Tenant Group.” For the Windows Virtual Desktop tenant name, enter the name of the tenant you created earlier in this process.

Note: If you are unsure what your Windows Virtual Desktop tenant name is, use the PowerShell command “Get-RdsTenant” to obtain it.

Enter valid credentials for your Azure AD environment (UPN and password).

13_authenticate.png

Step 5: Check the summary

Check the summary windows to see your setup passed validation, then click OK.
MarketPlaceStep5.png

Step 6: Finalize the creation of your host pool

Hit Create, sit back, and relax. Wait for the deployment to finish. The process takes roughly 20 minutes.

15_create-host-pool.png

Test if a user can access a full desktop session

Once you have created your Windows Virtual Desktop host pool, you can download the client for Android or Windows, or use the HTML5 client. Here’s how to test with Windows or the HTML5 client.

Test with the Windows client

Download the latest Windows Remote Desktop client and subscribe to the feed using the following URL: https://rdweb.wvd.microsoft.com. Once subscribed, you will find the virtualized apps and desktops in the Start menu. You’ll also notice that it’s possible to enable conditional access and/or MFA for users when subscribing to a feed.

16_remote-desktop-client.png

Test with the HTML5 client

Launch a browser InPrivate or incognito mode and visit http://aka.ms/wvdweb to access the HTML5 client. Authenticate using the login information to which you assigned a full desktop session.

17_html5-client.png

If you are successful, you should be able to view the desktop:

18_successful-vm-launch.png

What’s next?

Once you have completed your setup of Windows Virtual Desktop, you can assign other users to your host pool using the following PowerShell command, replacing <WVDTENANTNAME> with the name of your tenant, <HOSTPOOLNAME> with the name of your host pool, and leveraging the appropriate user principal name:

Add-RdsAppGroupUser <WVDTENANTNAME> <HOSTPOOLNAME> "Desktop Application Group" -UserPrincipalName USER@TENANT.onmicrosoft.com

In our environment, this is what the command looks like:

Add-RdsAppGroupUser CSPieter FullDesktop "Desktop Application Group" -UserPrincipalName user2@cspieter.onmicrosoft.com

You can also move on to more advanced tasks, such as:

  • Setting up a host pool dedicated for RemoteApps instead of full desktops.
  • Installing FSLogix profile containers so that you can benefit from the profile solution that makes Office365 ProPlus work, just like on a local PC and/or laptop.

To explore other scenarios and learn more about Windows Virtual Desktop, please see the Windows Virtual Desktop documentation on Docs and watch What is Windows Virtual Desktop? on Microsoft Mechanics. I also encourage you to join the Windows Virtual Desktop community on Tech Community to connect with the Windows Virtual Desktop team and your fellow public preview participants.

108 Comments
Microsoft

Do you have any activities that have state of failed?

Brass Contributor

@Stefan Georgiev: I don't think so. I even ran the commands for another user that I specified defaultDesktopUsers. Is there an command that lists all the Activity IDs?

 

Microsoft

@ShehzadUIT Get-RdsDiagnosticActivities -TenantName <yourtenant> -username <user having the error>

Brass Contributor

@Stefan Georgiev Get-RdsDiagnosticActivities -TenantName <yourtenant> -username <user having the error> comes back empty.

Copper Contributor

 

Hi Everybody 

 

I have Enabled Azure Active directory service synchronized with Azure active directory and follow the steps 100%. unfortunately, I received the below error. I have tried many times. Please advise 

 

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"InvalidParameter\\\",\\r\\n \\\"message\\\": \\\"The Admin Username specified is not allowed.\\\",\\r\\n \\\"target\\\": \\\"adminUsername\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"}]}

 

Copper Contributor

Is there any problem on this community. Nobody answer

Copper Contributor

Hi 

 

How to create more than one VM on the same host pool?

Thanks so much!! Great article!! 

Brass Contributor

Finally, I get WVD working in our environment. 

Brass Contributor
Does WVD support USB redirection to WVD VMs on Azure?
Microsoft

@ltkvien, Please check out this page that lists the redirection options.

Copper Contributor
@Stefan Georgiev: I have same error as @ShehzadUIT I entered the commands you suggested and I get an error from RDBROKER that ConnectionFaileedUserNotAuthoprized and that my user is « not authorized.to access this resource » But I set up this user as the TenantCreator role for the server application (in Enterprise applications) and I am listed as a user under the client application as well.
Copper Contributor

Hi 

 

 

I flow all steps, bat I dont have a remotedektop, can you help me to create a remotedesktop,

 

...?RDS web client screenshot.png

 

Copper Contributor

Hi Guys,

@Techman1910Remote Desktop.JPG

I have successfully setup "Windows Virtual Desktop" in Azure on a free trial, however I have a duplicated "Session Desktop" icon in the Remote Desktop app and via the Webclient, following a an unsuccessful install !

 

Therefore  "Session Desktop" works great, however the other fails, therefore I cannot see how to remove the "Session Desktop" icon that does not operate.

 

Can anybody share with me how to remove the "Session Desktop" not working ?

Copper Contributor

@Techman1910 I got the same problem of the duplicate session desktop icons. I believe it was because I attempted to create my host pool for the 2nd time (I blew away the first environment entirely). Anyway, I'd like to know how to remove it too.

 

--edit--

I figured it out. Using Powershell, 

Remove-RdsSessionHost
Remove-RdsAppGroup
Remove-RdsHostpool

with your correct parameteres in sequence. 

 

Copper Contributor

Hi , after configuring the remote desktop Pool , i just configured another Pool of Vm's for Apps (Words , Excel ) all works fine very cool !

 

2019-04-28 09_32_09-Remote Desktop.jpg

Copper Contributor

Hi Fadi

 

Is not possible to have windows & Apps on the same desktop pool? 

 

 

Microsoft

@Techman1910 

You can use to set custom names for the remote desktop names

 

Set-RdsRemoteDesktop -TenantName "080616-t" -HostPoolName "ERSwUPD080616-p1" -AppGroupName "Desktop Application Group" -FriendlyName "Blah"

 

Before removing a desktop you need to remove all the app groups under it. As for removing https://github.com/hardeights/wvd some good code hear that shows how you need to remove objects in order.

 

Regards

 

S

Copper Contributor

@Stefan Georgiev  ,

 

Hi , they are not in the same Pool 

 

My desktop Session are in the Pool:  FullDesktop

Apps Groups Name : Desktop Application Group

 

and My Apps (Word Excel) are in the Pool : Remote Apps

Apps Groups Name: Apps Groupe

Both Pool are in the same TenantName

is that ok ? 

 

Thanks

 

Copper Contributor

Hi! I am having same technical issue as @ShehzadUIT . I was able to deploy machines as host pool. I am able to connect to each one separately using RDP, but not from https://rdweb.wvd.microsoft.com/webclient/index.html web or rdp. Machines are deployed in VNET connected to on-prem networks. Users from local AD are synced to Azure AD and back to Azure ADDS machines are connected to.

Could you please share how you overcome this error ?

Copper Contributor

@vrvrvrvrvrmay I ask why you use both AD and AADDS?

Configuring WVD to use AADDS (no matter if AD is synced to AAD) requires the user to change password to get AAD to sync a new password hash to AADDS.

Copper Contributor

@ullerdkbecause of large environemnt and testing purposes. Issue here is not with credentials definitely. Password hashes are synced to Azure ADDS by using ADConnect, and as I mentioned - I am able to access machines deployed directly by RDP

Copper Contributor

@vrvrvrvrvrIt is not possible to "AAD Connect" sync between AAD and AADDS. This sync feature is built-in to AADDS.

So I still think your issues is due to missing password change.

Why not try it - change password on a test user?

Copper Contributor

I have not said that I am using AAD Connect to sync between AAD and AADDS. I just have described workflow.  I do have services connected to AADDS (via LDAPS) and I am able to AuthN so this is not an issue. It seems that some network access restrictions are preventing this connection, however I have set-up next hop to internet for VNET's subnet I have deployed virtual desktop machines.. Guide is missing info regarding networking requirements (except DNS).

Copper Contributor

@Fadi Matni 

 

You said :

and My Apps (Word Excel) are in the Pool : Remote Apps

Apps Groups Name: Apps Groupe

 

How can you select apps ? during the provision pool, there is not option related to select apps.

Copper Contributor

 

Setting up a host pool dedicated for RemoteApps instead of full desktops.

 

Is there a guide for this ?

 

 

Copper Contributor

Hi, I'm getting the error "Your Computer Can't connect to the remote desktop gateway server"

Works fine from Web Link, I've tried it on 5 different PC's running Windows 10, 3 worked and 2 showed the below error.

Its definitely to do with the Win10 PC but cant find a fix anywhere.

Any help greatly appreciated!

Andy

 

 

 

Capture.JPG

Copper Contributor

Anybody experience with a custom W10 template? On Step 3 I tryed it with a custom vhd in an blob storage, but the deployment validation failed with the error: InvalidTemplate - template parameter "basURL" not found

Is there a how-to available for custom templates?

Copper Contributor

@Jafar1970 

here is the guide for publishing RemoteApps: https://docs.microsoft.com/en-us/azure/virtual-desktop/manage-app-groups

Maybe you are searching for step3 -> Run the following cmdlet to get a list of start menu apps on the host pool's virtual machine image....

Brass Contributor

I am having the craziest time getting this VIrtual Machine Publishing in the client I can you standard rdp and get to this machine using a public Ip address.  I am using Azure Domain Services I manually joined the machine to the domain. The error i Keep getting is your Admin has not made any resources available.  I am trying to figure out what I need to do to make it available its very strange!

Copper Contributor

For LOB application, can i install directly in WVD? using the same perimeter as in RD session host (change user /install) ? can the gallery image be use for this or need a custom image?

Copper Contributor

@James Lau 

yes, you can directly install your application without seperate commands like "change user /install"

The easiest way for VWD with LOB apps is, to create a custom image (maybe this post helps: https://www.anoopcnair.com/wvd-custom-image-creation-using-windows-10/). Don´t forget FSLogix for the user profiles.

Copper Contributor

I fail to grasp if this solution is possible in a Cloud-only environment. 
So given that one does not use on-premise DCs and would like to keep it this way, is it possible to set everything on the Cloud yet have Virtual Desktop on on-premise desktops ? 
Yes, no - ideas all welcomed!

Copper Contributor

@PeterAtL Yes - there is no need for a local domain control in your edge locations (well, unless you are using non AAD joined W10 desktops as your endpoints), you can have you're Domain Controlelrs's etc hosted on IAAS in Azure. No on prem infrastructure (other than your LAN router/DHCP/DNS) required. As long as your endpoints have internet connectivity, you're golden. 

 

Brass Contributor

"Virtual machines can be paused or stopped when needed to reduce costs." 

For a DC that is synced with on-prem DC over a VPN, powering off a DC seems like a bad idea, doesn't it? 
I thought DCs were intended to be running always and constantly in sync 

Microsoft

Hi

 

I have two AD forests in on-premises environment and users from both forests are synchronized to Azure AD. I believe I will be able to create two different pools and assign them to respective user in each domain. for example any user with UPN suffix @Contoso.com will get VM from pool A and user with UPN suffix @fabrikam.com will get VM from pool B

 

Hope my understanding is correct. Can anyone confirm this ?

 

@Parveen Khanna : Yes, your scenario should work since the user will be recognized from their original domain. The user would only be able to login to the VMs connected to the opposite domain if you have a trust setup.

Iron Contributor

Hi All,

This is more of a question rather than a discussion.
Currently situation -  I have Citrix to publish apps and we have published an app to the users that has a SQL database to hold data.

My question is, how can we configure an app that has a database instance at the back-end and publish the app via WVD?

If you can share your knowledge that would be wonderful.

Thanks.

Shehan.

@shehanjp : You would publish your WVD apps the same way you do with Citrix. You have full control on the VM image, the Azure virtual network, and any other databases you want to configure on that network, so it should mirror what you do with Citrix. The main difference is that now you install the Windows Virtual Desktop agent instead of the Citrix connectors in your environment.

Iron Contributor

@Christian_Montoya 

Yes I understand now. I can map the relationship between the back end and the WVD environment which I couldn't earlier. Thanks for your explanation on this.

 

Cheers!
Shehan.

Copper Contributor

I worked on such a product 12 years ago. This product was world's first virtual desktop and won World Economic Forum's award for that. :)

It provided same features as accessing personal windows desktop using any internet enabled device also then being able to sync data to this desktop from anywhere. This still is a great idea.   

Copper Contributor

It's a good innovation

Microsoft

Hello Pieter, 

Thank you for a thorough guide on how to get a basic deployment done.  Your blog post along with Tom Hickling's post  (https://cloudblogs.microsoft.com/industry-blog/en-gb/cross-industry/2019/09/19/windows-virtual-deskt...

are the best starter guide for WVD deployment. 

 

Regards,

Sai

 

Deleted
Not applicable

any update on this? I am getting the same error:

 

We couldn't connect because there are currently no available resources. Try again later or if this keeps happening, ask your admin or tech support for help.

Microsoft

I think that this page needs to be updated post the Spring 2020 Release.

Copper Contributor

Hi Pieter,

 

What is the difference configuring WVD from marketplace and configuring it by using the search bar on the Azure portal. The icons are different if you have noticed. But they both basically do the same thing. Do you have any valid explanations? Am just being curious. Thank you.

Microsoft

@humanejard if the name matches, it's the same bits. Thanks

Brass Contributor

It's been a while that I have commented on this conversation thread. Since Windows Virtual Desktop has gone GA, our consulting team has implemented it in a couple of production environment for our clients. Let me tell you that the feedback from the clients have been amazing. So bravo @PieterWigleven  @Michael Niehaus  and Windows Virtual Desktop product team for this.

 

Recently, we have come across an issue within the WVD environment. It is auto sign-in of OneDrive using ADAL.

 

The Scenario where we are having this issue where the WVD desktop environment is joined to our on-premise Active Directory domain.

 

These are things we have done to enable auto sign-in for OneDrive using ADAL:

 

1. We have configured a group policy to enable ADAL for OneDrive. the policy settings are:

TC00001.png

2. All our user accounts including the test account has a M365 E3 license assigned

3. All our user accounts including our test account are on-premise AD accounts that are synchronized between AD and AAD using AAD Connect (Password hash synchronization)

 

but ADAL doesn't work and OneDrive doesn't auto sign-in for users. 

 

We have logged a couple of tickets with Microsoft and after weeks of to and fro conversations and troubleshooting, they have come back saying that it is by Design (I.e.  "Windows Virtual Desktop environment, ADAL configured with the above configuration (1, 2 and 3) is not supported" and if you want this auto sign-in configured, you will either use Hybrid AD join scenario or federation). I have asked for any Microsoft docs links that mentions that but they have failed to provide any. 

 

I know that this question is not directly related to the configuration of WVD and I apologies for it but more and more people will face this issue once they have implemented WVD in production environment and therefore, i request @PieterWigleven  @Michael Niehaus and the WVD team to look into this issue and see what they think.

 

Thanks in advance and High Regards

Shehzad

 

 

Microsoft
Copper Contributor

We couldn't connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help.

 

im getting this error, kindly suggest me

Version history
Last update:
‎Mar 18 2020 04:30 AM
Updated by: