When a Windows 10 device running build 1703 or earlier and managed with ConfigMgr\SCCM 1706 or earlier, native device management is disabled by SCCM by default. This means organizations can no longer take advantage of the modern EMM profiles that Windows 10 has to offer. This condition does not affect Windows 10 builds 1709 and newer or ConfigMrg\SCCM 1710 and newer.
The VMware Workspace ONE Integration Client allows you to enroll ConfigMgr or SCCM-managed Windows 10 devices into Workspace ONE for co-management. Without the client, Windows native device management is disabled by SCCM.
To enroll SCCM-managed devices, you must download the VMware Workspace ONE SCCM Integration Client from Workspace ONE Resources. The client must be installed on the SCCM-managed devices before enrollment. We recommend that customers use the VMware Workspace ONE AirLift product to streamline enrollment of co-managed devices.
- AirWatch 8.2+
- Windows 10 devices only
- VMware Workspace ONE SCCM Integration Client
Use the VMware Workspace ONE SCCM Integration Client
Download and install the VMware Workspace ONE SCCM Integration Client onto your SCCM-managed Windows 10 devices to enroll the devices into Workspace ONE.
To enroll SCCM-managed devices:
- Navigate here.
- Download the VMware Workspace ONE Integration Client.
- Using SCCM, push the .MSI to your managed devices and install the client. For help using SCCM, refer to Microsoft support and documentation.
- After installation, enroll your Windows 10 devices using any enrollment method.
How conflicting settings values are resolved:
- For settings with different security levels, the most secure policy takes precedence.
- For settings with equal security levels, the last write wins according to priority of source: Group Policy > MDM Policy > Enterprise provisioning package > OEM provisionining package > Microsoft provisioning package