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

fix: Replace generic "syntax" with language code

Browse Source
This commit is contained in:
Nick Schonning 2019-07-14 00:51:46 -04:00
parent 142f44d70f
commit 04fcf4d3a2
50 changed files with 379 additions and 388 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

322
mdop/uev-v2/application-template-schema-reference-for-ue-v-2x-both-uevv2.md
View File

@ -240,7 +240,7 @@ Version identifies the version of the settings location template for administrat
**Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
``` syntax
```xml
<!--
Version History
@ -279,25 +279,25 @@ Author identifies the creator of the settings location template. Two optional ch
Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
``` syntax
<Process>
<Filename>MyApplication.exe</Filename>
<Architecture>Win64</Architecture>
<ProductName> MyApplication </ProductName>
<FileDescription>MyApplication.exe</FileDescription>
<ProductVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</ProductVersion>
<FileVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</FileVersion>
</Process>
```xml
<Process>
<Filename>MyApplication.exe</Filename>
<Architecture>Win64</Architecture>
<ProductName> MyApplication </ProductName>
<FileDescription>MyApplication.exe</FileDescription>
<ProductVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</ProductVersion>
<FileVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</FileVersion>
</Process>
```
### Filename
@ -354,14 +354,14 @@ UE-V does not support ARM processors in this version.
ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
``` syntax
<Process>
<Filename>MyApplication.exe</Filename>
<ProductName>My Application 6.x by Contoso.com</ProductName>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
```xml
<Process>
<Filename>MyApplication.exe</Filename>
<ProductName>My Application 6.x by Contoso.com</ProductName>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
```
### FileDescription
@ -374,23 +374,22 @@ FileDescription is an optional tag that allows for an administrative description
For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
``` syntax
```xml
<Processes>
<Process>
<Filename>MyApplication.exe</Filename>
<FileDescription>My Application Main Engine</ FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
<Process>
<Filename>MyApplicationHelper.exe</Filename>
<FileDescription>My Application Background Process Executable</FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
<Process>
<Filename>MyApplication.exe</Filename>
<FileDescription>My Application Main Engine</ FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
<Process>
<Filename>MyApplicationHelper.exe</Filename>
<FileDescription>My Application Background Process Executable</FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
</Processes>
```
@ -408,44 +407,44 @@ The product and file version elements may be left unspecified. Doing so makes th
Product version: 1.0 specified in the UE-V Generator produces the following XML:
``` syntax
<ProductVersion>
<Major Minimum="1" Maximum="1" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```xml
<ProductVersion>
<Major Minimum="1" Maximum="1" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```
**Example 2:**
File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
``` syntax
<FileVersion>
<Major Minimum="5" Maximum="5" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="2" Maximum="2" />
<Patch Minimum="1000" Maximum="1000" />
</FileVersion>
```xml
<FileVersion>
<Major Minimum="5" Maximum="5" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="2" Maximum="2" />
<Patch Minimum="1000" Maximum="1000" />
</FileVersion>
```
**Incorrect Example 1 – incomplete range:**
Only the Minimum attribute is present. Maximum must be included in a range as well.
``` syntax
<ProductVersion>
<Major Minimum="2" />
</ProductVersion>
```xml
<ProductVersion>
<Major Minimum="2" />
</ProductVersion>
```
**Incorrect Example 2 – Minor specified without Major element:**
Only the Minor element is present. Major must be included as well.
``` syntax
<ProductVersion>
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```xml
<ProductVersion>
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```
### FileVersion
@ -462,19 +461,19 @@ Including a FileVersion element for an application allows for more granular fine
The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
``` syntax
<Process>
<Filename>MSACCESS.EXE</Filename>
<Architecture>Win32</Architecture>
<ProductVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
<FileVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</FileVersion>
</Process>
```xml
<Process>
<Filename>MSACCESS.EXE</Filename>
<Architecture>Win32</Architecture>
<ProductVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
<FileVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</FileVersion>
</Process>
```
### <a href="" id="application21"></a>Application Element
@ -1177,16 +1176,16 @@ Version identifies the version of the settings location template for administrat
**Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
``` syntax
<!--
Version History
```xml
<!--
Version History
Version 1 Jul 05, 2012 Initial template created by Generator - Denise@Contoso.com
Version 2 Jul 31, 2012 Added support for app.exe v2.1.3 - Mark@Contoso.com
Version 3 Jan 01, 2013 Added font settings support - Mark@Contoso.com
Version 4 Jan 31, 2013 Added support for plugin settings - Tony@Contoso.com
-->
<Version>4</Version>
Version 1 Jul 05, 2012 Initial template created by Generator - Denise@Contoso.com
Version 2 Jul 31, 2012 Added support for app.exe v2.1.3 - Mark@Contoso.com
Version 3 Jan 01, 2013 Added font settings support - Mark@Contoso.com
Version 4 Jan 31, 2013 Added support for plugin settings - Tony@Contoso.com
-->
<Version>4</Version>
```
**Important**  
@ -1216,25 +1215,25 @@ Author identifies the creator of the settings location template. Two optional ch
Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
``` syntax
<Process>
<Filename>MyApplication.exe</Filename>
<Architecture>Win64</Architecture>
<ProductName> MyApplication </ProductName>
<FileDescription>MyApplication.exe</FileDescription>
<ProductVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</ProductVersion>
<FileVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</FileVersion>
</Process>
```xml
<Process>
<Filename>MyApplication.exe</Filename>
<Architecture>Win64</Architecture>
<ProductName> MyApplication </ProductName>
<FileDescription>MyApplication.exe</FileDescription>
<ProductVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</ProductVersion>
<FileVersion>
<Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" />
</FileVersion>
</Process>
```
### Filename
@ -1291,14 +1290,14 @@ UE-V does not support ARM processors in this version.
ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
``` syntax
<Process>
<Filename>MyApplication.exe</Filename>
<ProductName>My Application 6.x by Contoso.com</ProductName>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
```xml
<Process>
<Filename>MyApplication.exe</Filename>
<ProductName>My Application 6.x by Contoso.com</ProductName>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
```
### FileDescription
@ -1311,23 +1310,22 @@ FileDescription is an optional tag that allows for an administrative description
For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
``` syntax
```xml
<Processes>
<Process>
<Filename>MyApplication.exe</Filename>
<FileDescription>My Application Main Engine</ FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
<Process>
<Filename>MyApplicationHelper.exe</Filename>
<FileDescription>My Application Background Process Executable</FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
<Process>
<Filename>MyApplication.exe</Filename>
<FileDescription>My Application Main Engine</ FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
<Process>
<Filename>MyApplicationHelper.exe</Filename>
<FileDescription>My Application Background Process Executable</FileDescription>
<ProductVersion>
<Major Minimum="6" Maximum="6" />
</ProductVersion>
</Process>
</Processes>
```
@ -1345,44 +1343,44 @@ The product and file version elements may be left unspecified. Doing so makes th
Product version: 1.0 specified in the UE-V Generator produces the following XML:
``` syntax
<ProductVersion>
<Major Minimum="1" Maximum="1" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```xml
<ProductVersion>
<Major Minimum="1" Maximum="1" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```
**Example 2:**
File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
``` syntax
<FileVersion>
<Major Minimum="5" Maximum="5" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="2" Maximum="2" />
<Patch Minimum="1000" Maximum="1000" />
</FileVersion>
```xml
<FileVersion>
<Major Minimum="5" Maximum="5" />
<Minor Minimum="0" Maximum="0" />
<Build Minimum="2" Maximum="2" />
<Patch Minimum="1000" Maximum="1000" />
</FileVersion>
```
**Incorrect Example 1 – incomplete range:**
Only the Minimum attribute is present. Maximum must be included in a range as well.
``` syntax
<ProductVersion>
<Major Minimum="2" />
</ProductVersion>
```xml
<ProductVersion>
<Major Minimum="2" />
</ProductVersion>
```
**Incorrect Example 2 – Minor specified without Major element:**
Only the Minor element is present. Major must be included as well.
``` syntax
<ProductVersion>
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```xml
<ProductVersion>
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
```
### FileVersion
@ -1399,19 +1397,19 @@ Including a FileVersion element for an application allows for more granular fine
The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
``` syntax
<Process>
<Filename>MSACCESS.EXE</Filename>
<Architecture>Win32</Architecture>
<ProductVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
<FileVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</FileVersion>
</Process>
```xml
<Process>
<Filename>MSACCESS.EXE</Filename>
<Architecture>Win32</Architecture>
<ProductVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</ProductVersion>
<FileVersion>
<Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" />
</FileVersion>
</Process>
```
### <a href="" id="application"></a>Application Element

5
windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
View File

@ -42,7 +42,7 @@ Before attempting this procedure, you should read and understand the information
2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
``` syntax
```powershell
<#
.SYNOPSIS
This Windows PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats.
@ -59,9 +59,6 @@ Before attempting this procedure, you should read and understand the information
.\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200
#>
[]()
[]()
function ConvertSIDToHexFormat
{
   param([System.Security.Principal.SecurityIdentifier]$sidToConvert)

4
windows/client-management/mdm/activesync-csp.md
View File

@ -60,13 +60,13 @@ When managing over OMA DM, make sure to always use a unique GUID. Provisioning w
Braces { } are required around the GUID. In OMA Client Provisioning, you can type the braces. For example:
``` syntax
```xml
<characteristic type="{C556E16F-56C4-4EDB-9C64-D9469EE1FBE0}"/>
```
For OMA DM, you must use the ASCII values of %7B and %7D for the opening and closing braces, respectively. For example, if the GUID is "C556E16F-56C4-4EDB-9C64-D9469EE1FBE0", type:
``` syntax
```xml
<Target>
<LocURI>
./Vendor/MSFT/ActiveSync/Accounts/%7BC556E16F-56C4-4EDB-9C64-D9469EE1FBE0%7D

