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.
Enable Modern authentication to Secure your user idenitites, with Multi-factor authentication. Many companies have a lot of data in public cloud, that data is usually secured by user identities, it’s common that users choose a weak and common password, that are easy for hackers to recognize.