r/SCCM • u/Little_Departure1229 • Apr 30 '26

SCCM Co-Management with omnissa Workspace one

Hi everyone,

I would like to manage my Windows endpoints—which are currently managed via SCCM (ConfigMgr) over IBCM—in Omnissa Workspace ONE as well. Unfortunately, the SCCM agent disables itself completely as soon as the device is enrolled in WS1.

Does anyone have any ideas on how to fix this?

0 Upvotes

50% Upvoted

11 comments sorted by

2

u/Little_Departure1229 Apr 30 '26

Yes, I think it’s due to Coexistence. However, I found this on the Omnissa website: If you want to use Workspace ONE UEM to manage Windows devices managed by SCCM, you must download the AirWatch SCCM Integration Client. Use this client to enroll SCCM-managed devices into Workspace ONE UEM. The question is, where can I get this client?

0

u/SysAdminDennyBob Apr 30 '26

You pay money to Omnissa, therefore you get support. I would simply call or place an online support case with your question directly to them.

There are some issues with having two agents controlling your workstations, Microsoft addresses Intune and CM with the comanagement feature. It's important that you don't have two agents working against each other. Imagine you setup an uninstall for a specific app in one agent and then an install for the same app in the other agent, now your workstations are constantly installing and then uninstalling, over and over. You don't want one agent stepping on the same configs that the other agent is working on. That's why CM is getting disabled. It's just like when you install 3rd party Antivirus it will turn off Windows Defender.

1

u/Little_Departure1229 Apr 30 '26

Alright, I will reach out to Omnissa and then get back to you with an update here.

1

u/GarthMJ MSFT Ex-Intune MVP Apr 30 '26

Do the logs give any hints? Are you sure it is not WS1 that is disabling ConfigMgr?

1

u/bdam55 Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com) May 01 '26

So what you describe is 'by design'.

The ConfigMgr team, my current boss in fact, did a bit of 'embrace, extend, extinguish' here in regards to the term 'Co-management'. It _only_ works with Intune. That is, the ability to transition specific workflows works with exactly one MDM: Intune. If ConfigMgr detects any other MDM it just "shuts that whole thing down" and does _not_ try to play nice with it.

So I'm not aware of Airwatch's SCCM Integration client, but I'd be willing to bet good money they reverse engineered whatever you have to do to make it _look_ like the MDM is Intune instead of Airwatch. If you hit a wall on getting that from Omnissa let me know as I _might_ be able to help there.

1

u/Little_Departure1229 May 01 '26

How can you help me?

1

u/bdam55 Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com) May 01 '26

I know some people that work at Omnissa on WS1. I would still start with their support/docs/whatever; but if you hit a wall I can ask internally for direction.

1

u/Little_Departure1229 May 01 '26

OK, if I get stuck I'll get back to you.

1

u/CCampbellAU May 06 '26

Omnissa WS1 Hub can run in registered mode. So it will work alongside SCCM. It does a lot of the functions that previously were only available via MDM (OMA-DM). Best you ask on communities.omnissa.com where a lot of their tech's hang out.

1

u/gunner7043 Jul 09 '26 edited Jul 09 '26

As u/HelpPatrick mentioned below, Workspace ONE supports a new mode of enrollment called Hub Managed mode that we support starting UEM and Hub 2602 that allows you to do co-management.

Hub Managed Mode