Merge branch 'main' into patch-46

Author: lenewsad

memdocs/autopilot/known-issues.md

@@ -12,7 +12,7 @@ author: aczechowski
 ms.author: aaroncz
 ms.reviewer: jubaptis
 manager: dougeby
-ms.date: 12/08/2021
+ms.date: 03/28/2022
 ms.collection: M365-modern-desktop
 ms.topic: troubleshooting
 ---
@@ -28,6 +28,14 @@ This article describes known issues that can often be resolved by configuration
 
 ## Known issues
 
+### `DefaultuserX` profile not deleted
+
+When using the [EnableWebSignIn CSP](/windows/client-management/mdm/policy-csp-authentication#authentication-enablewebsignin), the `defaultuserX` profile may not be deleted. This CSP isn't currently supported. It's in private preview mode only and not recommended for production purposes at this time.
+
+### Autopilot reset ran into trouble. Could not find the recovery environment
+
+When attempting an Autopilot reset, an administrator sees the following message: _Autopilot reset ran into trouble. Could not find the recovery environment_. If there isn't an issue with the recovery environment, enter administrator credentials to continue with the reset process.
+
 ### Device-based Conditional Access policies
 
 1. The Intune Enrollment app must be excluded from any Conditional Access policy requiring **Terms of Use** because it isn’t supported.  See [Per-device terms of use](/azure/active-directory/conditional-access/terms-of-use#per-device-terms-of-use).

memdocs/configmgr/core/plan-design/hierarchy/ports.md

@@ -2,7 +2,7 @@
 title: Ports used for connections
 titleSuffix: Configuration Manager
 description: Learn about the required and customizable network ports that Configuration Manager uses for connections.
-ms.date: 02/16/2022
+ms.date: 04/01/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: reference
@@ -141,6 +141,7 @@ For more information, see [CMG data flow](../../clients/manage/cmg/data-flow.md)
 |DHCP|67 and 68|--|
 |TFTP|69 <sup>[Note 4](#bkmk_note4)</sup> |--|
 |Boot Information Negotiation Layer (BINL)|4011|--|
+|DHCPv6 for PXE responder without WDS |547|--|
 
 > [!IMPORTANT]
 > If you enable a host-based firewall, make sure that the rules allow the server to send and receive on these ports. When you enable a distribution point for PXE, Configuration Manager can enable the inbound (receive) rules on the Windows Firewall. It doesn't configure the outbound (send) rules.<!--SCCMDocs issue #744-->
@@ -370,6 +371,15 @@ A distribution point communicates to the management point in the following scena
 |-----------------|---------|---------|
 |HTTPS|--|443|
 
+### <a name="BKMK_PortsPullDP-DPSource"></a> Pull-Distribution point `-->` Distribution point configured as source
+
+|Description|UDP|TCP|
+|-----------------|---------|---------|
+|HTTP|--|80 <sup>[Note 2](#bkmk_note2) Alternate port available</sup>|
+|HTTPS|--|443 <sup>[Note 2](#bkmk_note2) Alternate port available</sup>|
+|Express updates|--|8005 <sup>[Note 2](#bkmk_note2) Alternate port available</sup><!-- SCCMDocs#2091 -->|
+
+
 ### <a name="BKMK_PortsRSP-SQL"></a> Reporting Services point `-->` SQL Server
 
 |Description|UDP|TCP|

memdocs/configmgr/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md

@@ -2,7 +2,7 @@
 title: Prepare to use an availability group
 titleSuffix: Configuration Manager
 description: Plan to use a SQL Server Always On availability group for the Configuration Manager site database.
-ms.date: 06/15/2021
+ms.date: 03/25/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -359,6 +359,8 @@ You don't need to make any changes to the configuration when adding a secondary
 
 When a site database uses an availability group, run the built-in **Backup Site server** maintenance task to back up common Configuration Manager settings and files. Don't use the MDF or LDF files created by that backup. Instead, make direct backups of these database files by using SQL Server.
 
+You can still use the SQL Server back up, however you can't restore it directly to a SQL Server Always On cluster. You need to restore it on a standalone server and move it back to SQL Server Always On.
+
 ### Transaction log
 
 Set the recovery model of the site database to **Full**. This configuration is a requirement for Configuration Manager use in an availability group. Plan to monitor and maintain the size of the site database transaction log. In the full recovery model, the transactions aren't hardened until it makes a full backup of the database or transaction log. For more information, see [Back up and restore of SQL Server databases](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases).

memdocs/configmgr/core/servers/deploy/configure/troubleshoot-microsoft-connected-cache.md

@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 # Troubleshoot Microsoft Connected Cache in Configuration Manager
 
-This article provides technical details about Microsoft Connected Cache in Configuration Manager. Use it to help troubleshoot issues that you may have in your environment. For more information on how it works and how to use it, see [Microsoft Connected Cache in Configuration Manager](../../../plan-design/hierarchy/microsoft-connected-cache.md).
+This article provides technical details about Microsoft Connected Cache in Configuration Manager. Use it to help troubleshoot issues that you might have in your environment. For more information on how it works and how to use it, see [Microsoft Connected Cache in Configuration Manager](../../../plan-design/hierarchy/microsoft-connected-cache.md).
 
 ## Verify
 
@@ -24,95 +24,92 @@ Verify this behavior [on a client](#verify-on-a-client) or [on the server](#veri
 
 ### Verify on a client
 
-1. On client running a supported version of Windows 10 or later, download cloud-managed content. For more information on the types of content that Connected Cache supports, see [Supported content types](../../../plan-design/hierarchy/microsoft-connected-cache.md#supported-content-types).
-
-2. Open PowerShell and run the following command: `Get-DeliveryOptimizationStatus`
-
-For example:
-
-```PowerShell
-PS C:\> Get-DeliveryOptimizationStatus
-
-FileId                      : ec523d49c4f7c3c4444f0d9b952286ce40fdcee4
-FileSize                    : 549064
-TotalBytesDownloaded        : 549064
-PercentPeerCaching          : 0
-BytesFromPeers              : 0
-BytesFromHttp               : 0
-Status                      : Caching
-Priority                    : Background
-BytesFromCacheServer        : 549064
-BytesFromLanPeers           : 0
-BytesFromGroupPeers         : 0
-BytesFromInternetPeers      : 0
-BytesToLanPeers             : 0
-BytesToGroupPeers           : 0
-BytesToInternetPeers        : 0
-DownloadDuration            : 00:00:00.0780000
-HttpConnectionCount         : 2
-LanConnectionCount          : 0
-GroupConnectionCount        : 0
-InternetConnectionCount     : 0
-DownloadMode                : 99
-SourceURL                   : http://au.download.windowsupdate.com/c/msdownload/update/software/defu/2019/09/am_delta_p
-                              atch_1.301.664.0_ec523d49c4f7c3c4444f0d9b952286ce40fdcee4.exe
-NumPeers                    : 0
-PredefinedCallerApplication : WU Client Download
-ExpireOn                    : 9/6/2019 8:36:19 AM
-IsPinned                    : False
-```
+1. On a client running a supported version of Windows 10 or later, download cloud-managed content. For more information on the types of content that Connected Cache supports, see [Supported content types](../../../plan-design/hierarchy/microsoft-connected-cache.md#supported-content-types).
+
+1. Open PowerShell and run the following command: `Get-DeliveryOptimizationStatus`.
+
+    For example:
+
+    ```PowerShell
+    PS C:\> Get-DeliveryOptimizationStatus
+
+    FileId                      : ec523d49c4f7c3c4444f0d9b952286ce40fdcee4
+    FileSize                    : 549064
+    TotalBytesDownloaded        : 549064
+    PercentPeerCaching          : 0
+    BytesFromPeers              : 0
+    BytesFromHttp               : 0
+    Status                      : Caching
+    Priority                    : Background
+    BytesFromCacheServer        : 549064
+    BytesFromLanPeers           : 0
+    BytesFromGroupPeers         : 0
+    BytesFromInternetPeers      : 0
+    BytesToLanPeers             : 0
+    BytesToGroupPeers           : 0
+    BytesToInternetPeers        : 0
+    DownloadDuration            : 00:00:00.0780000
+    HttpConnectionCount         : 2
+    LanConnectionCount          : 0
+    GroupConnectionCount        : 0
+    InternetConnectionCount     : 0
+    DownloadMode                : 99
+    SourceURL                   : http://au.download.windowsupdate.com/c/msdownload/update/software/defu/2019/09/am_delta_p
+                                atch_1.301.664.0_ec523d49c4f7c3c4444f0d9b952286ce40fdcee4.exe
+    NumPeers                    : 0
+    PredefinedCallerApplication : WU Client Download
+    ExpireOn                    : 9/6/2019 8:36:19 AM
+    IsPinned                    : False
+    ```
 
 Notice that the `BytesFromCacheServer` attribute isn't zero.
 
-If the client isn't configured correctly, or the cache server isn't installed correctly, the Delivery Optimization client falls back to the original cloud source. Then the BytesFromCacheServer attribute will be zero.
+If the client isn't configured correctly, or the cache server isn't installed correctly, the Delivery Optimization client falls back to the original cloud source. Then the `BytesFromCacheServer` attribute will be zero.
 
 ### Verify on the server
 
-First, verify the registry properties are configured correctly: `HKLM\SOFTWARE\Microsoft\Delivery Optimization In-Network Cache`. For example, the drive cache location is `PrimaryDrivesInput\DOINC-E77D08D0-5FEA-4315-8C95-10D359D59294`, where `PrimaryDrivesInput` can be multiple drives such as `C,D,E`.
+First, verify the registry properties are configured correctly: `HKLM\SOFTWARE\Microsoft\Delivery Optimization In-Network Cache`. For example, the drive cache location is `PrimaryDrivesInput\DOINC-E77D08D0-5FEA-4315-8C95-10D359D59294`, where `PrimaryDrivesInput` can be multiple drives, such as `C,D,E`.
 
 Next, use the following method to simulate a client download request to the server with the mandatory headers.
 
 1. Open a 64-bit PowerShell window as an administrator.
-2. Run the following command, and replace the name or IP address of your server for `<DoincServer>`:
+1. Run the following command, and replace the name or IP address of your server for `<DoincServer>`:
 
-```PowerShell
-Invoke-WebRequest -URI "http://<DoincServer>/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
-```
+    ```PowerShell
+    Invoke-WebRequest -URI "http://<DoincServer>/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
+    ```
 
-The output looks similar to the following example:
+    The output looks similar to the following example:
 
-```PowerShell
-PS C:\WINDOWS\system32> Invoke-WebRequest -URI "http://SERVER01.CONTOSO.COM/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
+    ```PowerShell
+    PS C:\WINDOWS\system32> Invoke-WebRequest -URI "http://SERVER01.CONTOSO.COM/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
 
 
-StatusCode        : 200
-StatusDescription : OK
-Content           : {71, 73, 70, 56...}
-RawContent        : HTTP/1.1 200 OK
-                    X-HW: 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.at2
-                    .p,1567797125.cds058.se2.p
-                    X-CCC: cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwv...
-Headers           : {[X-HW, 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.a
-                    t2.p,1567797125.cds058.se2.p], [X-CCC,
-                    cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwvtSBQdT3uPQ5ikBe1ABMbdYIIncem+h5dtcLI6GY=],
-                    [X-CID, 100], [Accept-Ranges, bytes]...}
-RawContentLength  : 969710
-```
+    StatusCode        : 200
+    StatusDescription : OK
+    Content           : {71, 73, 70, 56...}
+    RawContent        : HTTP/1.1 200 OK
+                        X-HW: 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.at2
+                        .p,1567797125.cds058.se2.p
+                        X-CCC: cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwv...
+    Headers           : {[X-HW, 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.a
+                        t2.p,1567797125.cds058.se2.p], [X-CCC,
+                        cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwvtSBQdT3uPQ5ikBe1ABMbdYIIncem+h5dtcLI6GY=],
+                        [X-CID, 100], [Accept-Ranges, bytes]...}
+    RawContentLength  : 969710
+    ```
 
-The following attributes indicate success:
+    The following attributes indicate success:
 
-- `StatusCode : 200`
-- `StatusDescription : OK`
+    - `StatusCode : 200`
+    - `StatusDescription : OK`
 
 ## Log files
 
-- ARR setup log: `%temp%\arr_setup.log`
-
-- Connected Cache server setup log: `SMS_DP$\Ms.Dsp.Do.Inc.Setup\DoincSetup.log` on the distribution point, and `DistMgr.log` on the site server
-
-- IIS operational logs: By default, `%SystemDrive%\inetpub\logs\LogFiles`
-
-- Connected Cache server operational log: `C:\Doinc\Product\Install\Logs`
+- **Application Request Routing (ARR) setup log**: `%temp%\arr_setup.log`
+- **Connected Cache server setup log**: `SMS_DP$\Ms.Dsp.Do.Inc.Setup\DoincSetup.log` on the distribution point and `DistMgr.log` on the site server
+- **Internet Information Services (IIS) operational logs**: By default, `%SystemDrive%\inetpub\logs\LogFiles`
+- **Connected Cache server operational log**: `C:\Doinc\Product\Install\Logs`
 
     > [!TIP]
     > Among other uses, this log can help you identify connectivity issues with the Microsoft cloud.
@@ -168,15 +165,15 @@ When Configuration Manager installs the Connected Cache component on the distrib
 
 ## IIS configurations
 
-The Connected Cache server install makes several modifications to the IIS configuration on the distribution point.
+The Connected Cache server installation makes several modifications to the IIS configuration on the distribution point.
 
 ### Application request routing
 
-The Connected Cache server installs and configures IIS [Application Request Routing (ARR)](https://www.iis.net/downloads/microsoft/application-request-routing). To avoid potential conflicts, the distribution point can't already have this component installed.
+The Connected Cache server installs and configures IIS [Application Request Routing](https://www.iis.net/downloads/microsoft/application-request-routing). To avoid potential conflicts, the distribution point can't already have this component installed.
 
 ### Allowed server variables
 
-After you install the Connected Cache server, the default web site has the following *local* server variables:
+After you install the Connected Cache server, the default website has the following *local* server variables:
 
 - HTTP_HOST
 - QUERY_STRING
@@ -218,20 +215,20 @@ To change the custom header name for each server farm:
 
 1. Open IIS Manager.
 1. Select **Server Farms**.
-1. Select a server farm and the proxy icon. 
+1. Select a server farm and the proxy icon.
 1. Under **Custom Headers**, change the value `X-Forwarded-For` to `X-Forwarded-For-<custom-name>`.
 
 ## Manage server resources
 
-Disk space required for each Connected Cache server may vary, based on your organization's update requirements. 100 GB should be enough space to cache the following content:
+Disk space required for each Connected Cache server might vary, based on your organization's update requirements. Disk space of 100 GB should be enough to cache the following content:
 
 - A feature update
 - Two to three months of quality and Microsoft 365 Apps updates
 - Microsoft Intune apps and Windows inbox apps
 
 The Connected Cache server shouldn't consume much system memory or processor time. After you install the Connected Cache server, if you notice significant process or memory resource consumption, analyze the IIS and ARR log files.
 
-If the IIS and ARR log files take up too much space on the server, there are several methods you can use to manage the log files. For more information, see [Managing IIS Log File Storage](/iis/manage/provisioning-and-managing-iis/managing-iis-log-file-storage#overview).
+If the IIS and ARR log files take up too much space on the server, there are several methods you can use to manage the log files. For more information, see [Managing IIS log file storage](/iis/manage/provisioning-and-managing-iis/managing-iis-log-file-storage#overview).
 
 ## See also
 

memdocs/configmgr/core/understand/software-center.md

@@ -197,6 +197,9 @@ Specify how Software Center applies changes to software before the deadline.
 
 - **Suspend Software Center activities when my computer is in presentation mode**: This setting is enabled by default.
 
+> [!NOTE]
+> These settings are designed to be managed by end users and do not impact deployment deadlines.
+
 When instructed by your IT admin, select **Sync Policy**. This computer checks with the servers for anything new, such as applications, software updates, or operating systems.
 
 ### Remote Control

memdocs/configmgr/desktop-analytics/overview.md

@@ -106,10 +106,10 @@ To use Desktop Analytics, make sure your environment meets the following prerequ
   > - Use different Commercial IDs and Azure AD tenants.
   > - Configure both hierarchies to use the same Commercial ID to share the Azure AD tenant and Desktop Analytics instance. Use [different apps](connect-configmgr.md#bkmk_connect) for connecting each hierarchy. It may take up to 30 days after you disconnect a hierarchy for the portal to reflect changes.
 
-- Devices running Windows 7, Windows 8.1, or Windows 10.
+- Devices running Windows 10.
 
     > [!IMPORTANT]
-    > Starting in July 2021, Desktop Analytics supports the Windows diagnostic data processor configuration. This configuration is only for supported versions of Windows 10. Data for Windows 7, Windows 8, and earlier versions of Windows 10 will only show in Desktop Analytics until January 31, 2022. For more information, see [Support for the Windows diagnostic data processor configuration](whats-new.md#support-for-the-windows-diagnostic-data-processor-configuration).<!-- 10220671 -->
+    > Starting in July 2021, Desktop Analytics supports the Windows diagnostic data processor configuration. This configuration is only for supported versions of Windows 10. For more information, see [Support for the Windows diagnostic data processor configuration](whats-new.md#support-for-the-windows-diagnostic-data-processor-configuration).<!-- 10220671 -->
     >
     > Desktop Analytics doesn't support Windows 11.<!-- 10797955 --> For information about Windows 11 hardware readiness, Microsoft recommends that you enable tenant attach and [Endpoint analytics](../../analytics/overview.md).