What is Microsoft Windows Virtual Desktop – Easy to deploy, a guide on WVD for Citrix experts


What is Microsoft Windows Virtual Desktop – Easy to deploy, a guide on WVD for Citrix experts


I would love to start with to share what is Windows Virtual Desktop, It is a desktop and app virtualization service that runs on the cloud.

Important to understand that here's what you can do when you run Windows Virtual Desktop on Azure:

  • Set up a multi-session Windows 10 deployment that delivers a full Windows 10 with scalability
  • Virtualize Office 365 ProPlus and optimize it to run in multi-user virtual scenarios
  • Provide Windows 7 virtual desktops with free Extended Security Updates
  • Bring your existing Remote Desktop Services (RDS) and Windows Server desktops and apps to any computer
  • Virtualize both desktops and apps
  • Manage Windows 10, Windows Server, and Windows 7 desktops and apps with a unified management experience


I still love my experienced worked on Enterprise level Citrix VDI & Digital transformation projects in GCC region. It always close my heart, I also wanted to share details on Microsoft Windows Virtual Desktop, popular name is WVD, Here are some details, which could take as a WVD guide for Citrix experts.  Its easy to learn and deploy.  I hope this fill the gap between Citrix and WVD both world.  In my previous post explained about how to auto-deply FSLogix.  


In nutshell both technologies can either independently exist or be used together to deliver a remote access service to the customers! However it is important to understand the caveats of these technologies in order to better serve customers in these demanding times. 
Anyone who understands remote access solutions / VDI technologies know well that the basic high level architecture for all these technologies remain the same. 
  • Firstly, we would need an Active Directory infrastructure with domain controllers accessible to the resources being setup for delivery.
  • There is a Web interface that helps users to connect to the services they are entitled to (Storefront, RDWeb)
  • To process all the request they would need some sort of a processing unit in between the actual resources and the web interface service (RDBroker, Delivery Controller)
  • Then typically you have some sort of a mechanism to pool all these resources into different sets, serving different purposes for the organization.(Machine Catalogs)
  • one would also need some way to group the applications / desktops to be served to provide permissions to the users (Delivery groups, Application groups, RDS App Groups)
  • Further to this you would need to have a way to be able to provide persistent experience for the users so you would need a profile management solution, Don't forget to read about my blog on FSLogic Autodeploy post. 
  • All this would be for nothing, without providing users a way to access the resources externally in a secure manner, hence some sort of a gateway service (Citrix Gateway, RDGateway)
So if we compare the different components of Citrix virtual apps and desktop to Windows virtual desktop, it would look something like below diagram.

CITRIX VS WVD


WVD Tenant:

WVD Tenant is the first component you would be setting up on your Azure account to get started with Windows Virtual Desktop. Think of it as the XenDesktop Site that you are configuring on your Citrix. However here you are doing it all on Azure.

HostPool:

Hostpool's are a collection of machines that are hosted on azure and group together for a common purpose. You can have multiple hostpools for different purposes as intended by your organization. They are basically what we call in the VDI world "Session Hosts". Consider these as the Machine Catalogues in Citrix
Majorly we can have 2 different types of hostpools in WVD
  • Personal Hostpool, Where each user session gets a dedicated Desktop that he can logon to (Dedicated Desktops)
  • Pooled Hostpool, These type of hostpools are created to cater to Multi-Session connections from end users and if you would like to provide a random desktop from a pool of desktops on azure. 

AppGroup:

An AppGroup is basically clubbing of various applications / Desktop to be delivered to a set of users. Consider these as the Delivery Group / Application Group in Citrix. A Hostpool can have multiple AppGroups, But any AppGroup can only be associated with one Hostpool at any point of time.
There can be two types of AppGroups: 
  • RemoteApp  - This type of AppGroup is used to publish applications
  • Desktop - This type of AppGroup is used to publish Shared, pooled or dedicated Desktops. 
When a hostpool is created, by default a Desktop AppGroup is created. Which can be deleted if not required! 
Note that all user allocations are done to the AppGroups not the HostPool. Also, WVD supports only allocating the Azure AD user to the AppGroup. Hence planning this is crucial for your WVD deployment. 
Another important point to note here is unlike Citrix Delivery Groups where you may assign a user to both Desktop and Applications in a single delivery group / machine catalog, you can only ever tag the user to either a RemoteApp AppGroup or a Desktop AppGroup in a Hostpool.

RDWeb:

Since WVD is a desktop as a Service, there is really any control on the RDWeb. All of this is hosted and maintained by Microsoft for free of cost. So once you setup your WVD Tenant and create resources, all you need to do is access the portal: https://rdweb.wvd.microsoft.com/webclient with your organization's credentials to access resources entitled to you. Consider this as the Citrix Gateway Service on Citrix Cloud 

Stay safe in COVID-19. Don't forget to share your feedback about this post. 

Regards
Shiv Suthar
Cloud Solutions Consultant


Comments

Post a Comment

Popular posts from this blog

Operation on target Copy data failed: Failure happened on 'Source' side

Image
A simple Pipeline created to fetch data by querying the Rest Api and dumping the data received in blob storage, failed with following error: Error Operation on target Copy data_From API failed: Failure happened on 'Source' side. ErrorCode=UserErrorHttpStatusCodeIndicatingFailure,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The HttpStatusCode 400 indicates failure. {"errors":{"detail":"Internal server error"}},Source=Microsoft.DataTransfer.ClientLibrary,' Why it happened As the error says, something went wrong at source side however, I have tested the Rest API using postman and was able to get the response back with data. And I have reflected same in Source setting of Copy Data activity while creating the pipeline i.e. query, headers – content type and authorization etc Still getting the error, I rechecked again the keys,content type etc - no clue. Took hel
Read more

Run Android emulator and Android Studio on Azure VM using Hyper V

Image
14 min to read. Due to Corona outbreak, times are hard! Please take care everyone! I wish good health for all! Stay safe! There is another outbreak I am seeing – Making Development environment available on Azure to enable Work from home. Almost in every customer call I hear about requirement to enable Development Environment on Azure and accessing it from Home laptop/ PC and continue the business. In the era of “Mobile first” almost every big enterprise, every Small and Medium Business (SMB), every Start up company have mobile development teams. They use variety of tools and one of the important IDE used for Mobile development is “Android Studio”. Installing and running Android studio is smooth; however Android emulator installation fails on Azure VM. It is not s07aight forward. In this blog we will see “how to enable Android emulator with Android Studio on Azure VM”. Let’s go! Without a virtualization technology and VM acceleration, the Android emulator must 0
Read more

The workflow with 'Response' action type should not have triggers with 'splitOn' property

Image
While working on a POC about Debatching in Logic Apps using SplitOn ,    I was encountered with an below error when tried to add Response action in the workflow                             " Failed to save logic app DebatchXMLUsingSplitON. The workflow with 'Response' action type should not have triggers with 'splitOn' property defined: 'manual'. " Why it happened As I had to debatch an xml message, following xpath expression was provided to splitOn property xpath(xml(triggerBody()),'//*[local-name()="PurchaseOrder"  and namespace-uri() ="http://www.adventure-works.com"]' ) So this property will make logic app to instantiate equivalent number of the instances as that of number of splitted message. Say, a batched message with 3 messages in it is posted to this Logic App, then 3 instances of logic app gets created. And this is the reason, why designer stops us when we try to a
Read more