From 554f99075b691297cfe9bb0025855bd92c4e3605 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Fri, 7 Jun 2019 16:23:24 -0700 Subject: [PATCH] fixing appv and mdm note issues --- .../app-v/appv-release-notes-for-appv-for-windows.md | 2 +- windows/client-management/mdm/cm-cellularentries-csp.md | 4 ++-- .../mdm/mdm-enrollment-of-windows-devices.md | 3 ++- windows/client-management/troubleshoot-windows-freeze.md | 2 +- 4 files changed, 6 insertions(+), 5 deletions(-) diff --git a/windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md b/windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md index e4d37b5628..daf1783e49 100644 --- a/windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md +++ b/windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md @@ -137,7 +137,7 @@ The InsertVersionInfo.sql script is not required for versions of the App-V manag The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340). -> [!IMPORTANT]  +> [!IMPORTANT] > **Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3. ## Microsoft Visual Studio 2012 not supported diff --git a/windows/client-management/mdm/cm-cellularentries-csp.md b/windows/client-management/mdm/cm-cellularentries-csp.md index c8ece4bfd6..1fbb4940fd 100644 --- a/windows/client-management/mdm/cm-cellularentries-csp.md +++ b/windows/client-management/mdm/cm-cellularentries-csp.md @@ -139,7 +139,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid **IPType**

Optional. Type: String. Specifies the network protocol of the connection. Available values are "IPv4", "IPv6", "IPv4v6", and "IPv4v6xlat". If a value is not specified, the default value is "IPv4". -> [!WARNING]   +> [!WARNING] > Do not use IPv6 or IPv4v6xlat on a device or network that does not support IPv6. Data functionality will not work. In addition, the device will not be able to connect to a roaming network that does not support IPv6 unless you configure roaming connections with an IPType of IPv4v6. @@ -149,7 +149,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid

To allow MMS when data is set to OFF, set both ExemptFromDisablePolicy and UseRequiresMappingsPolicy to "1". This indicates that the connection is a dedicated MMS connection and that it should not be disabled when all other connections are disabled. As a result, MMS can be sent and received when data is set to OFF. Note that sending MMS while roaming is still not allowed. -> [!IMPORTANT]   +> [!IMPORTANT] > Do not set ExemptFromDisablePolicy to "1", ExemptFromRoaming to "1", or UseRequiresMappingsPolicy to "1" for general purpose connections.

To avoid UX inconsistency with certain value combinations of ExemptFromDisablePolicy and AllowMmsIfDataIsOff, when you do not set ExemptFromDisablePolicy to 1 (default is 0), you should: diff --git a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md index 60126c6e01..5c703305c7 100644 --- a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md +++ b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md @@ -364,7 +364,8 @@ Starting in Windows 10, version 1709, clicking the **Info** button will show a l ![work or school info](images/unifiedenrollment-rs1-35-b.png) -> [Note] Starting in Windows 10, version 1709, the **Manage** button is no longer available. +> [NOTE] +> Starting in Windows 10, version 1709, the **Manage** button is no longer available. ### Disconnect diff --git a/windows/client-management/troubleshoot-windows-freeze.md b/windows/client-management/troubleshoot-windows-freeze.md index d2e65aa3e8..c8c41b271b 100644 --- a/windows/client-management/troubleshoot-windows-freeze.md +++ b/windows/client-management/troubleshoot-windows-freeze.md @@ -97,7 +97,7 @@ If the computer is no longer frozen and now is running in a good state, use the 3. In the **Write Debugging Information** section, select **Complete Memory Dump**. - > [!NOTE] + > [!NOTE] > For Windows versions that are earlier than Windows 8 or Windows Server 2012, the Complete Memory Dump type isn't available in the GUI. You have to change it in Registry Editor. To do this, change the value of the following **CrashDumpEnabled** registry entry to **1** (REG_DWORD): >**HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\CrashDumpEnabled**