In any modern business environment, the ability to access services whenever and wherever they are needed is extremely important. In recent years, virtualization technology has become increasingly advanced, with various functionalities being introduced on a regular basis. As a result, traditional PC infrastructure has been gradually replaced with virtual desktop infrastructure VDI which allows you to run and manage multiple virtual machine-based desktops from any device or location.
Microsoft has also introduced its own VDI solution which enables access and management of remote desktops and operating systems.
After going through the entire deployment process, you get access to enterprise-level desktop virtualization, which can provide you with flexibility, efficiency, scalability, security and many more benefits. Hyper-V VDI is a centralized desktop delivery solution which enables running virtual desktop instances, including client operating systems OSesdata, and applications in a server-based virtual machine VM in the data center.
In this case, real physical computers are replaced with virtual desktops. Some users may be given administrator rights, which allows them to install or delete desktop applications, change system settings, install system updates, etc.
It is extremely difficult to control a large organization with thousands of employees performing thousands of tasks at the same time—even more so if this organization has multiple branches all over the world.
As a result, your infrastructure can become exposed to multiple potential threats and dangers. Many organizations decide to deploy the VDI solution in order to address some of their existing desktop management challenges and potential vulnerabilities. To better understand why some business owners choose to build a VDI environment, you need to understand how it works.
In a nutshell, the Microsoft VDI technology entails the following:. As you can see, Hyper-V VDI is a great option for business owners looking to simplify management over their current production workloads. However, there are even more reasons why you should deploy the Microsoft VDI environment, which we will discuss in detail below:.
The entire setup process is complex enough to make some business owners abandon the idea of building a Hyper-V VDI environment entirely. The Before You Begin section should open, which describes what you can do using this wizard.
In the Deployment Type section, click Standard deploymentwhich enables deployment of Remote Desktop Services across multiple servers. In the Deployment Scenario section, click Virtual machine-based desktop deployment in order to enable connection to virtual desktop collections.
Windows Virtual Desktop
Click Next. In the RD Connection Broker section, look through the list of servers available in the server pool and choose the server where the RD Connection Broker will be installed. In the Confirmation section, verify that everything is correct. Check the box Restart the destination server automatically if required and click Deploy. In the Completion section, you can monitor the process of installing RDS role services.
After the installation operation is complete, the local server should restart automatically. The next step is to create a virtual desktop collection, which allows you to build a single platform for running Windows desktops and applications, providing users with access to their personal workstations.This will be broken down into three parts.
Then in the second part, we will go through the process of creating a desktop collection and publishing a Windows 7 pooled VDI desktop. Finally in part three, we will go through the process of maintaining a desktop image for a pooled desktop. This portion will cover the maintenance and updating of the main image in a pooled VDI desktop environment. Before we begin, we will first need a physical server with the Hyper-V role installed.
In a production environment, a Hyper-V cluster is preferred, however for this example, we will be using a single Hyper-V server for our deployment. This is a single physical domain joined R2 server running Hyper-V called Lab The server must be physical and not a virtual machine. On the select installation type screen, select Remote Desktop Services installation and hit next. Since we are adding the Virtualization Host to an existing RDS farm which is already being managed with Server Manager in the server pool, it will automatically find the RD connection broker as it will be listed in the drop down.
Select standard type and hit next. For the deployment scenario, select virtual machine-based desktop deployment and hit next. Click next on both screens. In this scenario, we are also going to allow the wizard to create a new virtual switch within Hyper-V to be used for our virtual desktops.
Microsoft Virtual Desktop Infrastructure (VDI) Explained
This step is not required if a virtual switch was already configured on the Hyper-V server. Hit Deploy. Once it is finished, hit Close to close out of the wizard. If you now look in Hyper-V Manager, you will see a new virtual switch was created and will be used for the virtual desktops. Within the deployment properties, we now have two new sections.
One is called Active Directory and the other Export Location. Ive already pre-created an OU called VDI, and when I select it, it will give me an error stating the permissions are not correct. Depending on the level of security with the account you are logged in as, you can hit apply for the correct security permissions to be applied to the OU.
In some cases, you may be using an account which does not have access to make this change. In these cases, you can click on Generate Script and it will generate a PowerShell script you can copy and send to an admin who has the correct administrative privileges who can run the script to apply to appropriate permissions.
When the correct permissions are made, you will see the following message stating it is configured with the appropriate permissions. If we look at the security settings for the OU, you can see the correct permissions have been made. It will apply these permissions for each of the RD Connection Brokers in the farm since these will be the servers which will be facilitating the creation and deletion of the virtual desktops. Here we can specify the folder where the virtual template, which is used to create the desktops, will be copied to.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:. To set up Windows Virtual Desktop, you will need a few resources and to complete a few initial setup steps:. AD DS will always be running, resulting in a fixed charge per month.
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:. The process is much like how Azure requires you to enable non-standard resource providers before being able to use them. 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:. During this step, you will need two IDs:.
Note: Before proceeding, make sure you import the Windows Virtual Desktop cmdlets for Windows PowerShell as described in the prerequisites section above. 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.
Next, use the following command to create the Windows Virtual Desktop tenant. 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.
Select Windows Virtual Desktop — Provision a host pool. Enter details as follows:. Here an example of what step 3 of the wizard could look like:. Check the summary windows to see your setup passed validation, then click OK.
Hit Createsit back, and relax. Wait for the deployment to finish. The process takes roughly 20 minutes. Once subscribed, you will find the virtualized apps and desktops in the Start menu. Authenticate using the login information to which you assigned a full desktop session.
If you are successful, you should be able to view the desktop:. 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. Great article! I thought the Windows E3 entitlement in M F1 specifically excluded virtualisation rights? That's excellent news! The official docs. Logged in and working now - but the experience is pretty poor from the UK - I suspect everything is hairpinning via the managed RDP gateway in a US or something, even though my test desktop and I are in the UK.
The beta client also has no options to control the RDP stream - forcing the remote desktop to maximum screen resolution etc. I'm hoping we get some configurability back soon.
Huge potential though - looking forward to trying out a RemoteApp pool next! I would like to determine if this is more cost effective than our current set up. Any info would be helpful. The management tooling is free. No need to pay for gateways etc. If you are using Windows Server for your pools you'll still pay a little bit for that licence.Windows Virtual Desktop is a comprehensive desktop and app virtualization service running in the cloud.
Deploy and scale your Windows desktops and apps on Azure in minutes, and get built-in security and compliance features. Deliver the best Office ProPlus experience, with multi-session virtual desktop scenarios to provide the most productive virtualized experience for your users. Quickly virtualize and deploy modern and legacy desktop apps to the cloud in minutes with unified management in the Azure portal. Deploy a complete, intelligent solution that enhances creativity and collaboration for everyone.
Microsoft’s Virtual Desktop Infrastructure (VDI) (Part 1 of 2)
Optimize your cloud experience while lowering costs for your Windows Server desktops and apps. Get all the tools and resources you need to migrate your apps, data, and infrastructure at your own pace, with confidence. Get free extended security updates for your Windows 7 virtual desktop on Azure with Windows Virtual Desktop.
The program provides no-cost app compatibility assistance when deploying Windows 10 and Windows 10 multi-session with Windows Virtual Desktop. Enable development and testing scenarios including virtual developer desktops and simplified load and scale testing virtual machine VM management Windows Virtual Desktop.
Leverage the service to rapidly test. Learn more. See special offers. Select deployment options to match your needs. Use the estimator to understand the quality of your end-user experience when connecting to Windows Virtual Desktop. Find your recommended Azure region, determine your bandwidth requirements, and view your connection health. Learn how to deploy the optimal environment, get hands-on, and explore options for migrating to Windows Virtual Desktop.
Learn how you can deploy and scale your Windows desktops and apps on Azure in minutes, with built-in security and compliance. Read the Azure Blog and subscribe to Azure updates for the latest news and information on Azure products. Home Products Windows Virtual Desktop. Windows Virtual Desktop. Quickly deploy virtual desktops and apps to enable secure remote work. Contact sales for assistance. Windows Virtual Desktop Experience Estimator.
Deploy and scale virtualized Windows desktops and apps on Azure.In Windows Serverthe Microsoft Virtual Desktop Infrastructure VDI deployment is a scenario-based installation that allows you to install, configure, and manage your virtual desktops from a central location.
With the VDI deployment scenario, you are presented with two deployment types:. The deployment process completes the following tasks:. Creates a pooled virtual desktop collection that is based on a virtual hard disk of the virtual desktop template.
This topic contains instructions for setting up a test lab based on the Test Lab Guide: Base Configuration test lab and deploying a VDI Quick Start deployment that uses two servers and one client computer.
The following instructions are for configuring a VDI Quick Start deployment test lab that uses the minimum number of computers. Individual computers are needed to separate the services that are provided on the network and to clearly show the desired functionality. This configuration is not designed to reflect best practices or to reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed to work only on a separate test lab network.
Computers connected to each other by using a Hyper-V virtual switch as shown in the following figure. The computer on which are you installing the Quick Start must have access to join computers to the domain. The virtual desktop template a virtual hard disk must be generalized by using Sysprep and then shut down. You must have hardware-assisted virtualization on APP1 to successfully complete this test lab.
Test Lab Guide: Virtual Desktop Infrastructure Quick Start
You must be logged on as a member of the Domain Admins group or a member of the Administrators group on each computer to complete the tasks that are described in this guide. If you cannot complete a task when you are logged on with an account that is a member of the Administrators group, try performing the task when you are logged on with an account that is a member of the Domain Admins group.
This test lab guide uses the base configuration test lab as a starting place. Before you proceed with the remainder of the steps in this guide, complete the steps in the Test Lab Guide: Base Configuration. If you have already completed the steps in Test Lab Guide: Base Configuration, and you saved a disk image or a virtual machine snapshot of the base configuration, you can restore the base configuration in Hyper-V Manager, and then proceed to the next step. Server Manager will start automatically.
If it does not automatically start, click Starttype servermanager. On the Select installation type page, click Remote Desktop Services installationand then click Next.As you know about server virtualization, the remote system can be almost anything, a PC or a pretty dumb terminal system, all the processing horsepower is done at the server and the actual applications are all centralized at the server as well.Windows Virtual Desktop #1 Deployment
There are 2 different ways desktop sessions are doled out. The personal desktop means every time you get a VDI guest session it is the exact same dedicated session just for you. This now goes to my point about where VDI fits in the marketplace. If you already have a good patch management system to update desktops across a building, then you already have a process to deal with your desktops.
From a single client interface, administrators can create a solution for both RDS and VDI users addressing the needs for all desktop users. Here are the latest Insider stories. More Insider Sign Out. Sign In Register.
Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here. More from the IDG Network. Top 10 in Windows Server R2. Desktop virtualization: Will Windows 7 change the game? Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind. Related: Microsoft. IT Salary Survey: The results are in.Windows VDA is a device or user-based licensing mechanism for managing access to virtual desktops. There is no need to perform Windows 10 Pro activation.
Inherited Activation is enabled. All VMs created by a user with a Windows 10 E3 or E5 license are automatically activated independent of whether a user signs in with a local account or using an Azure Active Directory account. In this scenario, the underlying Windows 10 Pro license must be activated prior to Subscription Activation of Windows 10 Enterprise. For examples of activation issues, see Troubleshoot the user experience. Optional To disable network level authentication, type the following at an elevated command prompt:.
On the Remote tab, choose Allow remote connections to this computer and then click Select Users. Click Addtype Authenticated usersand then click OK three times.
Install Windows Configuration Designer. If you must activate Windows 10 Pro as described for scenario 3complete the following steps.
Otherwise, skip to step On the Account Management page, choose Enroll into Active Directory and then enter the account details. You will need to update the provisioning package and re-inject it into the image after days. Existing virtual machines that are Azure AD-joined and deployed will not need to be recreated.
Otherwise, skip to step 8. Copy the. Double click to initiate the provisioning package install. This will reboot the system. Enter or replace the line that specifies authentication level with the following two lines of text:.
You may also leave feedback directly on GitHub. Skip to main content. Exit focus mode. VMs must be generation 1.
Open Windows Configuration Designer and click Provison desktop services. Note: You can use a different project name, but this name is also used with dism. On the Set up network page, choose Off. On the Add applications page, add applications if desired. This step is optional. On the Add certificates page, add certificates if desired. On the Finish page, click Create.
In file explorer, double-click the VHD to mount the disk image. Determine the drive letter of the mounted image. Type the following at an elevated commnand prompt. Replace the letter G with the drive letter of the mounted image, and enter the project name you used if it is different than the one suggested: Dism.
Is this page helpful? Yes No.