Many types of people are using virtualization on local devices. For organizations that use Windows 365 Enterprise, Nested virtualization is now available. This empowers users to create virtual instances on their Cloud PC as they would on their local device. Users can use the following systems with this new feature:
- Windows Subsystem for Linux (WSL)
- Windows Subsystem for Android
In this article, I will go through the requirement for nested virtualization on Cloud PC and how to get started with it by enabling Hyper-V.
For the past four months, I have been working on a Cloud PC on my Macbook pro 2021 as my end-to-end device every day. I have been surprised by how good it is working, but there are also some flaws I came across. In this article, I will try to cover all the aspects of my experience with Windows in the cloud from a Mac.
Google country redirection is very annoying when having the virtual machine in another country than your users. Services like google detect the users’ location (internet breakout) and redirect them to a language page based on that. he issue is not within Windows 365 / CloudPC. Google redirects users based on where it thinks users are coming from (Internet breakout). Imagine the virtual machine are located in West Europe (Netherlands), then Google will display everything in Dutch.
When a user is logged into their Cloud PC, non-admin users cannot see the Restart button in the power menu. Therefore they can only restart their Cloud PC from the Windows 365 web interface. I don’t think this is an issue if users only use the Windows 365 web interface. However, I see a “user experience” issue if they are using the Remote Desktop Client instead.
Redirecting local resources such as printers and local drives can be helpful for users to work properly and more efficient. Users can choose which local resources they would like to redirect. There might be reasons to prevent redirection of printers, clipboards, audio, etc.
Let’s look at what options are available and how we, as administrators, can manage them.
If you manage Active Directory, Windows Server deployment, or something else, PowerShell is an essential tool to master. When it comes to Windows 365, there is no difference. The capability to deploy or get information on environments is handy, especially if you want to automate something.
This article will go through how to get information about your Windows 365 environment with PowerShell. But how is it possible when there is no PowerShell module for Windows 365?
To create an Azure Managed image, you have to “Generalize” the VM. once it’s Generalized, it will become unusable. You have to create a new VM and begin from scratch if any changes are needed. You can create a temporary VM to resolve this, but it doesn’t come without some flaws.
It is essential to secure identities and environments from hackers in today’s world, and Windows 365 is no exception. Azure Multi-factor Authentication (MFA) In combination with conditional Access, makes securing your Windows 365 environment even easier and more manageable.
Windows 365 Enterprise can be used with predefined Windows 10/11 images, but you can also use a custom image when deploying cloud PCs to users. This might be a good idea if you wish to preconfigure something in the image before deploying.