Home
%3CLINGO-SUB%20id%3D%22lingo-sub-707325%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Configuring%20workloads%20in%20a%20co-managed%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-707325%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20manage%20Windows%2010%20devices%20with%20both%20Configuration%20Manager%20and%20Microsoft%20Intune%20using%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsccm%2Fcomanage%2Foverview%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eco-management%3C%2FA%3E%2C%20Intune%20Support%20Engineer%20%3CSTRONG%3EBetty%20Jia%3C%2FSTRONG%3E%20just%20posted%20a%20great%20article%20over%20on%20our%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FIntune-Customer-Success%2Fbg-p%2FIntuneCustomerSuccess%22%20target%3D%22_self%22%3EIntune%20Customer%20Success%20blog%3C%2FA%3E%20that%20you'll%20want%20to%20take%20a%20look%20at.%20She%20examines%20an%20issue%20where%26nbsp%3Bapps%20and%20PowerShell%20scripts%20deployed%20from%20Intune%20to%20co-managed%20devices%20show%20a%20status%20of%20%3CSTRONG%3ENot%20applicable%3C%2FSTRONG%3E%26nbsp%3Beven%20though%20the%20same%20are%20successfully%20deployed%20to%20devices%20managed%20solely%20by%20Intune.%20Spoiler%20alert%3A%20It%20has%20to%20do%20with%20configuring%20workloads%20like%20%3CSTRONG%3EClient%20Apps%3C%2FSTRONG%3E%26nbsp%3Band%20enabling%20pre-release%20features%20in%20your%20Configuration%20Manager%20environment.%20I%20won't%20give%20it%20all%20away%2C%20but%20I%20will%20say%20that%20whether%20you%20use%20co-management%20today%20or%20have%20plans%20to%20do%20so%20in%20the%20future%2C%20this%20is%20one%20you%E2%80%99ll%20want%20to%20bookmark.%20You%20can%20read%20Betty's%20complete%20post%20at%20the%20link%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CFONT%20size%3D%224%22%20color%3D%22%23333399%22%3E%3CEM%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FIntune-Customer-Success%2FSupport-Tip-Configuring-workloads-in-a-co-managed-environment%2Fba-p%2F707221%22%20target%3D%22_self%22%3ESupport%20Tip%3A%20Configuring%20workloads%20in%20a%20co-managed%20environment%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-707325%22%20slang%3D%22en-US%22%3E%3CP%3EIntune%20Support%20Engineer%20Betty%20Jia%20walks%20through%20resolving%20an%20issue%20you%20might%20see%20when%20co-management%20is%20enabled%2C%20and%20talks%20about%20how%20to%20enable%20pre-release%20features%20in%20Configuration%20Manager.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-707325%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECo-management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

If you manage Windows 10 devices with both Configuration Manager and Microsoft Intune using co-management, Intune Support Engineer Betty Jia just posted a great article over on our Intune Customer Success blog that you'll want to take a look at. She examines an issue where apps and PowerShell scripts deployed from Intune to co-managed devices show a status of Not applicable even though the same are successfully deployed to devices managed solely by Intune. Spoiler alert: It has to do with configuring workloads like Client Apps and enabling pre-release features in your Configuration Manager environment. I won't give it all away, but I will say that whether you use co-management today or have plans to do so in the future, this is one you’ll want to bookmark. You can read Betty's complete post at the link below.

 

Support Tip: Configuring workloads in a co-managed environment