mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 12:23:37 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into wufbds-reorg-7512938
This commit is contained in:
@ -47,7 +47,7 @@ We recommend that you disable or manage Windows Hello for Business provisioning
|
||||
|
||||
### Disable Windows Hello for Business using Intune Enrollment policy
|
||||
|
||||
The following method explains how to disable Windows Hello for Business enrollment without Intune.
|
||||
The following method explains how to disable Windows Hello for Business enrollment using Intune.
|
||||
|
||||
1. Sign into the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Go to **Devices** > **Enrollment** > **Enroll devices** > **Windows enrollment** > **Windows Hello for Business**. The Windows Hello for Business pane opens.
|
||||
|
@ -235,14 +235,14 @@ Example: D:(A;;FA;;;WD)
|
||||
| "GR" | GENERIC READ | "SD" | Delete |
|
||||
| "GW" | GENERIC WRITE | "WD" | Modify Permissions |
|
||||
| "GX" | GENERIC EXECUTE | "WO" | Modify Owner |
|
||||
| File access rights | "RP" | Read All Properties |
|
||||
| File access rights | | "RP" | Read All Properties |
|
||||
| "FA" | FILE ALL ACCESS | "WP" | Write All Properties |
|
||||
| "FR" | FILE GENERIC READ | "CC" | Create All Child Objects |
|
||||
| "FW" | FILE GENERIC WRITE | "DC" | Delete All Child Objects |
|
||||
| "FX" | FILE GENERIC EXECUTE | "LC" | List Contents |
|
||||
| Registry key access rights | "SW" | All Validated Writes |
|
||||
| "KA" | "LO" | "LO" | List Object |
|
||||
| "K" | KEY READ | "DT" | Delete Subtree |
|
||||
| Registry key access rights | | "SW" | Self Write |
|
||||
| "KA" | KEY ALL ACCESS | "LO" | List Object |
|
||||
| "KR" | KEY READ | "DT" | Delete Subtree |
|
||||
| "KW" | KEY WRITE | "CR" | All Extended Rights |
|
||||
| "KX" | KEY EXECUTE | | |
|
||||
|
||||
@ -272,4 +272,4 @@ For file system and registry objects, the following recommendations apply.
|
||||
|
||||
- If you have critical registry objects for which you need to monitor all modifications (especially permissions changes and owner changes), monitor for the specific **Object\\Object Name.**
|
||||
|
||||
- If you have high-value computers for which you need to monitor all changes for all or specific objects (for example, file system or registry objects), monitor for all [4670](event-4670.md) events on these computers<b>.</b> For example, you could monitor the **ntds.dit** file on domain controllers.
|
||||
- If you have high-value computers for which you need to monitor all changes for all or specific objects (for example, file system or registry objects), monitor for all [4670](event-4670.md) events on these computers<b>.</b> For example, you could monitor the **ntds.dit** file on domain controllers.
|
||||
|
Reference in New Issue
Block a user