From f26cf9062eb450c20daf551e22cf4a4822017df7 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Fri, 16 Nov 2018 15:11:11 -0800 Subject: [PATCH] edits --- .../mdm/policy-csp-deviceinstallation.md | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/windows/client-management/mdm/policy-csp-deviceinstallation.md b/windows/client-management/mdm/policy-csp-deviceinstallation.md index ea69e7a5a1..323dbfe1ff 100644 --- a/windows/client-management/mdm/policy-csp-deviceinstallation.md +++ b/windows/client-management/mdm/policy-csp-deviceinstallation.md @@ -117,6 +117,40 @@ ADMX Info: +To enable this policy, use the following SyncML. This example allows Windows to install a fictitious device ID, a list of hardware IDs and a list of compatible IDs. In this example, the enumerator is specified by the GUID "{17ed6609-9bc8-44ca-8548-abb79b13781b}". The format of the vendor-specific-id field is Vendor&Device&Subsystem&Revision, where the Vendor subfield is "ven_1", the Device subfield is "dev_2", the Subsystem subfield is "subsys_3", and the Revision subfield is "rev_4". +A device ID is the hardware ID that is the most specific description of a device. In the following example, the device ID specifies the vendor, the device, the subsystem, and the revision. This example applies to matching device IDs that are already installed. + +To configure multiple classes, use `` as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_IDs_Deny_Retroactive to true. + + +``` syntax + + + + $CmdID$ + + + ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/AllowInstallationOfMatchingDeviceIDs + + + chr + + + + + + +``` + +To verify the policies are applied properly, check C:\windows\INF\setupapi.dev.log and see if the following is listed near the end of the log: + +```txt +>>> [Device Installation Restrictions Policy Check] +>>> Section start 2018/11/15 12:26:41.659 +<<< Section end 2018/11/15 12:26:41.751 +<<< [Exit status: SUCCESS] +``` +