deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Corrected code block label to a valid type

Browse Source 
Valid types are listed here: https://review.docs.microsoft.com/en-us/help/contribute/metadata-taxonomies?branch=master#dev-lang
This commit is contained in:
Gary Moore 2021-11-10 12:24:33 -08:00
parent d6a8f600c6
commit f136bda35c
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
windows/client-management/mdm/enterprisedataprotection-csp.md
View File

@ -30,7 +30,8 @@ To learn more about WIP, see the following articles:
- [General guidance and best practices for Windows Information Protection (WIP)](/windows/security/information-protection/windows-information-protection/guidance-and-best-practices-wip) - [General guidance and best practices for Windows Information Protection (WIP)](/windows/security/information-protection/windows-information-protection/guidance-and-best-practices-wip)
The following shows the EnterpriseDataProtection CSP in tree format. The following shows the EnterpriseDataProtection CSP in tree format.
```
```console
./Device/Vendor/MSFT ./Device/Vendor/MSFT
EnterpriseDataProtection EnterpriseDataProtection
----Settings ----Settings
@ -45,6 +46,7 @@ EnterpriseDataProtection
--------EDPShowIcons --------EDPShowIcons
----Status ----Status
``` ```
<a href="" id="--device-vendor-msft-enterprisedataprotection"></a>**./Device/Vendor/MSFT/EnterpriseDataProtection** <a href="" id="--device-vendor-msft-enterprisedataprotection"></a>**./Device/Vendor/MSFT/EnterpriseDataProtection**
The root node for the CSP. The root node for the CSP.
@ -72,7 +74,6 @@ Changing the primary enterprise ID is not supported and may cause unexpected beh
> The client requires domain name to be canonical, otherwise the setting will be rejected by the client. > The client requires domain name to be canonical, otherwise the setting will be rejected by the client.
Here are the steps to create canonical domain names: Here are the steps to create canonical domain names:
1. Transform the ASCII characters (A-Z only) to lowercase. For example, Microsoft.COM -> microsoft.com. 1. Transform the ASCII characters (A-Z only) to lowercase. For example, Microsoft.COM -> microsoft.com.
@ -112,7 +113,6 @@ The CSP checks the current edition and hardware support (TPM), and returns an er
> This setting is only supported in Windows 10 Mobile. > This setting is only supported in Windows 10 Mobile.
Supported operations are Add, Get, Replace, and Delete. Value type is integer. Supported operations are Add, Get, Replace, and Delete. Value type is integer.
<a href="" id="settings-datarecoverycertificate"></a>**Settings/DataRecoveryCertificate** <a href="" id="settings-datarecoverycertificate"></a>**Settings/DataRecoveryCertificate**
@ -124,7 +124,7 @@ Specifies a recovery certificate that can be used for data recovery of encrypted
DRA information from MDM policy must be a serialized binary blob identical to what we expect from GP. DRA information from MDM policy must be a serialized binary blob identical to what we expect from GP.
The binary blob is the serialized version of following structure: The binary blob is the serialized version of following structure:
``` syntax ```cpp
// //
//  Recovery Policy Data Structures //  Recovery Policy Data Structures
// //
@ -243,7 +243,6 @@ typedef enum _PUBLIC_KEY_SOURCE_TAG {
EfsCertificate, EfsCertificate,
EfsCertificateThumbprint EfsCertificateThumbprint
} PUBLIC_KEY_SOURCE_TAG, *PPUBLIC_KEY_SOURCE_TAG; } PUBLIC_KEY_SOURCE_TAG, *PPUBLIC_KEY_SOURCE_TAG;
``` ```
For EFSCertificate KeyTag, it is expected to be a DER ENCODED binary certificate. For EFSCertificate KeyTag, it is expected to be a DER ENCODED binary certificate.