SOLVED
Home

Custom Policy CSP for NCSC Guidance for Windows 10

%3CLINGO-SUB%20id%3D%22lingo-sub-251233%22%20slang%3D%22en-US%22%3ECustom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251233%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20NCSC%20Guidance%20for%20Deploying%20Intune%20managed%20Windows%2010%20clients%20(%3CA%20href%3D%22https%3A%2F%2Fwww.ncsc.gov.uk%2Fguidance%2Feud-guidance-windows-10-1803-mobile-device-management%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EHERE%3C%2FA%3E)%20lists%20two%20custom%20OMA-URI%20settings%20that%20block%20unwanted%20devices%20from%20being%20installed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E.%2FDevice%2FVendor%2FMSFT%2FPolicy%2FConfig%2FDeviceInstallation%2FPreventInstallationOfMatchingDeviceIDs%3C%2FP%3E%3CP%3E.%2FDevice%2FVendor%2FMSFT%2FPolicy%2FConfig%2FDeviceInstallation%2FPreventInstallationOfMatchingDeviceSetupClasses%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20the%20policy%20JSON%20that%20the%20NCSC%20supply%20is%20missing%20these%20settings.%20I%20tried%20to%20create%20the%20SyncML%20for%20both%20IDs%20using%20guidance%20from%20the%20Internet%20but%20I%20get%20a%20catastrophic%20failure%20error%20message%20in%20the%20logs%20and%20the%20policies%20do%20not%20apply.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20settings%20that%20I%20have%20used%20are%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E.%2FDevice%2FVendor%2FMSFT%2FPolicy%2FConfig%2FDeviceInstallation%2FPreventInstallationOfMatchingDeviceIDs%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CENABLED%3E%3C%2FENABLED%3E%3CBR%20%2F%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_IDs_Deny_List%26quot%3B%22%20value%3D%22%26quot%3BPCI%5CCC_0C0A%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_IDs_Deny_Retroactive%26quot%3B%22%20value%3D%22%26quot%3B1%26quot%3B%2F%22%3E%3C%2FDATA%3E%3C%2FDATA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E.%2FDevice%2FVendor%2FMSFT%2FPolicy%2FConfig%2FDeviceInstallation%2FPreventInstallationOfMatchingDeviceSetupClasses%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CENABLED%3E%3C%2FENABLED%3E%3CBR%20%2F%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_Classes_Deny_Retroactive%26quot%3B%22%20value%3D%22%26quot%3B1%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_Classes_Deny_List%26quot%3B%22%20value%3D%22%26quot%3B%7Bd48179be-ec20-11d1-b6b8-00c04fa372a7%7D%26amp%3B%23xF000%3B%7B7ebefbc0-3200-11d2-b4c2-00a0C9697d07%7D%26amp%3B%23xF000%3B%7Bc06ff265-ae09-48f0-812c-16753d7cba83%7D%26amp%3B%23xF000%3B%7B6bdd1fc1-810f-11d0-bec7-08002be2092f%7D%26quot%3B%2F%22%3E%3C%2FDATA%3E%3C%2FDATA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20successfully%20applied%20these%20settings%20using%20a%20custom%20device%20configuration%20policy%3F%20If%20so%20where%20am%20I%20going%20wrong%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20assistance%20will%20be%20gratefully%20received%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-251233%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECSP%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%2010%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-269833%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269833%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20again%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Every%20helpful%20comment!%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-269815%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269815%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eit's%20a%20bit%20misleading%20they%20write%20String%20(XML)%20but%20they%20mean%20data%20type%20string%20and%20use%20the%20XML%20string%20as%20value.%20Later%20in%20the%20guide%20they%20write%26nbsp%3B%3CSPAN%3EString%20(XML%20file)%20and%20there%20they%20really%20mean%26nbsp%3BString%20(XML%20file).%20Treat%20all%20String%20(XML)%20entries%20as%20data%20type%20String.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EYour%20TrunOffAutoPlay%20example%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E.%2FUser%2FVendor%2FMSFT%2FPolicy%2FConfig%2FAutoplay%2FTurnOffAutoPlay%3CBR%20%2F%3E%3CSTRONG%3EString%3A%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CENABLED%3E%3C%2FENABLED%3E%3CDATA%20id%3D%22%26quot%3BAutorun_Box%26quot%3B%22%20value%3D%22%26quot%3B255%26quot%3B%22%3E%3C%2FDATA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebest%2C%3C%2FP%3E%0A%3CP%3EOliver%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-269810%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269810%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Oliver%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20last%20question%2C%20as%20I'm%20following%20also%20the%20NCSC%20Guidance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20did%20you%20configured%20the%20autoplay%20settings%20with%20MDM%3F%26nbsp%3BI'm%20assuming%20that%20those%20are%20String%20(XML).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20the%20NCSC%20guide%2C%20set%20String%20XML%20for%20almost%20all%20the%20policies%20(even%20the%20previous%20one)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-268860%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-268860%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Oliver%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-268856%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-268856%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20have%20to%20use%20type%20String.%20Not%20the%20type%20String%20(XML).%20That%E2%80%98s%20how%20it%20is%20supposed%20to%20be%20configured.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%3CBR%20%2F%3EOliver%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-268850%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-268850%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20facing%20the%20same%20problem.%20One%20quick%20question%2C%20are%20you%20using%20the%20String%20(XML%20file)%20type%20or%20the%20String%20type%20when%20setting%20the%20custom%20Settings%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20using%20the%20String%20(XML%20file)%20I'm%20getting%20an%20error%20when%20saving%20the%20profile.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20Advance%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251561%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251561%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20help%20and%20very%20quick%20response!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20policies%20applied%20with%20your%20settings%20straight%20away.%20I%20checked%20the%20registry%20location%20where%20the%20ADMX%20backed%20policy%20is%20applied%20and%20the%20tuple%20structure%20makes%20sense%20because%20there%20is%20a%20value%2Fdata%20registry%20value%20pair%20for%20each%20item%20in%20the%20CSP%20policy%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251481%22%20slang%3D%22en-US%22%3ERe%3A%20Custom%20Policy%20CSP%20for%20NCSC%20Guidance%20for%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251481%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Andrew%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eyou%20need%20to%20specify%20the%20list%20elements%20slightly%20different.%20Every%20list%20element%20must%20be%20specified%20as%20a%20tuple%20with%20the%20official%20separator%20and%20then%20it%20is%20working.%20e.g.%20instead%20of%26nbsp%3B%3CSPAN%3EPCI%5CCC_0C0A%20you%20must%20specify%26nbsp%3BPCI%5CCC_0C0A%3CSTRONG%3E%26amp%3B%23xF000%3B%3C%2FSTRONG%3EPCI%5CCC_0C0A.%20In%20addition%20the%20retroactive%20values%20must%20be%20true%20or%20false.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E.%2FVendor%2FMSFT%2FPolicy%2FConfig%2FDeviceInstallation%2FPreventInstallationOfMatchingDeviceIDs%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CENABLED%3E%3C%2FENABLED%3E%3C%2FP%3E%0A%3CP%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_IDs_Deny_List%26quot%3B%22%20value%3D%22%26quot%3BPCI%5CCC_0C0A%26amp%3B%23xF000%3BPCI%5CCC_0C0A%26quot%3B%2F%22%3E%3C%2FDATA%3E%3C%2FP%3E%0A%3CP%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_IDs_Deny_Retroactive%26quot%3B%22%20value%3D%22%26quot%3Btrue%26quot%3B%2F%22%3E%3C%2FDATA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E.%2FVendor%2FMSFT%2FPolicy%2FConfig%2FDeviceInstallation%2FPreventInstallationOfMatchingDeviceSetupClasses%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CENABLED%3E%3C%2FENABLED%3E%3C%2FP%3E%0A%3CP%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_Classes_Deny_List%26quot%3B%22%20value%3D%22%26quot%3B%26lt%3B%2FP%22%3E%0A%3C%2FDATA%3E%3C%2FP%3E%3CDIV%3E%0A%3CDIV%3E%3CSPAN%3E%7Bd48179be-ec20-11d1-b6b8-00c04fa372a7%7D%26amp%3B%23xF000%3B%7Bd48179be-ec20-11d1-b6b8-00c04fa372a7%7D%26amp%3B%23xF000%3B%7B7ebefbc0-3200-11d2-b4c2-00a0C9697d07%7D%26amp%3B%23xF000%3B%7B7ebefbc0-3200-11d2-b4c2-00a0C9697d07%7D%26amp%3B%23xF000%3B%7Bc06ff265-ae09-48f0-812c-16753d7cba83%7D%26amp%3B%23xF000%3B%7Bc06ff265-ae09-48f0-812c-16753d7cba83%7D%26amp%3B%23xF000%3B%7B6bdd1fc1-810f-11d0-bec7-08002be2092f%7D%26amp%3B%23xF000%3B%7B6bdd1fc1-810f-11d0-bec7-08002be2092f%7D%3C%2FSPAN%3E%22%2F%26gt%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CDATA%20id%3D%22%26quot%3BDeviceInstall_Classes_Deny_Retroactive%26quot%3B%22%20value%3D%22%26quot%3Btrue%26quot%3B%2F%22%3E%3C%2FDATA%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3Ethis%20applies%20successfully%20on%20my%20devices.%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F49534i497AF35ACF2C0BBF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22SNAG-0009.png%22%20title%3D%22SNAG-0009.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3Ebest%2C%3CBR%20%2F%3EOliver%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Andrew Matthews
Contributor

