#Vmware workspace one update
#Vmware workspace one windows 10
#Vmware workspace one software
#Vmware workspace one windows 8.1

Now we can finally get to the whole point of this article: Workspace ONE for Microsoft Endpoint Manager will be VMware’s recommendation for customers that are using both products.Īs Shanker Iyer wrote, “ Workspace ONE will build value on top of Microsoft Endpoint Manager for management of Windows 10 devices. Enter Microsoft Endpoint Manager and Workspace ONE for MEMĪs I covered in my article about Microsoft Endpoint Manager, Microsoft is now all about enabling customers to use SCCM and co-management as long as they want, and they’re connecting SCCM to Intune in a new cloud-based management plane. So, the changes to the SCCM agent seem a bit old-school Microsoft to me, but that’s business. VMware had AirLift to keep things coordinated and also I thought that the DeviceManageability CSP was supposed to help with this, too. Microsoft’s justification is that they did this to avoid potential conflicts, but this seems a little odd to me. This did cause problems for some customers, and it sounds like it wasn’t communicated very well. So, this essentially kills a whole swath of co-management (or coexistence in Microsoft’s terms) scenarios.

#Vmware workspace one update

The SCCM 1902 update rollup made an interesting change for co-management and coexistence: If an SCCM-managed device is enrolled into an MDM server other than Intune (i.e., Workspace ONE and any other third-parties), the SCCM agent reverts to a read-only mode. Now, there was one wrinkle in all of this. So, they should be closing in on 2 million devices for 2019. It’s almost the end of the year, and I haven’t seen any more recent numbers, but they did say that they were enrolling a Windows 10 device every 16 seconds. ” VMware was off and running on a super ambitious path.Īt VMworld 2019, we got a progress report: VMware had enrolled 1 million Windows 10 devices in the first half of 2019. At the time, I wrote: “ I don’t think anybody is ready to turn off SCCM any time soon, but the battle lines on this front have been drawn. Microsoft called this “coexistence,” though the rest of the world calls this co-management.Ī few months later, VMware introduced AirLift, their product for pulling configuration data out of SCCM, and coordinating management with Workspace ONE. Other vendors, including VMware, could take also take advantage of the changes in Wind, and enroll SCCM-managed devices into their own MDM servers. Microsoft built an integration between SCCM and Intune to coordinate the handoff of management tasks from one side to another, and called this “co-management.” On Microsoft’s side, at Ignite 2017, they announced a change in Windthat would allow devices to be enrolled in both SCCM and MDM at the same time. AirWatch could even connect to machines that were managed via SCCM (before the co-management days).

#Vmware workspace one software

Without a doubt, there is more to do to make this appealing to all enterprises, but with their foot on the accelerator, VMware can get their pretty quickly.”īy this time, AirWatch (as it was still called) could deploy GPOs and join machines to a domain and VMware used Adaptiva for software distribution. “The general sense that I have coming out of VMworld is that VMware, perhaps more than anyone else, understands exactly what has to happen to get enterprises to switch to UEM. Gabe Knuth (then an independent blogger here at ) wrote this about VMware and Windows management : It was after VMworld 2017 when we felt that things were getting quite serious.

#Vmware workspace one windows 8.1

In 2014, they offered MDM plus an agent on Windows 8.1 in 2015, they were talking about doing AppVolumes on physical devices and 2016, they were partnered with Tanium for VMware Trustpoint.

The background on Workspace ONE and SCCMĭigging back in the archives, you can review VMware’s work on Windows management over the last five years. I already wrote about Microsoft Endpoint Manager (or MEM, as folks are starting to call it) today we’ll look at Workspace ONE for Microsoft Endpoint Manager and what it means. On top of all this, earlier this year, Microsoft made a change to SCCM that made it more difficult to use third-party MDM connections (e.g., MDM enrollment in Workspace ONE) on devices managed by SCCM.