4
windows/client-management/mdm/assignedaccess-csp.md
View File

@ -796,7 +796,7 @@ StatusConfiguration Get
StatusConfiguration Replace On
```syntax
```xml
<SyncML xmlns='SYNCML:SYNCML1.2'>
<SyncBody>
<Replace>
@ -1219,7 +1219,7 @@ ShellLauncherConfiguration Get
## AssignedAccessAlert XSD
```syntax
```xml
<?xml version="1.0" encoding="utf-8"?>
<xs:schema
elementFormDefault="qualified"

10
windows/client-management/mdm/certificatestore-csp.md
View File

@ -360,7 +360,7 @@ Supported operations are Add, Get, and Replace.
Add a root certificate to the MDM server.
``` syntax
```xml
<Add>
<CmdID>1</CmdID>
<Item>
@ -379,7 +379,7 @@ Add a root certificate to the MDM server.
Get all installed client certificates.
``` syntax
```xml
<Get>
<CmdID>1</CmdID>
<Item>
@ -394,7 +394,7 @@ Get all installed client certificates.
Delete a root certificate.
``` syntax
```xml
<Delete>
<CmdID>1</CmdID>
<Item>
@ -409,7 +409,7 @@ Delete a root certificate.
Configure the device to enroll a client certificate through SCEP.
``` syntax
```xml
<Atomic>
<CmdID>100</CmdID>
<Add>
@ -588,7 +588,7 @@ Configure the device to enroll a client certificate through SCEP.
Configure the device to automatically renew an MDM client certificate with the specified renew period and retry interval.
``` syntax
```xml
<Atomic>
<CmdID>1</CmdID>
<Replace>

8
windows/client-management/mdm/cm-cellularentries-csp.md
View File

@ -198,7 +198,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
To delete a connection, you must first delete any associated proxies and then delete the connection. The following example shows how to delete the proxy and then the connection.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_ProxyEntries">
<nocharacteristic type="GPRS_Proxy"/>
@ -214,7 +214,7 @@ To delete a connection, you must first delete any associated proxies and then de
Configuring a GPRS connection:
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
<characteristic type="GPRSConn">
@ -231,7 +231,7 @@ Configuring a GPRS connection:
Configuring an LTE connection:
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
<characteristic type="LteConn">
@ -250,7 +250,7 @@ Configuring an LTE connection:
Configuring a CDMA connection:
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
<characteristic type="CDMAConn">

8
windows/client-management/mdm/cmpolicy-csp.md
View File

@ -240,7 +240,7 @@ Specifies the type of connection being referenced. The following list describes
Adding an application-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
@ -285,7 +285,7 @@ Adding an application-based mapping policy. In this example, the ConnectionId fo
Adding a host-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
@ -334,7 +334,7 @@ Adding a host-based mapping policy. In this example, the ConnectionId for type C
Adding an application-based mapping policy:
``` syntax
```xml
<SyncML>
<SyncBody>
<Atomic>
@ -401,7 +401,7 @@ Adding an application-based mapping policy:
Adding a host-based mapping policy:
``` syntax
```xml
<SyncML>
<SyncBody>
<Atomic>

8
windows/client-management/mdm/cmpolicyenterprise-csp.md
View File

@ -240,7 +240,7 @@ Specifies the type of connection being referenced. The following list describes
Adding an application-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
@ -285,7 +285,7 @@ Adding an application-based mapping policy. In this example, the ConnectionId fo
Adding a host-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
@ -334,7 +334,7 @@ Adding a host-based mapping policy. In this example, the ConnectionId for type C
Adding an application-based mapping policy:
``` syntax
```xml
<SyncML>
<SyncBody>
<Atomic>
@ -401,7 +401,7 @@ Adding an application-based mapping policy:
Adding a host-based mapping policy:
``` syntax
```xml
<SyncML>
<SyncBody>
<Atomic>

6
windows/client-management/mdm/customdeviceui-csp.md
View File

@ -38,7 +38,7 @@ Package Full Name of the App that needs be launched in the background. This can
**Set StartupAppID**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -60,7 +60,7 @@ Package Full Name of the App that needs be launched in the background. This can
**Get all background tasks**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Get>
@ -78,7 +78,7 @@ Package Full Name of the App that needs be launched in the background. This can
**Add background task**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Add>

4
windows/client-management/mdm/device-update-management.md
View File

@ -648,7 +648,7 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
Example
``` syntax
```xml
<Replace>
<CmdID>$CmdID$</CmdID>
<Item>
@ -919,7 +919,7 @@ The following screenshots of the administrator console shows the list of update
Set auto update to notify and defer.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Replace xmlns="">

4
windows/client-management/mdm/deviceinstanceservice-csp.md
View File

@ -70,7 +70,7 @@ The parent node to group SIM2 specific information in case of dual SIM mode.
The following sample shows how to query roaming status and phone number on the device.
``` syntax
```xml
<Get>
<CmdID>2</CmdID>
<Item>
@ -88,7 +88,7 @@ The following sample shows how to query roaming status and phone number on the d
Response from the phone.
``` syntax
```xml
<Results>
<CmdID>3</CmdID>
<MsgRef>1</MsgRef>

2
windows/client-management/mdm/devicelock-csp.md
View File

@ -126,7 +126,7 @@ Required. This node has the same set of policy nodes as the **ProviderID** node.
Set device lock policies:
``` syntax
```xml
<Atomic>
<CmdID>13</CmdID>
<Add>

4
windows/client-management/mdm/diagnosticlog-csp.md
View File

@ -420,7 +420,7 @@ Default value is 0 meaning no keyword.
Get provider **Keywords**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Get>
@ -440,7 +440,7 @@ Get provider **Keywords**
Set provider **Keywords**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

2
windows/client-management/mdm/disconnecting-from-mdm-unenrollment.md
View File

