mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
adding image
This commit is contained in:
parent
8546c04ec9
commit
3bdbdd01a5
8
.vscode/settings.json
vendored
Normal file
8
.vscode/settings.json
vendored
Normal file
@ -0,0 +1,8 @@
|
||||
{
|
||||
"markdownlint.config": {
|
||||
"MD028": false,
|
||||
"MD025": {
|
||||
"front_matter_title": ""
|
||||
}
|
||||
}
|
||||
}
|
BIN
windows/client-management/images/config-lock-mdsl.png
Normal file
BIN
windows/client-management/images/config-lock-mdsl.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 45 KiB |
@ -21,6 +21,8 @@ In an enterprise organization, IT administrators enforce policies on their corpo
|
||||
|
||||
Secured-Core Configuration Lock (Config Lock) is a new [Secured-Core PC (SCPC)](/windows-hardware/design/device-experiences/oem-highly-secure) feature that prevents configuration drift from Secured-Core PC features (shown below) caused by unintentional misconfiguration. In short, it ensures a device intended to be a Secured-Core PC remains a Secured-Core PC.
|
||||
|
||||
:::image type="content" source="images/config-lock-mdsl.png" alt-text="modern device security levels for config lock.":::
|
||||
|
||||
To summarize, Config Lock:
|
||||
|
||||
- Enables IT to “lock” Secured-Core PC features when managed through MDM
|
||||
|
Loading…
x
Reference in New Issue
Block a user