Merge pull request #7123 from MicrosoftDocs/main

Publish 03/25/2022 3:30 PM PT

Author: Angela Fleischmann

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

@@ -370,6 +370,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/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/intune/fundamentals/what-is-intune.md

@@ -108,13 +108,9 @@ Intune integrates with Azure AD to enable a broad set of access control scenario
 
 ## How to get Intune
 
-Intune is available:
+There are many ways to get Intune. For more information, see [Licenses available for Microsoft Intune](licenses.md).
 
-- As a stand-alone [Azure service](https://go.microsoft.com/fwlink/?linkid=2090973)
-- Included with [Microsoft 365](https://www.microsoft.com/microsoft-365/enterprise-mobility-security/microsoft-intune) and [Microsoft 365 government](https://www.microsoft.com/microsoft-365/government)
-- As [Mobile Device Management in Microsoft 365](https://support.office.com/article/Set-up-Mobile-Device-Management-MDM-in-Office-365-dd892318-bc44-4eb1-af00-9db5430be3cd), which consists of some limited Intune features
-
-Intune is used in many sectors, including [government](/enterprise-mobility-security/solutions/ems-govt-service-description), [education](https://www.microsoft.com/en-us/education/intune), [kiosk or dedicated device](../configuration/kiosk-settings.md) for manufacturing and retail, and more.
+Intune is used in many sectors, including [government](/enterprise-mobility-security/solutions/ems-govt-service-description), [education](https://www.microsoft.com/education/intune), [kiosk or dedicated device](../configuration/kiosk-settings.md) for manufacturing and retail, and more.
 
 ## Next steps
 

memdocs/intune/fundamentals/whats-new.md

@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 03/23/2022
+ms.date: 03/25/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -150,28 +150,6 @@ For more information on these policy types, see:
 Applies to:
 - Windows 10/11
 
-#### Endpoint security profiles support filters; See the filter status on a device configuration profile report<!-- 11889620 -->
-There are some new features when using filters:
-- When you create a device configuration profile for Windows devices, a per-policy report shows reporting information in the **Device and user check-in status** (**Devices** > **Configuration profiles** > *Select an existing policy*).
-
-  When you select **View report**, the report has an **Assignment Filter** column. Use this column to determine if a filter successfully applied to your policy.
-
-- Endpoint Security policies support filters. So, when you assign an endpoint security policy, you can use filters to assign the policy based on rules you create.
-
-- When you create a new endpoint security policy, it automatically uses the [new device configuration profile reporting](#new-reporting-experience-for-device-configuration-profiles). When you look at the per-policy report, it also has an **Assignment Filter** column (**Devices** > **Configuration profiles** > *Select an existing endpoint security policy* > **View report**). Use this column to determine if a filter successfully applied to your policy.
-
-For more information on filters, see:
-- [Use filters when assigning your apps, policies, and profiles](filters.md)
-- [List of platforms, policies, and app types supported by filters](filters-supported-workloads.md)
-
-Applies to:
-- All platforms
-
-Does not apply to:
-- Administrative Templates (Windows 10/11)
-- Device Firmware Configuration Interface (DFCI) (Windows 10/11)
-- OEMConfig (Android Enterprise)
-
 #### New macOS settings in the Settings Catalog<!-- 13111526 idready idstaged wnready -->
 The Settings Catalog has new macOS settings you can configure (**Devices** > **Configuration profiles** > **Create profile** > **macOS** for platform >**Settings catalog (preview)** for profile type):
 
@@ -2888,4 +2866,4 @@ For previous months, see the [What's New archive](whats-new-archive.md).
 
 ## Notices
 
-[!INCLUDE [Intune notices](../includes/intune-notices.md)]
+[!INCLUDE [Intune notices](../includes/intune-notices.md)]

memdocs/intune/includes/intune-notices.md

@@ -124,7 +124,7 @@ No action is needed at this time. Review our [In Development](../fundamentals/in
 
 ### Plan for change: Intune is moving to support iOS/iPadOS 13 and later<!--10144130-->
 
-Later this year, we expect Apple to release iOS 15. Microsoft Intune, including the Intune Company Portal and Intune app protection policies (APP, also known as mobile application management), will require  iOS/iPadOS 13 and later shortly after iOS 15's release.
+Apple has released iOS 15. Microsoft Intune, including Intune Company Portal and Intune app protection policies (APP, also known as mobile application management), now requires iOS/iPadOS 13 and later.
 
 #### How does this affect you or your users?
 

memdocs/intune/remote-actions/teamviewer-support.md

@@ -29,7 +29,7 @@ ms.collection:
 
 # Use TeamViewer to remotely administer Intune devices
 
-Devices managed by Intune can be administered remotely using [TeamViewer](https://www.teamviewer.com). TeamViewer is a partner program that you purchase separately. This articles shows you how to configure TeamViewer within Intune, and how to remotely administer a device.
+Devices managed by Intune can be administered remotely using [TeamViewer](https://www.teamviewer.com). TeamViewer is a partner program that you purchase separately. This article shows you how to configure TeamViewer within Intune, and how to remotely administer a device.
 
 This feature applies to:
 
@@ -43,10 +43,7 @@ This feature applies to:
 
 - The administrator configuring the TeamViewer connector must have an Intune license. You can give administrators access to Microsoft Endpoint Manager without them requiring an Intune license. For more information, see [Unlicensed admins](../fundamentals/unlicensed-admins.md). 
 
-- The Intune administrator in the Endpoint Manager admin center must have the following [Intune roles](../fundamentals/role-based-access-control.md):  
-
-  - **Update Remote Assistance**: Allows administrators to modify the TeamViewer connector settings.
-  - **Request Remote Assistance**: Allows administrators to start a new remote assistance session for any user. Users with this role are not limited by any Intune role within a scope. Also, user or device groups assigned an Intune role within a scope can also request remote assistance. 
+- Only a Global administrator or Intune administrator in the Endpoint Manager admin center can onboard TeamViewer. 
 
 - Use a supported Intune-managed device: