Forum Discussion
Steve Whitcher
Oct 19, 2017Bronze Contributor
Is Co-Management just a more granular either-or choice?
Let me preface this by saying that I haven't yet seen the Ignite demo of Co-Management, so this may have been addressed there. If so, I apologize for not being more prepared. Once we enable co-m...
Steve Whitcher
Oct 19, 2017Bronze Contributor
So it will not be possible to have a computer have updates managed in the cloud, but also get additional updates published through system center? If I move that workload over, do I lose the ability to push third party software updates to clients using SCUP and SCCM?
Is moving a workload an all or nothing thing, or can management of a workload be configured per client or collection?
Is moving a workload an all or nothing thing, or can management of a workload be configured per client or collection?
dctardy
Microsoft
Oct 19, 2017You are right that third party updates are not part of Windows Update for Business (at least not at the moment, it is a common ask and we are looking into it). In a co-management environment you can continue to use SCCM to manage those. In a cloud only environment Intune can help manage these updates with the Intune Management Extension through PowerShell scripts.
- Steve WhitcherOct 19, 2017Bronze ContributorOk, so even if we move management of windows updates to intune/wufb, clients will still get updates that are pushed out from SCCM as well if they aren't in wufb?
- dctardyOct 19, 2017
Microsoft
You have the option to move a set of pilot device to be fully Intune managed and those that you don't move are still managed by SCCM. But, once you have moved a client workload for software updates to Intune, that will be fully managed by Intune and WUfB. The previous response applies - SCUP only applies to those device managed by SCCM.