@ -105,7 +105,7 @@ After the previous package is sent, the unenrollment process begins.
When the server initiates disconnection, all undergoing sessions for the enrollment ID are aborted immediately to avoid deadlocks. The server will not get a response for the unenrollment, instead a generic alert notification is sent with messageid=1.
``` syntax
```xml
<Alert>
<CmdID>4</CmdID>
<Data>1226</Data>

8
windows/client-management/mdm/dmclient-csp.md
View File

@ -70,7 +70,7 @@ Supported operation is Get.
The following is a Get command example.
``` syntax
```xml
<Get>
<CmdID>12</CmdID>
<Item>
@ -173,7 +173,7 @@ To work around the timeout, you can use this setting to keep the session alive b
Here is an example of DM message sent by the device when it is in pending state:
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncHdr>
<VerDTD>1.2</VerDTD>
@ -229,7 +229,7 @@ Added in Windows 10, version 1607. The list of management server URLs in the fo
``` syntax
```xml
<Replace>
<CmdID>101</CmdID>
<Item>
@ -770,7 +770,7 @@ Note that &lt;LocURI&gt;./Vendor/MSFT/DMClient/Unenroll&lt;/LocURI&gt; is suppor
The following SyncML shows how to remotely unenroll the device. Note that this command should be inserted in the general DM packages sent from the server to the device.
``` syntax
```xml
<Exec>
<CmdID>2</CmdID>
<Item>

10
windows/client-management/mdm/dynamicmanagement-csp.md
View File

@ -29,7 +29,7 @@ The following diagram shows the DynamicManagement configuration service provider
<p style="margin-left: 20px">Default value is False. Supported operations are Get and Replace.</p>
<p style="margin-left: 20px">Example to turn on NotificationsEnabled:</p>
``` syntax
```xml
<Replace>
<CmdID>100</CmdID>
<Item>
@ -84,7 +84,7 @@ The following diagram shows the DynamicManagement configuration service provider
Disable Cortana based on Geo location and time, From 9am-5pm, when in the 100 meters radius of the specified latitude/longitude
``` syntax
```xml
<Replace>
<CmdID>200</CmdID>
<Item>
@ -138,7 +138,7 @@ Disable Cortana based on Geo location and time, From 9am-5pm, when in the 100 me
Disable camera using network trigger with time trigger, from 9-5, when ip4 gateway is 192.168.0.1
``` syntax
```xml
<Replace>
<CmdID>300</CmdID>
<Item>
@ -193,7 +193,7 @@ Disable camera using network trigger with time trigger, from 9-5, when ip4 gatew
Delete a context
``` syntax
```xml
<Delete>
<CmdID>400</CmdID>
<Item>
@ -206,7 +206,7 @@ Delete a context
Get ContextStatus and SignalDefinition from a specific context
``` syntax
```xml
<Get>
<CmdID>400</CmdID>
<Item>

10
windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md
View File

@ -64,7 +64,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
> [!NOTE]
> The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -114,7 +114,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
Here is the snippet from appv.admx:
``` syntax
```xml
<!-- Publishing Server 2 -->
<policy name="Publishing_Server2_Policy" class="Machine" displayName="$(string.PublishingServer2)"
explainText="$(string.Publishing_Server_Help)" presentation="$(presentation.Publishing_Server2)"
@ -206,7 +206,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
Here is the example XML for Publishing_Server2_Policy :
``` syntax
```xml
<data id="Publishing_Server2_Name_Prompt" value="Name"/>
<data id="Publishing_Server_URL_Prompt" value="http://someuri"/>
<data id="Global_Publishing_Refresh_Options" value="1"/>
@ -226,7 +226,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
> [!NOTE]
> The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
``` syntax
```xml
<?xml version="1.0" encoding="utf-8"?>
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
@ -264,7 +264,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
The \<Data> payload is \<disabled/>. Here is an example to disable AppVirtualization/PublishingAllowServer2.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

2
windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md
View File

