fixing last note format issues

This commit is contained in:
Liza Poggemeyer
2019-06-07 17:25:05 -07:00
parent 989d59d4b0
commit 169ed2f7da
12 changed files with 16 additions and 26 deletions

View File

@ -43,7 +43,7 @@ Defines restrictions for applications.
Additional information:
- [Find publisher and product name of apps](#productname) - step-by-step guide for getting the publisher and product names for various Windows apps.
- [Whitelist example](#whitelist-example) - example for Windows 10 Mobile that denies all apps except the ones listed.
- [Whitelist example](#whitelist-examples) - example for Windows 10 Mobile that denies all apps except the ones listed.
<a href="" id="enterprisedataprotection"></a>**EnterpriseDataProtection**
Captures the list of apps that are allowed to handle enterprise data. Should be used in conjunction with the settings in **./Device/Vendor/MSFT/EnterpriseDataProtection** in [EnterpriseDataProtection CSP](enterprisedataprotection-csp.md).

View File

@ -1078,7 +1078,7 @@ Specifies the properties of the publisher details.
</tr>
<tr class="even">
<td><p>architectures</p></td>
<td><p>collection of <a href="#productarchitecture" data-raw-source="[ProductArchitecture](#productarchitecture)">ProductArchitecture</a></p></td>
<td><p>collection of <a href="#productarchitectures" data-raw-source="[ProductArchitectures](#productarchitectures)">ProductArchitectures</a></p></td>
</tr>
</tbody>
</table>

View File

@ -41,7 +41,7 @@ Supported operations are Add, Delete, Get and Replace.
The Apps and Settings sections of lockdown XML constitute an Allow list. Any app or setting that is not specified in AssignedAccessXML will not be available on the device to users. The following table describes the entries in lockdown XML.
> [!IMPORTANT]  
> [!IMPORTANT]
> When using the AssignedAccessXml in the EnterpriseAssignedAccess CSP through an MDM, the XML must use escaped characters, such as \< instead of < because it is embedded in an XML. The examples provided in the topic are formatted for readability.
When using the AssignedAccessXml in a provisioning package using the Windows Configuration Designer tool, do not use escaped characters.
@ -518,7 +518,7 @@ Tiles | **Turning-on tile manipulation** - By default, under Assigned Access, ti
The following sample file contains configuration for enabling tile manipulation.
> [!NOTE
> [!NOTE]
> Tile manipulation is disabled when you dont have a `<Tiles>` node in lockdown XML, or if you have a `<Tiles>` node but dont have the `<EnableTileManipulation>` node.
``` syntax
@ -1665,16 +1665,4 @@ The following table lists the product ID and AUMID for each app that is included
<td>Microsoft.XboxApp_8wekyb3d8bbwe!Microsoft.XboxApp</td>
</tr>
</tbody>
</table>
</table>

View File

@ -44,7 +44,7 @@ When a product key is pushed from an MDM server to a user's device, **changepk.e
After the device restarts, the edition upgrade process completes. The user will receive a notification of the successful upgrade.
> [!IMPORTANT]  
> [!IMPORTANT]
> If another policy requires a system reboot that occurs when **changepk.exe** is running, the edition upgrade will fail.
@ -55,7 +55,7 @@ After the device restarts, the edition upgrade process completes. The user will
This node can also be used to activate or change a product key on a particular edition of Windows 10 desktop device by entering a product key. Activation or changing a product key does not require a reboot and is a silent process for the user.
> [!IMPORTANT]  
> [!IMPORTANT]
> The product key entered must be 29 characters (that is, it should include dashes), otherwise the activation, edition upgrade, or product key change on Windows 10 desktop devices will fail. The product key is acquired from Microsoft Volume Licensing Service Center. Your organization must have a Volume Licensing contract with Microsoft to access the portal.
@ -106,7 +106,7 @@ The date type is XML.
The supported operation is Execute.
> [!IMPORTANT]  
> [!IMPORTANT]
> The XML license file contents must be properly escaped (that is, it should not simply be a copied XML), otherwise the edition upgrade on Windows 10 mobile devices will fail. For more information on proper escaping of the XML license file, see Section 2.4 of the [W3C XML spec](http://www.w3.org/TR/xml/) . The XML license file is acquired from the Microsoft Volume Licensing Service Center. Your organization must have a Volume Licensing contract with Microsoft to access the portal.