One of the core elements of Windows 365 is the Reprovisioning feature, which allows IT Administrators to recreate a user’s Cloud PC within minutes. Even though the old Cloud PC is being deleted from Intune, the device object still exists in Azure AD. Because Reprovisioning of Cloud PCs might be done quite frequently depending on how many Cloud PCs and issues the users face. The number of device objects in Azure AD might increase quite fast.
Manually going into the Microsoft Endpoint Manager portal to check for failures is not an ideal workflow if you ask me. When failures or anything unintended happens, they should be reported automatically to you outside the system for a better response time. With this new feature, we are differently going a step in the right direction. There are currently three pre-defined alert rules we can use.
You might face yourself in a position where you have to secure files and the current state of a Cloud PC for investigation. With the Place Cloud PC under review feature, you can take a snapshot of a Cloud PC to secure data and safely hand it over for investigation. In this blog post, I will go through the prerequisite, how to use the feature and what it means for the end-user.
Sending the user an email with guidelines on connecting before their Cloud PC is ready could lead the user to try to connect before the Cloud PC is ready. Wouldn’t it be cool if a user only gets an email when their Cloud PC is provisioned and ready to use? in my mind, that is the optimal way of giving the information. I will go through the aspect of how this is working.
Knowing how often users connect to their Cloud PC gives you an idea if they are using it or not. From here, you can investigate if there is a reason for a user not to use the Cloud PC as first intended. Ultimately you can track down the users who no longer need a Cloud PC and can save that license cost. as you might know, there is no built-in usage report in the MEM portal. Therefore I have cooperated with Donna Ryan on a PowerShell script that will gather information about login count over a period and the last login date.
Resizing a Windows 365 Enterprise Cloud PC is very easy and can be done directly within the MEM portal. I like this feature and how seamless it’s working. However, we cannot resize our Cloud PC if we have assigned the license through group-based licensing.
Group-based licensing is a must to gain better visibility and control of your licenses. Therefore it’s a big issue if you ask me.
This article will showcase the PowerShell script I have created to resize group-based licensed Cloud PC.
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:
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.