Merge pull request #6519 from MicrosoftDocs/main

1/11/2021 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -1082,6 +1082,11 @@
             "source_path": "memdocs/configmgr/develop/core/understand/sqlviews/reports-supplied-with-configuration-manager.md",
             "redirect_url": "/mem/configmgr/core/servers/manage/list-of-reports",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "memdocs/configmgr/core/plan-design/hierarchy/state-messaging-system-center-configuration-manager.md",
+            "redirect_url": "/mem/configmgr/core/plan-design/hierarchy/state-messages",
+            "redirect_document_id": true
         }
     ]
 }

memdocs/configmgr/comanage/quickstart-paths.md

@@ -48,6 +48,8 @@ For a tutorial on this path, see [Tutorial: Enable co-management for existing Co
 
 ## <a name="bkmk_path2"></a> Path 2: Bootstrap with modern provisioning
 
+This path is for those devices that are first enrolled with Intune. They are cloud-first devices and use Intune to install the Configuration Manager client.
+
 Here's what you need to set it up:
 
 1. [Setup enhanced HTTP](../core/plan-design/hierarchy/enhanced-http.md)  

memdocs/configmgr/core/TOC.yml

@@ -488,7 +488,7 @@ items:
     - name: Release notes
       href: servers/deploy/install/release-notes.md
     - name: State messages
-      href: plan-design/hierarchy/state-messaging-system-center-configuration-manager.md   
+      href: plan-design/hierarchy/state-messages.md
     - name: Unicode and ASCII support
       href: plan-design/hierarchy/unicode-and-ascii-support.md
 - name: Manage infrastructure

memdocs/configmgr/core/clients/deploy/about-client-settings.md

@@ -2,7 +2,7 @@
 title: Client settings
 titleSuffix: Configuration Manager
 description: Learn about the default and custom settings for controlling client behaviors
-ms.date: 01/05/2022
+ms.date: 01/11/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: reference
@@ -676,7 +676,7 @@ _Applies to version 2103 and later_
 
 Enable this option for Software Center to use the Microsoft Edge WebView2 browser control. The WebView2 browser control provides improved security and user experience. For example, more websites should work with these custom tabs without displaying script errors or security warnings.
 
-If it's not already installed, the Configuration Manager client installs the **Microsoft Edge WebView2 runtime (fixed version)** on the device.
+If it's not already installed, the Configuration Manager client installs the **Microsoft Edge WebView2 runtime (fixed version)** on the device. Clients download the WebView2 redistributable installation file from the management point. The installer is over 100 MB in size. If you need to enable this setting on a large number of clients, and are concerned about the effect of network usage, predeploy the WebView2 runtime as an application. Use the software distribution features of Configuration Manager to better control the content distribution and timing of software installation.<!-- 12769440 -->
 
 > [!NOTE]
 > - If the client device isn't running .NET Framework version 4.6.2 or later, it falls back to use the Internet Explorer browser control. Starting in version 2107, the client requires .NET version 4.6.2, and version 4.8 is recommended.<!--10402814--> For more information, see [Prerequisites for deploying clients to Windows computers](prerequisites-for-deploying-clients-to-windows-computers.md#more-details-about-microsoft-net).

memdocs/configmgr/core/plan-design/hierarchy/client-peer-cache.md

@@ -48,7 +48,7 @@ To enable peer cache, deploy the [client settings](#client-settings) to a collec
 - A client that operates as a peer content source submits a list of available cached content to its management point using state messages. A peer content source client also sends a state message to the management point when it removes content from its local cache.
 
   > [!NOTE]
-  > For the list of applicable peer content source state messages, see [State messages in Configuration Manager](state-messaging-system-center-configuration-manager.md#7200-state_topictype_super_peer_update_cache_map). Specifically those with state message IDs of 7200, 7201, 7202, and 7203.
+  > For the list of applicable peer content source state messages, see [State messages in Configuration Manager](state-messages.md#7200-state_topictype_super_peer_update_cache_map). Specifically those with state message IDs of 7200, 7201, 7202, and 7203.
 
 - Another client in the same boundary group makes a content location request to the management point. The server returns the list of potential content sources. This list includes each peer cache source that has the content and is online. It also includes the distribution points and other content source locations in that boundary group. For more information, see [Content source priority](fundamental-concepts-for-content-management.md#content-source-priority).