The NCSC Guidance for Deploying Intune managed Windows 10 clients (HERE) lists two custom OMA-URI settings that block unwanted devices from being installed. 

 

./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceIDs

./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses

 

Unfortunately the policy JSON that the NCSC supply is missing these settings. I tried to create the SyncML for both IDs using guidance from the Internet but I get a catastrophic failure error message in the logs and the policies do not apply. 

 

The settings that I have used are 

 

./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceIDs

 

<enabled/>
<data id="DeviceInstall_IDs_Deny_List" value="PCI\CC_0C0A"/>
<data id="DeviceInstall_IDs_Deny_Retroactive" value="1"/>

 

./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses

 

<enabled/>
<data id="DeviceInstall_Classes_Deny_Retroactive" value="1"/>
<data id="DeviceInstall_Classes_Deny_List" value="{d48179be-ec20-11d1-b6b8-00c04fa372a7}&#xF000;{7ebefbc0-3200-11d2-b4c2-00a0C9697d07}&#xF000;{c06ff265-ae09-48f0-812c-16753d7cba83}&#xF000;{6bdd1fc1-810f-11d0-bec7-08002be2092f}"/>

 

Has anyone successfully applied these settings using a custom device configuration policy? If so where am I going wrong?

Any assistance will be gratefully received

 