@ -275,7 +275,7 @@ After the installation of updates is completed, the IT Admin can use the DURepor
<a href="" id="example-script"></a>
## Example PowerShell script
``` syntax
```powershell
param (
# [Parameter (Mandatory=$true, HelpMessage="Input File")]
[String]$inputFile,

58
windows/client-management/mdm/enterprise-app-management.md
View File

@ -78,7 +78,7 @@ Note that performing a full inventory of a device can be resource intensive on t
Here is an example of a query for all apps on the device.
``` syntax
```xml
<!-- Get all apps under AppManagement -->
<Get>
<CmdID>1</CmdID>
@ -92,7 +92,7 @@ Here is an example of a query for all apps on the device.
Here is an example of a query for a specific app for a user.
``` syntax
```xml
<!-- Get all information of a specific app for a user -->
<Get>
<CmdID>1</CmdID>
@ -121,7 +121,7 @@ For detailed descriptions of each node, see [EnterpriseModernAppManagement CSP](
Here is an example of a query for all app licenses on a device.
``` syntax
```xml
<!-- Get all app licenses for the device -->
<Get>
<CmdID>1</CmdID>
@ -135,7 +135,7 @@ Here is an example of a query for all app licenses on a device.
Here is an example of a query for all app licenses for a user.
``` syntax
```xml
<!-- Get a specific app license for a user -->
<Get>
<CmdID>1</CmdID>
@ -161,7 +161,7 @@ For more information about the AllowAllTrustedApps policy, see [Policy CSP](poli
Here are some examples.
``` syntax
```xml
<!-- Get policy (Default)-->
<Get>
<CmdID>1</CmdID>
@ -199,7 +199,7 @@ For more information about the AllowDeveloperUnlock policy, see [Policy CSP](pol
Here is an example.
``` syntax
```xml
<!-- Get policy (Default)-->
<Get>
<CmdID>1</CmdID>
@ -244,7 +244,7 @@ Here are the requirements for this scenario:
Here are some examples.
``` syntax
```xml
<Exec>
<CmdID>1</CmdID>
<Item>
@ -281,7 +281,7 @@ In the SyncML, you need to specify the following information in the Exec command
Here is an example of an offline license installation.
``` syntax
```xml
<Exec>
<CmdID>1</CmdID>
<Item>
@ -315,7 +315,7 @@ The Add command for the package family name is required to ensure proper removal
Here is an example of a line-of-business app installation.
``` syntax
```xml
<!-- Add PackageFamilyName -->
<Add>
<CmdID>0</CmdID>
@ -342,7 +342,7 @@ Here is an example of a line-of-business app installation.
Here is an example of an app installation with dependencies.
``` syntax
```xml
<!-- Add PackageFamilyName -->
<Add>
<CmdID>0</CmdID>
@ -376,7 +376,7 @@ Here is an example of an app installation with dependencies.
Here is an example of an app installation with dependencies and optional packages.
``` syntax
```xml
<!-- Add PackageFamilyName -->
<Add>
<CmdID>0</CmdID>
@ -438,7 +438,7 @@ Here is an example of app installation.
> **Note**  This is only supported in Windows 10 for desktop editions.
``` syntax
```xml
<!-- Add PackageFamilyName -->
<Add>
<CmdID>0</CmdID>
@ -475,7 +475,7 @@ Here is an example of app installation with dependencies.
> **Note**  This is only supported in Windows 10 for desktop editions.
``` syntax
```xml
<!-- Add PackageFamilyName -->
<Add>
<CmdID>0</CmdID>
@ -526,7 +526,7 @@ When an app is installed successfully, the node is cleaned up and no longer pres
Here is an example of a query for a specific app installation.
``` syntax
```xml
<!-- Get all app status under AppInstallation for a specific app-->
<Get>
<CmdID>2</CmdID>
@ -540,7 +540,7 @@ Here is an example of a query for a specific app installation.
Here is an example of a query for all app installations.
``` syntax
```xml
<!-- Get all app status under AppInstallation-->
<Get>
<CmdID>2</CmdID>
@ -558,7 +558,7 @@ Application installations can take some time to complete, hence they are done as
Here is an example of an alert.
``` syntax
```xml
<Alert>
<CmdID>4</CmdID>
<Data>1226</Data>
@ -594,7 +594,7 @@ To uninstall an app, you delete it under the origin node, package family name, a
Here is an example for uninstalling all versions of an app for a user.
``` syntax
```xml
<!-- Uninstall App for a Package Family-->
<Delete>
<CmdID>1</CmdID>
@ -608,7 +608,7 @@ Here is an example for uninstalling all versions of an app for a user.
Here is an example for uninstalling a specific version of the app for a user.
``` syntax
```xml
<!-- Uninstall App for a specific package full name-->
<Delete>
<CmdID>1</CmdID>
@ -631,7 +631,7 @@ Removing provisioned app occurs in the device context.
Here is an example for removing a provisioned app from a device.
``` syntax
```xml
<!— Remove Provisioned App for a Package Family-->
<Delete>
<CmdID>1</CmdID>
@ -645,7 +645,7 @@ Here is an example for removing a provisioned app from a device.
Here is an example for removing a specific version of a provisioned app from a device:
``` syntax
```xml
<!-- Remove Provisioned App for a specific package full name-->
<Delete>
<CmdID>1</CmdID>
@ -663,7 +663,7 @@ You can remove app licenses from a device per app based on the content ID.
Here is an example for removing an app license for a user.
``` syntax
```xml
<!-- Remove App License for a User-->
<Delete>
<CmdID>1</CmdID>
@ -677,7 +677,7 @@ Here is an example for removing an app license for a user.
Here is an example for removing an app license for a provisioned package (device context).
``` syntax
```xml
<!-- Remove App License for a provisioned package (device) -->
<Delete>
<CmdID>1</CmdID>
@ -697,7 +697,7 @@ For user-based uninstallation, use ./User in the LocURI, and for provisioning, u
Here is an example. There is only one uninstall for hosted and store apps.
``` syntax
```xml
<Alert>
<Data>1226</Data>
<Item>
@ -723,7 +723,7 @@ To update an app from Microsoft Store, the device requires contact with the stor
Here is an example of an update scan.
``` syntax
```xml
<!— Initiate a update scan for a user-->
<Exec>
<CmdID>1</CmdID>
@ -737,7 +737,7 @@ Here is an example of an update scan.
Here is an example of a status check.
``` syntax
```xml
<!— Get last error related to the update scan-->
<Get>
<CmdID>1</CmdID>
@ -766,7 +766,7 @@ Turning off updates only applies to updates from the Microsoft Store at the devi
Here is an example.
``` syntax
```xml
<!— Prevent app from being automatically updated-->
<Replace>
<CmdID>1</CmdID>
@ -795,7 +795,7 @@ You can install app on non-system volumes, such as a secondary partition or remo
Here is an example.
``` syntax
```xml
<!-- Get policy (Default)-->
<Get>
<CmdID>1</CmdID>
@ -832,7 +832,7 @@ The RestrictAppDataToSystemVolume policy in [Policy CSP](policy-configuration-se
Here is an example.
``` syntax
```xml
<!-- Get policy (Default)-->
<Get>
<CmdID>1</CmdID>
@ -873,7 +873,7 @@ The valid values are 0 (off, default value) and 1 (on).
Here is an example.
``` syntax
```xml
<!-- Get policy (Default)-->
<Get>
<CmdID>1</CmdID>

2
windows/client-management/mdm/enterpriseapn-csp.md
View File

@ -132,7 +132,7 @@ The following image shows the EnterpriseAPN configuration service provider in tr
## Examples
``` syntax
```xml
<!--
Copyright (c) Microsoft Corporation. All rights reserved.
-->

16
windows/client-management/mdm/enterpriseappmanagement-csp.md
View File

@ -209,7 +209,7 @@ The Microsoft Store application has a GUID of d5dc1ebb-a7f1-df11-9264-00237de2db
Use the following SyncML format to query to see if the application is installed on a managed device:
``` syntax
```xml
<Get>
<CmdID>1</CmdID>
<Item>
@ -222,7 +222,7 @@ Use the following SyncML format to query to see if the application is installed
Response from the device (it contains list of subnodes if this app is installed in the device).
``` syntax
```xml
<Results>
<CmdID>3</CmdID>
<MsgRef>1</MsgRef>
@ -266,7 +266,7 @@ The value actually applied to the device can be queried via the nodes under the
Enroll enterprise ID “4000000001” for the first time:
``` syntax
```xml
<Add>
<CmdID>2</CmdID>
<Item>
@ -293,7 +293,7 @@ Enroll enterprise ID “4000000001” for the first time:
Update the enrollment token (for example, to update an expired application enrollment token):
``` syntax
```xml
<Replace>
<CmdID>2</CmdID>
<Item>
@ -310,7 +310,7 @@ Update the enrollment token (for example, to update an expired application enrol
Query all installed applications that belong to enterprise id “4000000001”:
``` syntax
```xml
<Get>
<CmdID>2</CmdID>
<Item>
@ -325,7 +325,7 @@ Query all installed applications that belong to enterprise id “4000000001”:
Response from the device (that contains two installed applications):
``` syntax
```xml
<Results>
<CmdID>3</CmdID>
<MsgRef>1</MsgRef>
@ -444,7 +444,7 @@ To perform an XAP update, create the Name, URL, Version, and DownloadInstall nod
``` syntax
```xml
<Atomic>
<CmdID>2</CmdID>
<!-- The Add command can be used if the download node does not have a matching product ID
@ -514,7 +514,7 @@ To perform an XAP update, create the Name, URL, Version, and DownloadInstall nod
Uninstall an installed enterprise application with product ID “{7BB316008A-141D-4A79-810F-8B764C4CFDFB }”:
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Delete>

46
windows/client-management/mdm/enterpriseassignedaccess-csp.md
View File

@ -61,7 +61,7 @@ Application | <img src="images/enterpriseassignedaccess-csp.png" alt="modern app
Application | Include PinToStart to display an app on the Start screen. For apps pinned to the Start screen, identify a tile size (small, medium, or large), and a location. The size of a small tile is 1 column x 1 row, a medium tile is 2 x 2, and a large tile is 4 x 2. For the tile location, the first value indicates the column and the second value indicates the row. A value of 0 (zero) indicates the first column, a value of 1 indicates the second column, and so on. Include autoRun as an attribute to configure the application to run automatically.
Application example:
``` syntax
```xml
<Application productId="{2A4E62D8-8809-4787-89F8-69D0F01654FB}" autoRun="true">
<PinToStart>
<Size>Large</Size>
@ -78,7 +78,7 @@ Entry | Description
Application | Multiple App Packages enable multiple apps to exist inside the same package. Since ProductIds identify packages and not applications, specifying a ProductId is not enough to distinguish between individual apps inside a multiple app package. Trying to include application from a multiple app package with just a ProductId can result in unexpected behavior. To support pinning applications in multiple app packages, use an AUMID parameter in lockdown XML. For the list of product ID and AUMID, see [ProductIDs in Windows 10 Mobile](#productid). The following example shows how to pin both Outlook mail and Outlook calendar.
Application example:
``` syntax
```xml
<Apps>
<!-- Outlook Calendar -->
<Application productId="{A558FEBA-85D7-4665-B5D8-A2FF9C19799B}"
@ -110,7 +110,7 @@ Entry | Description
Folder | A folder should be contained in `<Applications/>` node among with other `<Application/>` nodes, it shares most grammar with the Application Node, **folderId** is mandatory, **folderName** is optional, which is the folder name displayed on Start. **folderId** is a unique unsigned integer for each folder.
Folder example:
``` syntax
```xml
<Application folderId="4" folderName="foldername">
<PinToStart>
<Size>Large</Size>
@ -123,7 +123,7 @@ Folder example:
```
An application that belongs in the folder would add an optional attribute **ParentFolderId**, which maps to **folderId** of the folder. In this case, the location of this application will be located inside the folder.
``` syntax
```xml
<Application productId="{2A4E62D8-8809-4787-89F8-69D0F01654FB}">
<PinToStart>
<Size>Medium</Size>
@ -252,7 +252,7 @@ For example, in place of SettingPageDisplay, you would use ms-settings:display.
Here is an example for Windows 10, version 1703.
``` syntax
```xml
<Settings>
<System name="ms-settings:display"/>
<System name="ms-settings:appsforwebsites"/>
@ -327,14 +327,14 @@ Starting in Windows 10, version 1703, Quick action settings no longer require an
In this example, all settings pages and quick action settings are allowed. An empty \<Settings> node indicates that none of the settings are blocked.
``` syntax
```xml
<Settings>
</Settings>
```
In this example for Windows 10, version 1511, all System setting pages are enabled. Note that the System page group is added as well as all of the System subpage names.
``` syntax
```xml
<Settings>
<System name="SettingsPageGroupPCSystem" />
<System name="SettingsPageDisplay" />
@ -350,7 +350,7 @@ In this example for Windows 10, version 1511, all System setting pages are ena
```
Here is an example for Windows 10, version 1703.
``` syntax
```xml
<Settings>
<System name="ms-settings:display"/>
<System name="ms-settings:appsforwebsites"/>
@ -382,7 +382,7 @@ Buttons | The following list identifies the hardware buttons on the device that
> Custom buttons are hardware buttons that can be added to devices by OEMs.
Buttons example:
``` syntax
```xml
<Buttons>
<ButtonLockdownList>
<!-- Lockdown all buttons -->
@ -407,7 +407,7 @@ The Search and custom buttons can be <em>remapped</em> or configured to open a s
To remap a button in lockdown XML, you supply the button name, the button event (typically "press"), and the product ID for the application the button will open.
``` syntax
```xml
<ButtonRemapList>
<Button name="Search">
<ButtonEvent name="Press">
@ -503,7 +503,7 @@ MenuItems | Use **DisableMenuItems** to prevent use of the context menu, which i
MenuItems example:
``` syntax
```xml
<MenuItems>
<DisableMenuItems/>
</MenuItems>
@ -1196,7 +1196,7 @@ The XML examples in this section show how to perform various tasks by using OMA
The following example shows how to add a new policy.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="EnterpriseAssignedAccess">
<characteristic type="AssignedAccess">
@ -1211,7 +1211,7 @@ The following example shows how to add a new policy.
The following example shows how to specify the language to display on the device.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="EnterpriseAssignedAccess">
<characteristic type="Language">
@ -1230,7 +1230,7 @@ These XML examples show how to perform various tasks using OMA DM.
The following example shows how to lock down a device.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Add>
@ -1251,7 +1251,7 @@ The following example shows how to lock down a device.
The following example shows how to change the accent color to one of the standard colors.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -1274,7 +1274,7 @@ The following example shows how to change the accent color to one of the standar
The following example shows how to change the theme.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -1297,7 +1297,7 @@ The following example shows how to change the theme.
The following example shows how to set a custom theme accent color for the enterprise environment.
``` syntax
```xml
<SyncBody>
<Replace>
<CmdID>1</CmdID>
@ -1333,7 +1333,7 @@ The following example shows how to set a custom theme accent color for the enter
Use the examples in this section to set a new lock screen and manage the lock screen features. If using a UNC path, format the LocURI as \\\\host\\share\\image.jpg.
``` syntax
```xml
<Add>
<CmdID>2</CmdID>
<Item>
@ -1351,7 +1351,7 @@ Use the examples in this section to set a new lock screen and manage the lock sc
The following example shows how to query the device for the file being used as the lock screen.
``` syntax
```xml
<Get>
<CmdID>2</CmdID>
<Item>
@ -1364,7 +1364,7 @@ The following example shows how to query the device for the file being used as t
The following example shows how to change the existing lock screen image to one of your choosing.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -1389,7 +1389,7 @@ The following example shows how to change the existing lock screen image to one
The following example shows how to set the time zone to UTC-07 Mountain Time (US & Canada).
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -1411,7 +1411,7 @@ The following example shows how to set the time zone to UTC-07 Mountain Time (US
The following example shows how to set the time zone to Pacific Standard Time (UTC-08:00) without observing daylight savings time (UTC+01:00).
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -1435,7 +1435,7 @@ The following example shows how to set the time zone to Pacific Standard Time (U
The following example shows how to set the language.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

34
windows/client-management/mdm/enterprisedesktopappmanagement-csp.md
View File

@ -54,20 +54,14 @@ In Windows 10, version 1703 service release, a new tag \<DownloadFromAad\> was a
Here is an example:
```syntax
<Enforcement>
<CommandLine>/quiet</CommandLine>
<TimeOut>5</TimeOut>
<RetryCount>3</RetryCount>
<RetryInterval>5</RetryInterval>
<DownloadFromAad>1</DownloadFromAad>
</Enforcement>
```xml
<Enforcement>
<CommandLine>/quiet</CommandLine>
<TimeOut>5</TimeOut>
<RetryCount>3</RetryCount>
<RetryInterval>5</RetryInterval>
<DownloadFromAad>1</DownloadFromAad>
</Enforcement>
```
<a href="" id="msi-productid-status"></a>**MSI/*ProductID*/Status**
@ -112,7 +106,7 @@ Value type is string. Supported operation is Get.
**SyncML to request CSP version information**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Get>
@ -140,7 +134,7 @@ The following table describes the fields in the previous sample:
**SyncML to perform MSI operations for application uninstall**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Delete>
@ -168,7 +162,7 @@ The following table describes the fields in the previous sample:
**SyncML to perform MSI operations for application status reporting**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Get>
@ -196,7 +190,7 @@ The following table describes the fields in the previous sample:
**SyncML to perform MSI install operations for an application targeted to a specific user on the device. The Add command is required to preceed the Exec command.**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Add>
@ -290,7 +284,7 @@ The following table describes the fields in the previous sample:
**SyncML to perform MSI install operations for an application targeted to all users on the device (per-device installation)**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Add>
@ -540,7 +534,7 @@ Here's a list of references:
## Alert example
``` syntax
```xml
<Alert>
<CmdID>4</CmdID>
<Data>1224</Data>

6
windows/client-management/mdm/enterpriseextfilessystem-csp.md
View File

@ -70,7 +70,7 @@ Supported operations is Get.
The following example shows how to retrieve a file from the device.
``` syntax
```xml
<Get>
<CmdID>2</CmdID>
<Item>
@ -83,7 +83,7 @@ The following example shows how to retrieve a file from the device.
The following example shows the file name that is returned in the body of the response syncML code. In this example, the full path of the file on the device is C:/data/test/bin/filename.txt.
``` syntax
```xml
<Results>
<CmdID>3</CmdID>
<MsgRef>1</MsgRef>
@ -103,7 +103,7 @@ The following example shows the file name that is returned in the body of the re
The following example shows how to push a file to the device.
``` syntax
```xml
<Add>
<CmdID>2</CmdID>
<Item>

15
windows/client-management/mdm/enterprisemodernappmanagement-csp.md
View File

@ -52,7 +52,7 @@ Supported operation is Get.
Here's an example of AppInventoryResults operation.
``` syntax
```xml
<Get>
<CmdID>11</CmdID>
<Item>
@ -100,7 +100,7 @@ Supported operation is Get and Replace.
The following example sets the inventory query for the package names and checks the status for reinstallation for all main packages that are nonStore apps.
``` syntax
```xml
<Replace>
<CmdID>10</CmdID>
<Item>
@ -208,7 +208,7 @@ Supported operations are Get and Delete.
Here's an example for uninstalling an app:
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<!-- Uninstall app -->
@ -345,7 +345,7 @@ Value type is string. Supported operations are Add, Get, Replace, and Delete.
The following example sets the value for the 'Server'
``` syntax
```xml
<!— Configure app settings -->
<Add>
<CmdID>0</CmdID>
@ -363,7 +363,7 @@ The following example sets the value for the 'Server'
The following example gets all managed app settings for a specific app.
``` syntax
```xml
<!—Get app settings -->
<Get>
<CmdID>0</CmdID>
@ -583,7 +583,7 @@ For examples of how to use this CSP to for reporting apps inventory, installatio
Query the device for a specific app subcategory, such as nonStore apps.
``` syntax
```xml
<Get>
<CmdID>1</CmdID>
<Item>
@ -598,8 +598,7 @@ The result contains a list of apps, such as \<Data>App1/App2/App\</Data\>.
Subsequent query for a specific app for its properties.
``` syntax
```xml
<Get>
<CmdID>1</CmdID>
<Item>

12
windows/client-management/mdm/federated-authentication-device-enrollment.md
View File

@ -92,7 +92,7 @@ https://EnterpriseEnrollment.Contoso.com/EnrollmentServer/Discovery.svc
The following example shows the discovery service request.
``` syntax
```xml
<?xml version="1.0"?>
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:s="http://www.w3.org/2003/05/soap-envelope">
@ -198,7 +198,7 @@ The server has to send a POST to a redirect URL of the form ms-app://string (the
The following example shows a response received from the discovery web service which requires authentication via WAB.
``` syntax
```xml
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
@ -252,7 +252,7 @@ wsse:BinarySecurityToken/attributes/EncodingType: The &lt;wsse:BinarySecurityTok
The following is an enrollment policy request example with a received security token as client credential.
``` syntax
```xml
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@ -305,7 +305,7 @@ MS-XCEP supports very flexible enrollment policies using various Complex Types a
The following snippet shows the policy web service response.
``` syntax
```xml
<s:Envelope
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:s="http://www.w3.org/2003/05/soap-envelope"
@ -399,7 +399,7 @@ The RST may also specify a number of AdditionalContext items, such as DeviceType
The following example shows the enrollment web service request for federated authentication.
``` syntax
```xml
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@ -505,7 +505,7 @@ Here is a sample RSTR message and a sample of OMA client provisioning XML within
The following example shows the enrollment web service response.
``` syntax
```xml
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

2
windows/client-management/mdm/hotspot-csp.md
View File

@ -134,7 +134,7 @@ Changes to this node require a reboot.
For CDMA networks that use a separate Network Access Identity (NAI) for Internet sharing, a new parm, TetheringNAI, has been added in the [CM\_CellularEntries configuration service provider](cm-cellularentries-csp.md) configuration service provider. The following sample demonstrates how to specify the connection.
``` syntax
```xml
<wap-provisioningdoc>
<characteristic type="CM_CellularEntries">
<characteristic type="TetheringNAIConn">

2
windows/client-management/mdm/implement-server-side-mobile-application-management.md
View File

@ -59,7 +59,7 @@ Below are protocol changes for MAM enrollment: 
Here is an example provisioning XML for MAM enrollment.
``` syntax
```xml
<wap-provisioningdoc version="1.1">
<characteristic type="APPLICATION">
<parm name="APPID" value="w7"/>

4
windows/client-management/mdm/maps-csp.md
View File

@ -126,7 +126,7 @@ Here is a list of GUIDs of the most downloaded reqions.
Here is an example queuing a map package of New York for download.
``` syntax
```xml
<SyncML>
<SyncBody>
<Add>
@ -144,7 +144,7 @@ Here is an example queuing a map package of New York for download.
Here is an example that gets the status of the New York map package on the device.
``` syntax
```xml
<SyncML>
<SyncBody>
<Get>

2
windows/client-management/mdm/messaging-csp.md
View File

@ -55,7 +55,7 @@ The following diagram shows the Messaging configuration service provider in tree
**SyncML example**
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

4
windows/client-management/mdm/mobile-device-enrollment.md
View File

@ -103,7 +103,7 @@ To manually trigger enrollment migration, you can run MDMMaintenenceTask.
The enrollment server can decline enrollment messages using the SOAP Fault format. Errors created can be sent as follows:
``` syntax
```xml
<s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:header>
<a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>
@ -200,7 +200,7 @@ The enrollment server can decline enrollment messages using the SOAP Fault forma
In Windows 10, version 1507, we added the deviceenrollmentserviceerror element. Here is an example:
``` syntax
```xml
<s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:header>
<a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>

8
windows/client-management/mdm/multisim-csp.md
View File

@ -74,7 +74,7 @@ Supported operation is Get and Replace. Value type is bool.
## Examples
Get modem
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Get>
@ -93,7 +93,7 @@ Get modem
```
Get slots
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Get>
@ -112,7 +112,7 @@ Get slots
```
Get slot state
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Get>
@ -131,7 +131,7 @@ Get slot state
```
Select slot
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

4
windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
View File

@ -1660,7 +1660,7 @@ The software version information from **DevDetail/SwV** does not match the versi
Applies only to phone prior to build 10586.218: When ApplicationManagement/ApplicationRestrictions policy is deployed to Windows 10 Mobile, installation and update of apps dependent on Microsoft Frameworks may get blocked with error 0x80073CF9. To work around this issue, you must include the Microsoft Framework Id to your list of allowed apps.
``` syntax
```xml
<App ProductId="{00000000-0000-0000-0000-000000000000}" PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
```
@ -1709,7 +1709,7 @@ The following XML sample explains the properties for the EAP TLS XML including c
>For PEAP or TTLS Profiles the EAP TLS XML is embedded within some PEAP or TTLS specific elements.
``` syntax
```xml
<EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig">
<EapMethod>
<Type xmlns="http://www.microsoft.com/provisioning/EapCommon">13</Type>

16
windows/client-management/mdm/nodecache-csp.md
View File

@ -19,7 +19,7 @@ The NodeCache configuration service provider is used to manage the client cache.
NodeCache supports the comparison of hash values instead of actual node values:
``` syntax
```xml
<Type xmlns="syncml:metinf">
application/x-nodemon-sha256
</type>
@ -76,7 +76,7 @@ Supported operations are Get, Add, and Delete.
Here's an example for setting the ExpectedValue to nonexistent.
``` syntax
```xml
<Add>
<CmdID>10</CmdID>
<Item>
@ -146,7 +146,7 @@ Supported operations are Add, Get, and Delete.
Creating settings for node caching:
``` syntax
```xml
<Add>
<CmdID>2</CmdID>
<Item>
@ -222,7 +222,7 @@ Creating settings for node caching:
Getting nodes under Provider ID MDMSRV1, cache version, changed nodes, node, expected value:
``` syntax
```xml
<Get>
<CmdID>18</CmdID>
<Item>
@ -267,7 +267,7 @@ Getting nodes under Provider ID MDMSRV1, cache version, changed nodes, node, exp
Replacing the cache version, node URI, and expected value:
``` syntax
```xml
<Replace>
<CmdID>2</CmdID>
<Item>
@ -299,7 +299,7 @@ Replacing the cache version, node URI, and expected value:
For AutoSetExpectedValue, a Replace operation with empty data will query the ./DevDetail/Ext/Microsoft/DeviceName.
```syntax
```xml
<Add>
<CmdID>2001</CmdID>
<Item>
@ -335,12 +335,12 @@ A Get operation on ./Vendor/MSFT/NodeCache/MDM%20SyncML%20Server/Nodes/20/Expect
A Get operation on the ChangedNodesData returns an encoded XML. Here is example:
```syntax
```xml
<Nodes><Node Id="10" Uri=""></Node><Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node></Nodes>
```
It represents this:
```syntax
```xml
<Nodes>
<Node Id="10" Uri=""></Node>
<Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node>

6
windows/client-management/mdm/office-csp.md
View File

@ -67,7 +67,7 @@ The only supported operation is Get.
Sample SyncML to install Office 365 Business Retail from current channel.
```syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Exec>
@ -89,7 +89,7 @@ Sample SyncML to install Office 365 Business Retail from current channel.
To uninstall the Office 365 from the system:
```syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Exec>
@ -111,7 +111,7 @@ To uninstall the Office 365 from the system:
To get the current status of Office 365 on the device.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
  <SyncBody>
    <Get>

12
windows/client-management/mdm/on-premise-authentication-device-enrollment.md
View File

@ -86,7 +86,7 @@ https://EnterpriseEnrollment.Contoso.com/EnrollmentServer/Discovery.svc
The following example shows the discovery service request.
``` syntax
```xml
<?xml version="1.0"?>
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:s="http://www.w3.org/2003/05/soap-envelope">
@ -134,7 +134,7 @@ The discovery response is in the XML format and includes the following fields:
The following example shows a response received from the discovery web service for OnPremise authentication:
``` syntax
```xml
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
@ -171,7 +171,7 @@ For the OnPremise authentication policy, the UsernameToken in GetPolicies contai
The following example shows the policy web service request.
``` syntax
```xml
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@ -219,7 +219,7 @@ MS-XCEP supports very flexible enrollment policies using various Complex Types a
The following snippet shows the policy web service response.
``` syntax
```xml
<s:Envelope
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:s="http://www.w3.org/2003/05/soap-envelope"
@ -311,7 +311,7 @@ The RST may also specify a number of AdditionalContext items, such as DeviceType
The following example shows the enrollment web service request for OnPremise authentication.
``` syntax
```xml
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@ -396,7 +396,7 @@ The following example shows the enrollment web service request for OnPremise aut
The following example shows the enrollment web service response.
``` syntax
```xml
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:a="http://www.w3.org/2005/08/addressing"
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

2
windows/client-management/mdm/passportforwork-csp.md
View File

@ -273,7 +273,7 @@ Value type is string. Supported operations are Add, Get, Replace, and Delete.
Here's an example for setting Windows Hello for Business and setting the PIN policies. It also turns on the use of biometrics and TPM.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Add>

2
windows/client-management/mdm/personalization-csp.md
View File

@ -71,7 +71,7 @@ The following diagram shows the Personalization configuration service provider i
## Example SyncML
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

4
windows/client-management/mdm/policy-configuration-service-provider.md
View File

@ -5456,7 +5456,7 @@ The following diagram shows the Policy configuration service provider in tree fo
Set the minimum password length to 4 characters.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>
@ -5478,7 +5478,7 @@ Set the minimum password length to 4 characters.
Do not allow NFC.
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Replace>

6
windows/client-management/mdm/policy-csp-applicationmanagement.md
View File

@ -594,7 +594,7 @@ List of semi-colon delimited Package Family Names of Windows apps. Listed Window
For this policy to work, the Windows apps need to declare in their manifest that they will use the start up task. Example of the declaration here:
``` syntax
```xml
<desktop:Extension Category="windows.startupTask">
<desktop:StartupTask TaskId="CoffeeStartupTask" Enabled="true" DisplayName="ms-resource:Description" />
</desktop:Extension>
@ -972,7 +972,7 @@ Value type is string.
<!--Example-->
Sample SyncML:
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
<Add>
@ -999,7 +999,7 @@ Sample SyncML:
```
XSD:
``` syntax
```xml
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:simpleType name="recurrence" final="restriction">
<xs:restriction base="xs:string">

10
windows/client-management/mdm/policy-csp-deviceinstallation.md
View File

@ -121,7 +121,7 @@ ADMX Info:
To enable this policy, use the following SyncML. This example allows Windows to install compatible devices with a device ID of USB\Composite or USB\Class_FF. To configure multiple classes, use `&#xF000;` as a delimiter.
``` syntax
```xml
<SyncML>
<SyncBody>
<Replace>
@ -238,7 +238,7 @@ To enable this policy, use the following SyncML. This example allows Windows to
Enclose the class GUID within curly brackets {}. To configure multiple classes, use `&#xF000;` as a delimiter.
``` syntax
```xml
<SyncML>
<SyncBody>
<Replace>
@ -417,7 +417,7 @@ ADMX Info:
To enable this policy, use the following SyncML. This example prevents Windows from installing devices that are not specifically described by any other policy setting.
``` syntax
```xml
<SyncML>
<SyncBody>
<Replace>
@ -519,7 +519,7 @@ ADMX Info:
To enable this policy, use the following SyncML. This example prevents Windows from installing compatible devices with a device ID of USB\Composite or USB\Class_FF. To configure multiple classes, use <code>&amp;#xF000;</code> as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_IDs_Deny_Retroactive to true.
``` syntax
```xml
<SyncML>
<SyncBody>
<Replace>
@ -626,7 +626,7 @@ To enable this policy, use the following SyncML. This example prevents Windows f
Enclose the class GUID within curly brackets {}. To configure multiple classes, use `&#xF000;` as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_Classes_Deny_Retroactive to true.
``` syntax
```xml
<SyncML>
<SyncBody>
<Replace>

2
windows/client-management/mdm/policy-csp-internetexplorer.md
View File

@ -2249,7 +2249,7 @@ ADMX Info:
<!--/ADMXBacked-->
<!--Example-->
```syntax
```xml
<SyncBody>
<Replace>
<CmdID>2</CmdID>

2
windows/client-management/mdm/policy-csp-restrictedgroups.md
View File

@ -76,7 +76,7 @@ Caution: If a Restricted Groups policy is applied, any current member not on the
Starting in Windows 10, version 1809, you can use this schema for retrieval and application of the RestrictedGroups/ConfigureGroupMembership policy. A minimum occurrence of 0 members when applying the policy implies clearing the access group and should be used with caution.
``` syntax
```xml
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0">
<xs:simpleType name="member_name">
<xs:restriction base="xs:string">

2
windows/client-management/mdm/policy-csp-userrights.md
View File

@ -20,7 +20,7 @@ User rights are assigned for user accounts or groups. The name of the policy def
Here is an example syncml for setting the user right BackupFilesAndDirectories for Administrators and Authenticated Users groups.
```syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>

2
windows/client-management/mdm/policy-csp-windowslogon.md
View File

@ -305,7 +305,7 @@ If you disable or don't configure this policy setting, any user can disconnect t
Here is an example to enable this policy:
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Atomic>

2
windows/client-management/mdm/registry-ddf-file.md
View File

@ -17,7 +17,7 @@ ms.date: 06/26/2017
This topic shows the OMA DM device description framework (DDF) for the **Registry** configuration service provider. DDF files are used only with OMA DM provisioning XML.
``` syntax
```xml
<MgmtTree xmlns:MSFT="http://schemas.microsoft.com/MobileDevice/DM">
<VerDTD>1.2</VerDTD>
<Node>

2
windows/client-management/mdm/remotefind-csp.md
View File

@ -102,7 +102,7 @@ Supported operation is Get.
## Examples
``` syntax
```xml
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncBody>
<Atomic>

47
windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md
View File

@ -97,7 +97,7 @@ The BitLocker Network Unlock feature will install the WDS role if it is not alre
To install the role using Windows PowerShell, use the following command:
``` syntax
```powershell
Install-WindowsFeature WDS-Deployment
```
@ -109,7 +109,7 @@ To confirm the WDS service is running, use the Services Management Console or Wi
To confirm the service is running using Windows PowerShell, use the following command:
``` syntax
```powershell
Get-Service WDSServer
```
### <a href="" id="bkmk-installnufeature"/>Install the Network Unlock feature
@ -118,7 +118,7 @@ To install the Network Unlock feature, use Server Manager or Windows PowerShell.
To install the feature using Windows PowerShell, use the following command:
``` syntax
```powershell
Install-WindowsFeature BitLocker-NetworkUnlock
```
### <a href="" id="bkmk-createcerttmpl"/>Create the certificate template for Network Unlock
@ -184,7 +184,7 @@ To create a self-signed certificate, you can either use the New-SelfSignedCertif
Windows PowerShell example:
```syntax
```powershell
New-SelfSignedCertificate -CertStoreLocation Cert:\LocalMachine\My -Subject "CN=BitLocker Network Unlock certificate" -Provider "Microsoft Software Key Storage Provider" -KeyUsage KeyEncipherment -KeyUsageProperty Decrypt,Sign -KeyLength 2048 -HashAlgorithm sha512 -TextExtension @("1.3.6.1.4.1.311.21.10={text}OID=1.3.6.1.4.1.311.67.1.1","2.5.29.37={text}1.3.6.1.4.1.311.67.1.1")
```
@ -193,7 +193,7 @@ Certreq example:
1. Create a text file with an .inf extension. For example, notepad.exe BitLocker-NetworkUnlock.inf.
2. Add the following contents to the previously created file:
``` syntax
```ini
[NewRequest]
Subject="CN=BitLocker Network Unlock certificate"
ProviderType=0
@ -267,24 +267,27 @@ The configuration file, called bde-network-unlock.ini, must be located in the sa
The subnet policy configuration file must use a “\[SUBNETS\]” section to identify the specific subnets. The named subnets may then be used to specify restrictions in certificate subsections. Subnets are defined as simple name-value pairs, in the common INI format, where each subnet has its own line, with the name on the left of the equals sign, and the subnet identified on the right of the equal sign as a Classless Inter-Domain Routing (CIDR) address or range. The key word “ENABLED” is disallowed for subnet names.
[SUBNETS]
SUBNET1=10.185.250.0/24 ; comment about this subrange could be here, after the semi-colon
SUBNET2=10.185.252.200/28
SUBNET3= 2001:4898:a:2::/64 ; an IPv6 subnet
SUBNET4=2001:4898:a:3::/64; in production, the admin would likely give more useful names, like BUILDING9-EXCEPT-RECEP.
```
Following the \[SUBNETS\] section, there can be sections for each Network Unlock certificate, identified by the certificate thumbprint formatted without any spaces, which define subnets clients can be unlocked from with that certificate.
```ini
[SUBNETS]
SUBNET1=10.185.250.0/24 ; comment about this subrange could be here, after the semi-colon
SUBNET2=10.185.252.200/28
SUBNET3= 2001:4898:a:2::/64 ; an IPv6 subnet
SUBNET4=2001:4898:a:3::/64; in production, the admin would likely give more useful names, like BUILDING9-EXCEPT-RECEP.
```
Following the \[SUBNETS\] section, there can be sections for each Network Unlock certificate, identified by the certificate thumbprint formatted without any spaces, which define subnets clients can be unlocked from with that certificate.
>**Note:**  When specifying the certificate thumbprint, do not include any spaces. If spaces are included in the thumbprint the subnet configuration will fail because the thumbprint will not be recognized as valid.
Subnet restrictions are defined within each certificate section by denoting the allowed list of permitted subnets. If any subnet is listed in a certificate section, then only those subnets listed are permitted for that certificate. If no subnet is listed in a certificate section, then all subnets are permitted for that certificate. If a certificate does not have a section in the subnet policy configuration file, then no subnet restrictions are applied for unlocking with that certificate. This means for restrictions to apply to every certificate, there must be a certificate section for every Network Unlock certificate on the server, and an explicit allowed list set for each certificate section.
Subnet lists are created by putting the name of a subnet from the \[SUBNETS\] section on its own line below the certificate section header. Then, the server will only unlock clients with this certificate on the subnet(s) specified as in the list. For troubleshooting, a subnet can be quickly excluded without deleting it from the section by simply commenting it out with a prepended semi-colon.
[‎2158a767e1c14e88e27a4c0aee111d2de2eafe60]
;Comments could be added here to indicate when the cert was issued, which Group Policy should get it, and so on.
;This list shows this cert is only allowed to unlock clients on SUBNET1 and SUBNET3 subnets. In this example, SUBNET2 is commented out.
SUBNET1
;SUBNET2
SUBNET3
>**Note:**  When specifying the certificate thumbprint, do not include any spaces. If spaces are included in the thumbprint the subnet configuration will fail because the thumbprint will not be recognized as valid.
Subnet restrictions are defined within each certificate section by denoting the allowed list of permitted subnets. If any subnet is listed in a certificate section, then only those subnets listed are permitted for that certificate. If no subnet is listed in a certificate section, then all subnets are permitted for that certificate. If a certificate does not have a section in the subnet policy configuration file, then no subnet restrictions are applied for unlocking with that certificate. This means for restrictions to apply to every certificate, there must be a certificate section for every Network Unlock certificate on the server, and an explicit allowed list set for each certificate section.
Subnet lists are created by putting the name of a subnet from the \[SUBNETS\] section on its own line below the certificate section header. Then, the server will only unlock clients with this certificate on the subnet(s) specified as in the list. For troubleshooting, a subnet can be quickly excluded without deleting it from the section by simply commenting it out with a prepended semi-colon.
```ini
[‎2158a767e1c14e88e27a4c0aee111d2de2eafe60]
;Comments could be added here to indicate when the cert was issued, which Group Policy should get it, and so on.
;This list shows this cert is only allowed to unlock clients on SUBNET1 and SUBNET3 subnets. In this example, SUBNET2 is commented out.
SUBNET1
;SUBNET2
SUBNET3
```
To disallow the use of a certificate altogether, its subnet list may contain the line “DISABLED".

2
windows/security/threat-protection/microsoft-defender-atp/pull-alerts-using-rest-api.md
View File

@ -173,7 +173,7 @@ Here is an example return value:
### Get access token
The following code example demonstrates how to obtain an access token and call the Microsoft Defender ATP API.
```syntax
```csharp
AuthenticationContext context = new AuthenticationContext(string.Format("https://login.windows.net/{0}/oauth2", tenantId));
ClientCredential clientCredentials = new ClientCredential(clientId, clientSecret);
AuthenticationResult authenticationResult = context.AcquireToken(resource, clientCredentials);

12
windows/security/threat-protection/microsoft-defender-atp/python-example-code.md
View File

@ -39,7 +39,7 @@ The following example demonstrates how to obtain an Azure AD access token that y
Replace the *auth_url*, *client_id*, and *client_secret* values with the ones you got from **Settings** page in the portal:
```
```python
import json
import requests
from pprint import pprint
@ -62,7 +62,7 @@ token = json.loads(response.text)["access_token"]
## Step 2: Create request session object
Add HTTP headers to the session object, including the Authorization header with the token that was obtained.
```
```python
with requests.Session() as session:
session.headers = {
'Authorization': 'Bearer {}'.format(token),
@ -74,7 +74,7 @@ with requests.Session() as session:
## Step 3: Create calls to the custom threat intelligence API
After adding HTTP headers to the session object, you can now create calls to the API. The following example demonstrates how you can view all the alert definition entities:
```
```python
response = session.get("https://ti.securitycenter.windows.com/V1.0/AlertDefinitions")
pprint(json.loads(response.text))
```
@ -85,7 +85,7 @@ The response is empty on initial use of the API.
## Step 4: Create a new alert definition
The following example demonstrates how you to create a new alert definition.
```
```python
alert_definition = {"Name": "The alert's name",
"Severity": "Low",
"InternalDescription": "An internal description of the alert",
@ -104,7 +104,7 @@ The following example demonstrates how you to create a new alert definition.
## Step 5: Create a new indicator of compromise
You can now use the alert ID obtained from creating a new alert definition to create a new indicator of compromise.
```
```python
alert_definition_id = json.loads(response.text)["Id"]
ioc = {'Type': "Sha1",
@ -121,7 +121,7 @@ You can now use the alert ID obtained from creating a new alert definition to cr
## Complete code
You can use the complete code to create calls to the API.
```syntax
```python
import json
import requests
from pprint import pprint