Can SCCM Co-Management (Tenant Attached) & VMWare Workspace One Coexist in same environment ?
Are there any technical limitations/challenges with this setup ?
Also has anyone implemented Autopilot with Ping Federation we are facing issue with this ... any suggestions ?
Can SCCM Co-Management (Tenant Attached) & VMWare Workspace One Coexist in same environment ?
That depends on your definition of co-exist here and the scope.
Do ConfigMgr or Intune care about Workspace One? No.
Can you manage a Windows system using both? No.
Are there any technical limitations/challenges with this setup ?
You need to provide more details on what exactly "this setup" means.
Also has anyone implemented Autopilot with Ping Federation we are facing issue with this ... any suggestions ?
Autopilot doesn't care about the federation as long as the clients can perform the AADJ. To my knowledge, this works fine with Ping, however, that's something you need to validate with Ping.
Hi Jason,
Thanks for your reponse
We have all the Domain joined devices managed via SCCM and we are exploring option to enable Tenant Attach SCCM and enabling co-management using Intune for domain joined devices.
We have workspace one running in parallel for MDM (Android, Iphone, MAC) and Win 10 devices.
Win 10 domain join will continue to be managed by SCCM or SCCM+Intune and Win 10 Devices (Workspace joined) will be parallel without overlap (They will not have WorkspaceOne and SCCM+Intune) its always or.
So as per you its not technical limitation or design issue it can co-exist ?
As noted, as long as you don't try to manage a single system with both Workspace One and ConfigMgr/Intune, then sure. As noted above, the management systems (Intune/ConfigMgr and Workspace One) themselves don't know or care about each other (why and how would or could they?).
The only possible conflict here would be auto-enrollment using AAD as only a single MDM provider can be configured for auto-enrollment in AAD. I don't know anything about Workspace One though so I have no idea if this will or could actually be an issue or not.
Why'd you want to do this is another story though is this will add a large amount of complexity and confusion and make troubleshooting more difficult as well, but that's your choice to make.
@BSLABS-4465, For one device, we can manage it only with one not both. In general, having two management authorities for a single device can be challenging if not properly orchestrated between the two. With co-management, Configuration Manager and Intune balance the workloads to make sure there are no conflicts. This interaction doesn't exist with third-party services, so there are limitations with the management capabilities of coexistence.
When the Configuration Manager client detects that a third-party MDM service is also managing the device, it automatically deactivates certain workloads in Configuration Manager. This behavior allows the MDM service to take over these functions which prevents conflicting settings on the client that could adversely impact the device and user experience. We can see more details in the following link:
https://docs.microsoft.com/en-us/mem/configmgr/comanage/coexistence#:~:text=When%20you%20concurrently%20manage%20Windows,this%20functionality%20is%20called%20coexistence.
For Autopilot troubleshooting, here is some articles for the reference:
https://oofhours.com/2020/07/26/supercharge-the-hybrid-azure-ad-join-device-registration-process/
https://oofhours.com/2020/07/19/troubleshooting-windows-autopilot-hybrid-azure-ad-join/
https://oofhours.com/2020/02/17/what-happened-during-windows-autopilot-esp-decode-it/
Note: Non-Microsoft link, just for the reference.
Hope it can help.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
4 people are following this question.