8 Replies
Highlighted
Solution

Hi Andrew,

 

you need to specify the list elements slightly different. Every list element must be specified as a tuple with the official separator and then it is working. e.g. instead of PCI\CC_0C0A you must specify PCI\CC_0C0A&#xF000;PCI\CC_0C0A. In addition the retroactive values must be true or false.

 

./Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceIDs

 

<enabled/>

<data id="DeviceInstall_IDs_Deny_List" value="PCI\CC_0C0A&#xF000;PCI\CC_0C0A"/>

<data id="DeviceInstall_IDs_Deny_Retroactive" value="true"/>

 

./Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses

 

<enabled/>

<data id="DeviceInstall_Classes_Deny_List" value="

{d48179be-ec20-11d1-b6b8-00c04fa372a7}&#xF000;{d48179be-ec20-11d1-b6b8-00c04fa372a7}&#xF000;{7ebefbc0-3200-11d2-b4c2-00a0C9697d07}&#xF000;{7ebefbc0-3200-11d2-b4c2-00a0C9697d07}&#xF000;{c06ff265-ae09-48f0-812c-16753d7cba83}&#xF000;{c06ff265-ae09-48f0-812c-16753d7cba83}&#xF000;{6bdd1fc1-810f-11d0-bec7-08002be2092f}&#xF000;{6bdd1fc1-810f-11d0-bec7-08002be2092f}"/>
<data id="DeviceInstall_Classes_Deny_Retroactive" value="true"/>
 
this applies successfully on my devices.
 
SNAG-0009.png
 
best,
Oliver

Thanks for your help and very quick response!

 

The policies applied with your settings straight away. I checked the registry location where the ADMX backed policy is applied and the tuple structure makes sense because there is a value/data registry value pair for each item in the CSP policy data.

 

 

Hi,

 

I'm facing the same problem. One quick question, are you using the String (XML file) type or the String type when setting the custom Settings?

 

When using the String (XML file) I'm getting an error when saving the profile.

 

Thanks in Advance,

 

Hi,

You have to use type String. Not the type String (XML). That‘s how it is supposed to be configured.

Best,
Oliver

Hi Oliver,

 

One last question, as I'm following also the NCSC Guidance.

 

How did you configured the autoplay settings with MDM? I'm assuming that those are String (XML).

 

All the NCSC guide, set String XML for almost all the policies (even the previous one)

Hi,

 

it's a bit misleading they write String (XML) but they mean data type string and use the XML string as value. Later in the guide they write String (XML file) and there they really mean String (XML file). Treat all String (XML) entries as data type String.

 

Your TrunOffAutoPlay example:

 

./User/Vendor/MSFT/Policy/Config/Autoplay/TurnOffAutoPlay
String:
<enabled/><data id="Autorun_Box" value="255">

 

best,

Oliver

Thanks again,

 

very helpful comment! ;)

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies