Merge branch 'main' into release-cm2201-tp

v-alje · v-alje · commit af34bdf7095b · 2022-01-21T11:55:12.000-08:00
diff --git a/memdocs/analytics/enroll-configmgr.md b/memdocs/analytics/enroll-configmgr.md
@@ -33,10 +33,7 @@ Before you start this tutorial, make sure you have the following prerequisites:
 
 ### Licensing Prerequisites
 
-Endpoint analytics is included in the following plans:
-
-- [Enterprise Mobility + Security E3](https://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=51) or higher
-- [Microsoft 365 Enterprise E3](https://www.microsoft.com/en-us/microsoft-365/enterprise?rtc=1) or higher.
+Devices enrolled in Endpoint analytics need a valid license for the use of Microsoft Endpoint Manager. For more information, see [Microsoft Intune licensing](../intune/fundamentals/licenses.md) or [Microsoft Endpoint Configuration Manager licensing](../configmgr/core/understand/learn-more-editions.md).
 
 ## Endpoint analytics permissions
 
diff --git a/memdocs/analytics/enroll-intune.md b/memdocs/analytics/enroll-intune.md
@@ -43,10 +43,7 @@ To enroll devices to Endpoint analytics, they need to send required functional d
 
 ### Licensing Prerequisites
 
-Endpoint analytics is included in the following plans:
-
-- [Enterprise Mobility + Security E3](https://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=51) or higher
-- [Microsoft 365 Enterprise E3](https://www.microsoft.com/en-us/microsoft-365/enterprise?rtc=1) or higher.
+Devices enrolled in Endpoint analytics need a valid license for the use of Microsoft Endpoint Manager. For more information, see [Microsoft Intune licensing](../intune/fundamentals/licenses.md) or [Microsoft Endpoint Configuration Manager licensing](../configmgr/core/understand/learn-more-editions.md).
 
 ### Endpoint analytics permissions
 
diff --git a/memdocs/configmgr/hotfix/2010/5001600.md b/memdocs/configmgr/hotfix/2010/5001600.md
@@ -16,6 +16,12 @@ ms.localizationpriority: medium
 *Applies to: Configuration Manager (current branch, versions 1910 - 2010)*
 
 ## Summary of KB5001600
+> [!NOTE]
+> This update is replaced by the following newer version effective January 21, 2022
+>
+> [KB 12819689 Connected cache update for Microsoft Endpoint Configuration Manager version 2111](../../hotfix/2111/12819689.md)
+>
+
 Due to content delivery network changes, the Microsoft Connected Cache (MCC) server component installation fails when enabled for distribution points *after* **March 5, 2021**.
 This component is enabled by selecting the **Enable this distribution point to be used as Microsoft Connected Cache server** option in a distribution point's properties. 
 After March 5, 2021, once enabled, the component will retry installation three times before stopping. 
diff --git a/memdocs/configmgr/hotfix/2111/12709700.md b/memdocs/configmgr/hotfix/2111/12709700.md
@@ -69,7 +69,7 @@ The following major components are updated to the versions specified:
 
 |Component |Version |
 |---|---|
-| Site | 5.00.9060.1000 |
+| Full Version | 5.00.9068.1008 |
 | Configuration Manager console | 5.2111.1052.1700 |
 | Client | 5.00.9068.1008 |
 
diff --git a/memdocs/configmgr/hotfix/2111/12819689.md b/memdocs/configmgr/hotfix/2111/12819689.md
@@ -0,0 +1,63 @@
+---
+title: Connected cache update for Microsoft Endpoint Configuration Manager version 2111
+titleSuffix: Configuration Manager
+description: Console update for 2111
+ms.date: 1/21/2022
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: reference
+ms.assetid: 41afa274-7561-4c0e-80af-2d0fe01699ef
+author: bhuney
+ms.author: brianhun
+manager: dougeby
+---
+
+# Connected cache update for Microsoft Endpoint Configuration Manager version 2111
+
+*Applies to: Configuration Manager (current branch, version 2111)*
+## Summary of KB12819689
+
+An update is available to resolve the following issue with Configuration Manager current branch, version 2111.
+
+- The Microsoft Connected Cache (MCC) feature is not used as expected for Win32 apps deployed through Microsoft Intune in a co-managed environment.
+Review of the IntuneManagementExtension.log file shows an internet-based **DownloadURL** value. 
+The MCC component is enabled by selecting the **Enable this distribution point to be used as Microsoft Connected Cache server** option in a distribution point's properties.
+ 
+
+## Update information for Microsoft Endpoint Configuration Manager, version 2111
+The following hotfix to resolve this problem is available for download from the Microsoft Download Center:
+
+[Download this hotfix now](https://download.microsoft.com/download/a/3/a/a3af1ea3-79ba-4600-8953-c2a4b6b8b970/DoincInstall.exe).
+
+After you download this hotfix, refer to the following installation instructions.
+
+## Installation instructions
+1. Confirm there is not currently an installation of the MCC component in progress. This is done by checking for status message **9522**, generated by the `SMS_DISTRIBUTION_MANAGER` component. The 9522 message indicates that installation is no longer being retried.
+2. Copy the new version of `DoincInstall.exe`, version **1.5.5.9002**, to the `{SMSInstallDir}\bin\x64` folder on all site servers, including the Central Administration Site (CAS) if present, and any passive sites.
+3. Uncheck the **Enable this distribution point to be used as Microsoft Connected Cache server** option in the affected distribution point’s properties.
+4. Wait for the uninstall of MCC to complete on the distribution point. This can be confirmed by looking for a **9152** success status message, combined with the following entry in `distmgr.log`.
+   ```text
+   Finished waiting for DoincInstall. InvocationState: UninstallCompleted. InvocationExitCode: 0. InvocationMessage: .
+   ```
+5. Recheck the **Enable this distribution point to be used as Microsoft Connected Cache server** option for the affected distribution point.
+
+   > [!TIP]
+   > For sites with a large number of distribution points, replace steps 4 - 5 above with the following.
+   > - Create an empty file named `resetdps.trn` and place it in the `{SMSInstallDir}\inboxes\distmgr.box` folder. This will reinstall all distribution points for that site using the latest version of `DoincInstall.exe` copied in step 3. above. 
+
+## Prerequisites
+To apply this hotfix, you must be using Microsoft Endpoint Configuration Manager, versions 1910 through versions 2111.
+
+## Restart information
+You don't have to restart the computer after you apply this hotfix. 
+
+## Hotfix replacement information
+This hotfix replaces the following previously released hotfix.
+
+[KB5001600 Microsoft Connected Cache component fails to install on Configuration Manager current branch](../../hotfix/2010/5001600.md)
+
+## File information
+File information is available in the downloadable [KB12819689_FileList.txt](https://aka.ms/KB12819689_FileList) text file.
+
+## Release history
+- January 21, 2022: Initial hotfix release
diff --git a/memdocs/configmgr/hotfix/TOC.yml b/memdocs/configmgr/hotfix/TOC.yml
@@ -9,6 +9,8 @@ items:
     href: 2111/12709700.md
   - name: KB 12959506 Client update for Configuration Manager 2111
     href: 2111/12959506.md
+  - name: KB 12819689 Connected cache update for Microsoft Endpoint Configuration Manager version 2111
+    href: 2111/12819689.md
 - name: Version 2107
   items:
   - name: KB 10096997 Summary of changes in 2107
diff --git a/memdocs/intune/enrollment/device-enrollment-manager-enroll.md b/memdocs/intune/enrollment/device-enrollment-manager-enroll.md
@@ -33,7 +33,7 @@ ms.collection:
 
 # Enroll devices in Intune by using a device enrollment manager account
 
-You can enroll up to 1,000 mobile devices with a single Azure Active Directory account by using a device enrollment manager (DEM) account. DEM is an Intune permission that can be applied to an Azure AD user account and lets the user enroll up to 1,000 devices. A DEM account is useful for scenarios where devices are enrolled and prepared before handing them out to the users of the devices. By design, there's a limit of 150 Device Enrollment Manager (DEM) accounts in Microsoft Intune.
+You can enroll up to 1,000 devices with a single Azure Active Directory account by using a device enrollment manager (DEM) account. DEM is an Intune permission that can be applied to an Azure AD user account and lets the user enroll up to 1,000 devices. A DEM account is useful for scenarios where devices are enrolled and prepared before handing them out to the users of the devices. By design, there's a limit of 150 Device Enrollment Manager (DEM) accounts in Microsoft Intune.
 
 ## Limitations of devices that are enrolled with a DEM account
 
diff --git a/memdocs/intune/enrollment/enrollment-restrictions-set.md b/memdocs/intune/enrollment/enrollment-restrictions-set.md
@@ -200,7 +200,6 @@ The following filter properties are always available to use with enrollment poli
 
 * OS version 
 * Operating System SKU 
-* Ownership
 * Enrollment profile name
 
 **iOS/iPadOS and macOS**  
diff --git a/memdocs/intune/enrollment/windows-enrollment-status.md b/memdocs/intune/enrollment/windows-enrollment-status.md
@@ -99,7 +99,7 @@ To turn on the Enrollment Status Page, follow the steps below.
 8. Choose **Settings** > *choose the settings you want to apply to this profile* > **Save**.
 
 > [!NOTE]
-> Due to OS restrictions, only a subset of filters are available to use when assigning **Enrollment Status Page** policies. The filter picker will only show filters that have rules defined for `osVersion`, `operatingSystemSKU`, `deviceOwnership`, and `enrollmentProfileName` properties. Filters that contain other properties are not shown.
+> Due to OS restrictions, only a subset of filters are available to use when assigning **Enrollment Status Page** policies. The filter picker will only show filters that have rules defined for `osVersion`, `operatingSystemSKU`, and `enrollmentProfileName` properties. Filters that contain other properties are not shown.
 
 ## Set the enrollment status page priority
 
diff --git a/memdocs/intune/fundamentals/in-development.md b/memdocs/intune/fundamentals/in-development.md
@@ -90,7 +90,7 @@ As part of a public preview, you'll soon be able to use the Microsoft Defender f
 ## Device configuration
 
 ### Use Collect diagnostics to collect additional details from Windows 365 devices through Intune remote actions<!--  12636207 -->
-Intune’s remote action to [*Collect diagnostics*](../remote-actions/collect-diagnostics.md) will soon collect additional details from Windows 365 (Coud-PC) devices.  (**Devices** > **Windows** > *select a Windows 365 device* > **Collect diagnostics**)
+Intune's remote action to [*Collect diagnostics*](../remote-actions/collect-diagnostics.md) will soon collect additional details from Windows 365 (Cloud PC) devices.  (**Devices** > **Windows** > *select a Windows 365 device* > **Collect diagnostics**)
 
 The new details for Windows 365 devices include the following registry data:
 - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\WebRTC Redirector 
diff --git a/memdocs/intune/fundamentals/supported-devices-browsers.md b/memdocs/intune/fundamentals/supported-devices-browsers.md
@@ -31,29 +31,30 @@ ms.collection:
 
 # Supported operating systems and browsers in Intune
 
-Before setting up Microsoft Intune, review the supported operating systems and browsers.
-
-For help installing Intune on your device, see [using managed devices to get work done](../user-help/use-managed-devices-to-get-work-done.md) and [Intune network bandwidth usage](network-bandwidth-use.md).
-
-For more information on configuration service provider support, visit the [Configuration service provider reference](/windows/client-management/mdm/configuration-service-provider-reference).
+Before setting up Microsoft Intune, review the supported operating systems, versions, and browsers. 
 
 > [!NOTE]
 > Intune requires Android 6.x or higher for device enrollment scenarios. For Intune app protection policies, Intune requires Android 9.0 or higher. This requirement does NOT apply to [Microsoft Teams Android devices](https://www.microsoft.com/microsoft-teams/across-devices/devices?rtc=2) as these devices will continue to be supported.
 
 ## Intune supported operating systems
 
-You can manage devices running the following operating systems:
+Intune supports devices running the following operating systems (OS):
+
+* iOS
+* Android 
+* Windows
+* macOS 
 
 [!INCLUDE [mdm-supported-devices](../includes/mdm-supported-devices.md)]
 
-### Supported Samsung Knox Standard devices
+### Supported Samsung Knox Standard devices  
 
-To avoid Knox activation errors that prevent MDM enrollment, the Company Portal app only attempts Samsung Knox activation during MDM enrollment if the device appears in the [list of supported Knox devices](https://www.samsungknox.com/knox-supported-devices/knox-workspace). Devices that don't support Samsung Knox activation enroll as standard Android devices. A Samsung device might have some model numbers that support Knox, while others don't. Verify Knox compatibility with your device reseller before you buy and deploy Samsung devices.
+Microsoft Intune only attempts Samsung Knox activation during enrollment on supported Knox devices. Devices that don't support Samsung Knox enroll as standard Android devices. For a list of devices that support Samsung Knox, see [Devices secured by Knox](https://www.samsungknox.com/knox-supported-devices/knox-workspace) on the Samsung Knox website. It's important to look for your device model number when verifying support, because some device models support Knox while others do not. Always verify Knox compatibility with your device reseller before you buy and deploy Samsung devices.  
 
 > [!NOTE]
-> Enrolling Samsung Knox devices may require you to enable access to Samsung servers.
+> You may need to enable access to Samsung servers to enroll Samsung Knox devices. For more information about enrollment, see [Automatically enroll Android devices by using Samsung's Knox Mobile Enrollment](../enrollment/android-samsung-knox-mobile-enroll.md).  
 
-The following list of Samsung device models do not support Knox. They are enrolled as native Android devices by the Company Portal app for Android:
+The Samsung device models in the following table do not support Knox solutions and features. Intune enrolls them as native Android devices. 
 
 | **Device Name** | **Device Model Numbers** |
 | --- | --- |
@@ -94,14 +95,20 @@ The following list of Samsung device models do not support Knox. They are enroll
 
 ## Intune supported web browsers
 
-Different administrative tasks require that you use one of the following administrative websites.
+Device management and administrative tasks are done in the Microsoft Endpoint Management admin center. Use these portals to access the admin center:  
 
 - [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?LinkId=698854)
 - [Azure portal](https://portal.azure.com/)
 
-The following browsers are supported for these portals:
+Microsoft Endpoint Manager is supported with the following web browsers: 
 
 - Microsoft Edge (latest version)
 - Safari (latest version, Mac only)
 - Chrome (latest version)
-- Firefox (latest version)
+- Firefox (latest version)  
+
+## Next steps  
+For network configuration requirements, or to learn more about setting up devices using the configuration service provider (CSP), see:
+
+* [Intune network configuration requirements and bandwidth](network-bandwidth-use.md)   
+* [Configuration service provider reference](/windows/client-management/mdm/configuration-service-provider-reference)  
diff --git a/windows-365/enterprise/cisco-webex-support.md b/windows-365/enterprise/cisco-webex-support.md
@@ -38,7 +38,7 @@ To optimize Cisco Webex, you’ll need to:
 - Install the Webex App VDI plugin on the local Windows PC that the user will use to access the Cloud PC.
 
 > [!NOTE]  
-> If you run into issues with Cisco Webex for VDI on your Cloud PC, contact Cisco support.
+> If you run into issues with Cisco Webex for VDI on your Cloud PC, contact [Cisco support](https://help.webex.com/contact).
 
 ## Requirements
 
@@ -67,7 +67,7 @@ For more information on these installation steps, see [Cisco's Deployment guide
 
 ## To use the optimized Cisco Webex client
 
-To benefit from these optimizations, users must sign in to their Cloud PC from a Windows PC. After doing so, the user can open Cisco Webex from the Cloud PC.
+To benefit from these optimizations, users must sign in to their Cloud PC from a Windows PC. After doing so, the user can open Cisco Webex from the Cloud PC and use the WebEx client optimized for Windows 365 Cloud PC.
 
 ## To confirm that the Cisco Webex client is using the optimizations
 
diff --git a/windows-365/enterprise/end-user-access-cloud-pc.md b/windows-365/enterprise/end-user-access-cloud-pc.md
@@ -20,7 +20,7 @@ ms.assetid:
 #ROBOTS:
 #audience:
 
-ms.reviewer: alcort
+ms.reviewer: ivivano
 ms.suite: ems
 search.appverid: MET150
 #ms.tgt_pltfrm:
@@ -75,7 +75,7 @@ For a list of clients by operating system, see [Remote Desktop clients](/windows
 
 To set up their Remote Desktop client, users follow these steps:
 
-1. Download the Remote Desktop app from the Download App page on [www.microsoft.com/windows-365?rtc=1](https://www.microsoft.com/windows-365?rtc=1).
+1. Download the Remote Desktop app from the [Remote Desktop clients page](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients).
 2. Select **Subscribe**.
 3. Enter their Azure Active Directory credentials.
 4. The Cloud PC appears in the list, and they can double-click it to launch.
diff --git a/windows-365/enterprise/whats-new.md b/windows-365/enterprise/whats-new.md
@@ -47,19 +47,26 @@ Learn what new features are available in Windows 365 Enterprise.
 ### Scripts
 -->
 
+<!-- ########################## -->
+## Week of January 17, 2022
+
+#### New documentation article: Optimize Cisco Webex on a Windows 365 Cloud PC<!--37106382-->
+
+We’ve published a new help documentation article. For more information, see [Optimize Cisco Webex on a Windows 365 Cloud PC](cisco-webex-support.md).
+
 <!-- ########################## -->
 ## Week of January 10, 2022
 
 #### New documentation: Data encryption in Windows 365<!--36626607-->
 
-We've just added information to the help documentation about encryption for Windows 365 Cloud PCs. For more information, see [Data encryption in Windows 365](encryption.md).
+We've added information to the help documentation about encryption for Windows 365 Cloud PCs. For more information, see [Data encryption in Windows 365](encryption.md).
 
 <!-- ########################## -->
 ## Week of January 3, 2022
 
 #### New documentation: Gallery image update cycle<!--36626607-->
 
-We've just added information to the help documentation about the update cycle for Windows 365 Cloud PC gallery images. For more information, see [Gallery image update cycle](device-images.md#gallery-image-update-cycle).
+We've added information to the help documentation about the update cycle for Windows 365 Cloud PC gallery images. For more information, see [Gallery image update cycle](device-images.md#gallery-image-update-cycle).
 
 <!-- ########################## -->
 ## Week of December 13, 2021
@@ -85,7 +92,7 @@ The **Provisioning policies** page has a new column: **Image status**. It tells
 
 #### New documentation article: Optimize Zoom on a Windows 365 Cloud PC<!--37106382-->
 
-We’ve just published a new help documentation article. For more information, see [Optimize Zoom on a Windows 365 Cloud PC](zoom-support.md).
+We’ve published a new help documentation article. For more information, see [Optimize Zoom on a Windows 365 Cloud PC](zoom-support.md).
 
 <!-- vvvvvvvvvvvvvvvvvvvvvv -->
 ### Device security
