diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-intune.md b/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-intune.md index c9a7031428..72163a199c 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-intune.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-intune.md @@ -238,7 +238,7 @@ The following example shows how program execution from removable media can be di ## Restrict all devices from specific vendors -The following example restricts all devices from specific vendors (in this case identified by `090c` and `8068`). All other devices will be unrestricted, since the permission defined at the top level of the policy lists all possible permissions (read, write, and execute). +The following example restricts all devices from specific vendors (in this case identified by `fff0` and `4525`). All other devices will be unrestricted, since the permission defined at the top level of the policy lists all possible permissions (read, write, and execute). ```xml @@ -298,14 +298,14 @@ The following example restricts all devices from specific vendors (in this case vendors - 090c + fff0 permission none - 8068 + 4525 permission @@ -323,7 +323,7 @@ The following example restricts all devices from specific vendors (in this case ## Restrict specific devices identified by vendor ID, product ID, and serial number -The following example restricts two specific devices, identified by vendor ID `090c`, product ID `1000`, and serial numbers `04ZSSMHI2O7WBVOA` and `04ZSSMHI2O7WBVOB`. At all other levels of the policy the permissions include all possible values (read, write, and execute), meaning that all other devices will be unrestricted. +The following example restricts two specific devices, identified by vendor ID `fff0`, product ID `1000`, and serial numbers `04ZSSMHI2O7WBVOA` and `04ZSSMHI2O7WBVOB`. At all other levels of the policy the permissions include all possible values (read, write, and execute), meaning that all other devices will be unrestricted. ```xml @@ -383,7 +383,7 @@ The following example restricts two specific devices, identified by vendor ID `0 vendors - 090c + fff0 permission diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-jamf.md b/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-jamf.md index 2b059af7c6..eb82180726 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-jamf.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-jamf.md @@ -115,7 +115,7 @@ The following example shows how program execution from removable media can be di ## Restrict all devices from specific vendors -The following example restricts all devices from specific vendors (in this case identified by `090c` and `8068`). All other devices will be unrestricted, since the permission defined at the top level of the policy lists all possible permissions (read, write, and execute). +The following example restricts all devices from specific vendors (in this case identified by `fff0` and `4525`). All other devices will be unrestricted, since the permission defined at the top level of the policy lists all possible permissions (read, write, and execute). ```xml @@ -136,14 +136,14 @@ The following example restricts all devices from specific vendors (in this case vendors - 090c + fff0 permission none - 8068 + 4525 permission @@ -159,7 +159,7 @@ The following example restricts all devices from specific vendors (in this case ## Restrict specific devices identified by vendor ID, product ID, and serial number -The following example restricts two specific devices, identified by vendor ID `090c`, product ID `1000`, and serial numbers `04ZSSMHI2O7WBVOA` and `04ZSSMHI2O7WBVOB`. At all other levels of the policy the permissions include all possible values (read, write, and execute), meaning that all other devices will be unrestricted. +The following example restricts two specific devices, identified by vendor ID `fff0`, product ID `1000`, and serial numbers `04ZSSMHI2O7WBVOA` and `04ZSSMHI2O7WBVOB`. At all other levels of the policy the permissions include all possible values (read, write, and execute), meaning that all other devices will be unrestricted. ```xml @@ -180,7 +180,7 @@ The following example restricts two specific devices, identified by vendor ID `0 vendors - 090c + fff0 permission diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-overview.md b/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-overview.md index 90c207978f..39db0acd05 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-overview.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-device-control-overview.md @@ -349,7 +349,7 @@ Example of output: ```Output .Device(s) |-o Name: Untitled 1, Permission ["read", "execute"] -| |-o Vendor: General "090c" +| |-o Vendor: General "fff0" | |-o Product: USB Flash Disk "1000" | |-o Serial number: "04ZSSMHI2O7WBVOA" | |-o Mount point: "/Volumes/TESTUSB"