From 6311d86f893ae180d7e981a9192e69f352cdd8ea Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Thu, 13 Dec 2018 15:25:29 -0800 Subject: [PATCH] edits --- .../device-control/control-usb-devices-using-intune.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md b/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md index e83c6f10e6..ca7a3d4c1a 100644 --- a/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md +++ b/windows/security/threat-protection/device-control/control-usb-devices-using-intune.md @@ -86,8 +86,6 @@ Windows Defender ATP also allows installation and usage of only specifically app ![Custom profile](images/custom-profile-prevent-device-ids.png) -Instead of recommending a particular device ID to select, I would recommend we point the reader to the documentation on hardware identity . That has information about how the identities work overall and link to the common identifier structures (https://docs.microsoft.com/en-us/windows-hardware/drivers/install/device-identifier-formats). From there they can make an educated choice. One suggestion we can put, is to ensure to test the configuration prior to rolling it out to ensure it blocks and allows the devices expected. In testing, ideally various instances of the hardware should be used (i.e. two USB keys rather than only one example). - Peripherals that are allowed to be installed can be specified by their [hardware identity](https://docs.microsoft.com/windows-hardware/drivers/install/device-identification-strings). For a list of common identifier structures, see [Device Identifier Formats](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/device-identifier-formats). Test the configuration prior to rolling it out to ensure it blocks and allows the devices expected. Ideally test various instances of the hardware. For example, test multiple USB keys rather than only one. For a SyncML example that allows installation of specific device IDs, see [DeviceInstallation/AllowInstallationOfMatchingDeviceIDs CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deviceinstallation#deviceinstallation-allowinstallationofmatchingdeviceids). To allow specific device classes, see [DeviceInstallation/AllowInstallationOfMatchingDeviceSetupClasses CSP](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deviceinstallation#deviceinstallation-allowinstallationofmatchingdevicesetupclasses).