The WVD solution that you just implemented provides users with multi-session Windows 10 virtualized experiences. You can reset the password under the properties of the Virtual Machine in the Azure portal under the “Support + Troubleshooting” section, then the “Reset password” option.You have now created a secure connection between you and your Azure environment. Bring together Microsoft 365 and Azure to provide users with the only multi-session Windows 10 experience—with exceptional scale and reduced IT costs. And that’s it. The machines are identical.In my example, I will create two host pools.
Either open “Azure Active Directory” and click on “Enterprise Applications,” or visit this blade in your Azure Portal: Next, click on “Windows Virtual Desktop.” You can search for it if it is not visible.Select “Users and Groups,” then click on “Add User.”Search for, then select the user you would like to grant permission to create Windows Virtual Tenants to and then click “Assign.”Before we create our VM environment, we have to wrap up a few more initial steps:You can find the Active Directory tenant ID (or Directory ID) in the Azure Portal by selecting “Azure Active Directory,” then clicking on “Properties” or by visiting this link while logged into your Azure Portal: Copy the Active Directory tenant ID (or Directory ID), and save it somewhere safe as you need it later.To find the Subscription ID, from the same Azure Portal session either use the “Search” option to search for “Subscriptions” or visit the following link while logged into your Azure Portal:Copy the Subscription ID and save it somewhere safe, as you need it later.Now it’s time for some PowerShell stuff (Sorry if you thought that moving to the cloud would exempt you from PowerShell). More importantly, we hope you have learned something along the way. However, all in good time.Before we create an AD database, we need to secure our environment to keep out the bad guys. You will, however, be able to remote desktop to it. http://aka.ms/wvd/clients/windows Start the WVD Client – Desktop app. Windows Virtual Desktop or “WVD” is a desktop and app virtualization service that resides in the cloud and is then accessed by users using a device of their choice. It allows the VM to have internet access while installing updates and promoting it to a domain controller. If you remember, you set up the Point-to-Site VPN that allows you to access your Azure machines remotely. From an elevated PowerShell (or PowerShell ISE) session, run the two scripts below. Click Accept We need to repeat this step one more time. But it requires careful implementation to ensure that the user experience is optimal, efficient and secure. Then click “Next: Advanced” at the bottom of the screen.Skip the “Advanced” and “Tags” screens unless you wish to use them, then go straight to the “Review + create” tab. Head to the following tutorial to get started. Azure WVD Windows Virtual Desktop.
It merely reserves the first address assigned by the DHCP, so do not change the IP address to another value.Once the changes save, click on the “Virtual network/subnet” in blue text.Of course, we are going to need a DNS server reference for our environment. Lastly, reboot the VM.If all went well, then the result should be similar to below.
Otherwise, register and sign in. By software defining the desktop, you clip your dependency on rigid hardware and diminishing product lifecycles. Note: All of the text within the red box is the token, you need to copy that text and save it somewhere safely (i.e., use Notepad) so we can use it later to link the VM (wvd-apps-0) to WVD-Host-Pool02.
