Hi Robin,
We're using Workspace ONE UEM to provision and manage Windows devices. Where those devices run (on prem or in the cloud) generally doesn't matter, though there are of course some nuances between the various VDI/DaaS offerings in the market.
It's important to note the difference between provisioning and imaging. For the purposes of our discussion, imaging is the process of getting Windows installed, and provisioning is the process of staging or configuring a clean installation of Windows. WS1 UEM does not providing imaging, but we do provide provisioning.
Coming back to your question, we can absolutely use UEM provisioning capabilities to stage your template VMs that contain an existing Windows installation. Last year we published an article with step-by-step instructions to configure your Horizon 8 on vSphere templates with UEM, then automate the process of enrolling the clones for day 2 management.
Enhancements to UEM such as the ability to leave applications installed on unenroll were built to support use cases like this. We have additional features in the works which will further simplify template management and VM enrollment, and the intent is to continue expanding the infrastructure platforms you can use.
We have customers managing VMs on Amazon and Azure, but it's important to note that not all solutions are supported. For example, Windows 365 requires InTune for MDM enrollment, so those devices can't be enrolled to UEM. However, Horizon Cloud on Microsoft Azure VMs are extensively managed by WS1 UEM.
We'll follow up with some additional detail on the Image and Bundle process for Amazon, and the article I listed above should give you a good idea how this translates to Horizon 8 on vSphere. I'd love to hear your feedback on this approach, and if it seems applicable to your use case.
p.s. Be sure to watch the Forums as we've got more content coming about improvements for UEM on virtual devices!
Thanks,
Josh
Hi Robin, We're using Workspace ONE UEM to provision and manage Windows devices. Where those devices run (on prem or in the cloud) generally doesn't matter, though there are of course some nuances between the various VDI/DaaS offerings in the market. It's important to note the difference between provisioning and imaging. For the purposes of our discussion, imaging is the process of getting Windows installed, and provisioning is the process of staging or configuring a clean installation of Windows. WS1 UEM does not providing imaging, but we do provide provisioning. Coming back to your question, we can absolutely use UEM provisioning capabilities to stage your template VMs that contain an existing Windows installation. Last year we published an article with step-by-step instructions to configure your Horizon 8 on vSphere templates with UEM, then automate the process of enrolling the clones for day 2 management. Enhancements to UEM such as the ability to leave applications installed on unenroll were built to support use cases like this. We have additional features in the works which will further simplify template management and VM enrollment, and the intent is to continue expanding the infrastructure platforms you can use. We have customers managing VMs on Amazon and Azure, but it's important to note that not all solutions are supported. For example, Windows 365 requires InTune for MDM enrollment, so those devices can't be enrolled to UEM. However, Horizon Cloud on Microsoft Azure VMs are extensively managed by WS1 UEM. We'll follow up with some additional detail on the Image and Bundle process for Amazon, and the article I listed above should give you a good idea how this translates to Horizon 8 on vSphere. I'd love to hear your feedback on this approach, and if it seems applicable to your use case. p.s. Be sure to watch the Forums as we've got more content coming about improvements for UEM on virtual devices! Thanks, Josh
