Merge pull request #6660 from MicrosoftDocs/release-cm2201-tp

Release-cm2201-tp to main

Author: mestew

memdocs/configmgr/core/TOC.yml

@@ -285,14 +285,14 @@ items:
     items:
     - name: Technical Preview overview
       href: get-started/technical-preview.md
+    - name: 2201 features
+      href: get-started/2022/technical-preview-2201.md       
     - name: 2112 features
       href: get-started/2021/technical-preview-2112.md      
     - name: 2111 features
       href: get-started/2021/technical-preview-2111.md
     - name: 2110 features
       href: get-started/2021/technical-preview-2110.md
-    - name: 2109 features
-      href: get-started/2021/technical-preview-2109.md
   - name: Migrate data between hierarchies
     items:
     - name: Migration overview

memdocs/configmgr/core/get-started/2022/includes/2201/12486335.md

@@ -0,0 +1,55 @@
+---
+author: aczechowski
+ms.author: aaroncz
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_tsico"></a> Custom icon support for task sequences and packages
+
+<!--12486335-->
+
+Previously, task sequences and legacy packages would always display a default icon in Software Center. Based on your feedback, you can now add custom icons for task sequences and legacy packages. These icons appear in Software Center when you deploy these objects. Instead of a default icon, a custom icon can improve the user experience to better identify the software.
+
+### Try it out!
+
+Try to complete the tasks. Then send [Feedback](../../../../understand/product-feedback.md) with your thoughts on the feature.
+
+1. If needed, [create a task sequence](../../../../../osd/deploy-use/manage-task-sequences-to-automate-tasks.md) or [create a package and program](../../../../../apps/deploy-use/packages-and-programs.md#create-a-package-and-program).
+
+1. Open the properties of a task sequence or package.
+
+1. For a task sequence, switch to the **More Options** tab. For a package, the icon option is on the **General** tab.
+
+    > [!NOTE]
+    > The existing task sequence property page for **Performance** is now renamed to **More Options**.
+
+1. In the section for the icon, select **Browse**. Select an icon from the default shell library, or browse to another file in a local or network path.
+
+    - It supports the following file types:
+      - Programs (`.exe`)
+      - Libraries (`.dll`)
+      - Icons (`.ico`)
+      - Images (`.png`, `.jpeg`, `.jpg`)
+    - The file doesn't need to be on clients that you target with the deployment. Configuration Manager includes the image with the deployment policy.
+    - The maximum file size for an image is 256 KB.
+    - Icons can have pixel dimensions of up to 512 x 512.
+
+After you save the properties, deploy the task sequence or package, if it's not already deployed. For more information, see one of the following articles:
+
+- [Deploy a task sequence](../../../../../osd/deploy-use/deploy-a-task-sequence.md)
+- [Deploy packages and programs](../../../../../apps/deploy-use/packages-and-programs.md#deploy-packages-and-programs)
+
+When clients receive the deployment policy, they'll display the icon in Software Center.
+
+> [!NOTE]
+> To take full advantage of new Configuration Manager features, after you update the site, also update clients to the latest version. While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn't functional until the client version is also the latest.
+
+### Known issues with icons for legacy packages
+
+- To change the icon on an existing package that's already deployed, change another setting of the package or create a new deployment.<!-- 13040507 -->
+
+- Custom icons only appear for legacy packages that you deploy to device collections. They don't yet support user-based deployments.

memdocs/configmgr/core/get-started/2022/includes/2201/12487076.md

@@ -0,0 +1,18 @@
+---
+author: mestew
+ms.author: mstewart
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+ 
+## <a name="bkmk_reports"></a> Improvements to Power BI Report Server Integration
+<!--12487076-->
+
+We've made the following improvements for Power BI Report Server integration:
+
+- You can now use Microsoft Power BI Desktop (Optimized for Power BI Report Server) versions that were released after January 2021
+- Configuration Manager now correctly handles Power BI reports saved by Power BI Desktop (optimized for Power BI Report Server) May 2021 or later.
+   - Reports saved by Power BI Desktop (optimized for Power BI Report Server) May 2021 or later function in earlier versions of Configuration Manager. However, you might experience delays updating the data source on newly updated reports, or receive `The remote server returned an error; (400) Bad Request.` errors in the **SRSRP.log**. For more information about the relevant change to Power BI Desktop (optimized for Power BI Report Server) May 2021, see [Change data source connection strings in Power BI reports](/power-bi/report-server/connect-data-source-apis).

memdocs/configmgr/core/get-started/2022/includes/2201/12654996.md

@@ -0,0 +1,141 @@
+---
+author: aczechowski
+ms.author: aaroncz
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_powershell"></a> PowerShell release notes preview
+
+<!--12654996-->
+
+These release notes summarize changes to the Configuration Manager PowerShell cmdlets in this technical preview release.
+
+For more information about PowerShell for Configuration Manager, see [Get started with Configuration Manager cmdlets](/powershell/sccm/overview).
+
+### New cmdlets
+
+#### Get-CMAADTenant
+
+Use this cmdlet to get an Azure Active Directory (Azure AD) tenant from the site.
+
+```powershell
+Get-CMAADTenant
+Get-CMAADTenant -Id $id
+Get-CMAADTenant -Name $name
+```
+
+#### Set-CMCollectionCloudSync
+
+Use this cmdlet to configure the following cloud sync features for a collection:
+
+- Make a collection available to assign endpoint security policies from the Microsoft Endpoint Manager admin center. For more information, see [Tenant attach: Onboard Configuration Manager clients to Microsoft Defender for Endpoint from the admin center](../../../../../tenant-attach/atp-onboard.md).
+
+- Synchronize collection member results to Azure AD groups. For more information, see [Synchronize members to Azure AD groups](../../../../clients/manage/collections/create-collections.md#bkmk_aadcollsync).
+
+```powershell
+Set-CMCollectionCloudSync -Name $name -EnableAssignEndpointSecurityPolicy $true -TenantId $tenantId -AddGroupName $array  -Verbose
+Set-CMCollectionCloudSync -Id $collectionId -TenantName $tenantName -RemoveGroupName $array1  -AddGroupName $array2
+$collectionObj | Set-CMCollectionCloudSync TenantObject $tenantObj  -RemoveGroupName $array1  -AddGroupName $array2
+```
+
+### Modified cmdlets
+
+#### Get-CMDeploymentTypeDetectionClause
+
+For more information, see [Get-CMDeploymentTypeDetectionClause](/powershell/module/configurationmanager/Get-CMDeploymentTypeDetectionClause).
+
+**Non-breaking changes**
+
+The cmdlet can now get a detection clause from a script deployment type.
+
+#### Get-CMDeploymentStatusDetails
+
+For more information, see [Get-CMDeploymentStatusDetails](/powershell/module/configurationmanager/Get-CMDeploymentStatusDetails).
+
+**Bugs that were fixed**
+
+Updated the cmdlet to avoid a potential null reference error.
+
+#### Import-CMApplication
+
+For more information, see [Import-CMApplication](/powershell/module/configurationmanager/Import-CMApplication).
+
+**Non-breaking changes**
+
+Updated the import logic to align with console. Added new warning messages.
+
+#### New-CMCoManagementPolicy
+
+For more information, see [New-CMCoManagementPolicy](/powershell/module/configurationmanager/New-CMCoManagementPolicy).
+
+**Non-breaking changes**
+
+The cmdlet now supports applicability for Windows 11 on ARM64 devices.
+
+#### New-CMApplication
+
+For more information, see [New-CMApplication](/powershell/module/configurationmanager/New-CMApplication).
+
+**Non-breaking changes**
+
+It can now get an application icon from the specified file.
+
+#### New-CMTaskSequence
+
+For more information, see [New-CMTaskSequence](/powershell/module/configurationmanager/New-CMTaskSequence).
+
+**Non-breaking changes**
+
+Added the **IconLocationFile** parameter to support specifying an icon for the task sequence. For more information, see [Support for task sequence and package icons](#bkmk_tsico).
+
+#### New-CMTaskSequenceDeployment
+
+For more information, see [New-CMTaskSequenceDeployment](/powershell/module/configurationmanager/New-CMTaskSequenceDeployment).
+
+**Bugs that were fixed**
+
+Fixed an issue with the **AllowSharedContent** parameter.
+
+#### Publish-CMThirdPartySoftwareUpdateContent
+
+For more information, see [Publish-CMThirdPartySoftwareUpdateContent](/powershell/module/configurationmanager/Publish-CMThirdPartySoftwareUpdateContent).
+
+**Non-breaking changes**
+
+Added the **Force** parameter to run the command without asking for confirmation.
+
+#### Set-CMSoftwareUpdatePointComponent
+
+For more information, see [Set-CMSoftwareUpdatePointComponent](/powershell/module/configurationmanager/Set-CMSoftwareUpdatePointComponent).
+
+**Non-breaking changes**
+
+Added the **NonWindowsUpdateMaxRuntimeMins** parameter to change the default maximum run time for non-Windows software updates.
+
+#### Set-CMTaskSequence
+
+For more information, see [Set-CMTaskSequence](/powershell/module/configurationmanager/Set-CMTaskSequence).
+
+**Non-breaking changes**
+
+Added the **IconLocationFile** parameter to support specifying an icon for the task sequence. For more information, see [Support for task sequence and package icons](#bkmk_tsico).
+
+#### Set-CMTaskSequenceDeployment
+
+For more information, see [Set-CMTaskSequenceDeployment](/powershell/module/configurationmanager/Set-CMTaskSequenceDeployment).
+
+**Bugs that were fixed**
+
+Fixed an issue with the **AllowSharedContent** parameter.
+
+#### Start-CMTaskSequenceDeployment
+
+For more information, see [Start-CMTaskSequenceDeployment](/powershell/module/configurationmanager/Start-CMTaskSequenceDeployment).
+
+**Bugs that were fixed**
+
+Fixed an issue with the **AllowSharedContent** parameter.

memdocs/configmgr/core/get-started/2022/includes/2201/12895956.md

@@ -0,0 +1,19 @@
+---
+author: aczechowski
+ms.author: aaroncz
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_tsmedia"></a> Improved notice for content on task sequence media
+
+<!--12895956-->
+
+When you create task sequence media in the Configuration Manager console, you have to select distribution points that contain the content required by the task sequence. If some content isn't available on the selected distribution points, the wizard would display an error that simply said some packages aren't available.
+
+Based on your feedback, this message now includes the list of package IDs for the content that's not available. This change makes the notice more actionable, so you can more easily see what content is missing. This information is also listed in the CreateTsMedia.log file.
+
+:::image type="content" source="../../media/12895956-tsmedia-error.png" alt-text="Error message during task sequence media wizard when content isn't available on distribution points that lists the missing package IDs.":::

memdocs/configmgr/core/get-started/2022/includes/2201/3877839.md

@@ -0,0 +1,19 @@
+---
+author: aczechowski
+ms.author: aaroncz
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_sortico"></a> Sort by icon in the console
+
+<!--3877839-->
+
+Based on your feedback, in the Configuration Manager console you can now sort by icon. Any node that uses different icons now sorts properly. This improvement helps you easily group objects of a similar type.
+
+The following example shows the **Devices** node sorted by icon, which is the [device status](../../../../clients/manage/monitor-clients.md#monitor-individual-clients):
+
+:::image type="content" source="../../media/3877839-devices-sort-icon.png" alt-text="The Devices node in the Configuration Manager console sorted by the Icon column.":::

memdocs/configmgr/core/get-started/2022/includes/2201/4639895.md

@@ -0,0 +1,37 @@
+---
+author: aczechowski
+ms.author: aaroncz
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_ledbat"></a> LEDBAT support for software update points
+
+<!--4639895-->
+
+You can now enable Windows Low Extra Delay Background Transport (LEDBAT) for your software update points. LEDBAT adjusts download speeds during client scans against WSUS to help control network congestion.
+
+If a site system has both the distribution point and software update point roles, you can configure LEDBAT independently on the roles. For example, if you only enable LEDBAT on the distribution point role, the software update point role doesn't inherit the same configuration.
+
+For more general information on Windows LEDBAT, see [Fundamental concepts for content management](../../../../plan-design/hierarchy/fundamental-concepts-for-content-management.md#windows-ledbat).
+
+### Prerequisites for LEDBAT on software update points
+
+To use LEDBAT in this scenario, install the software update point role on a site system running Windows Server 2016 or later.
+
+### Try it out!
+
+Try to complete the tasks. Then send [Feedback](../../../../understand/product-feedback.md) with your thoughts on the feature.
+
+1. In the Configuration Manager console, go to the **Administration** workspace, expand **Site Configuration**, and select the **Servers and Site System Roles** node.
+
+1. Select a site system that has the software update point role.
+
+1. In the details pane of site system roles, select the **Software update point** role.
+
+1. In the ribbon, on the **Site Role** group, select **Properties**.
+
+1. On the **General** tab of the software update point properties, enable the following setting: **Adjust the download speed to use the unused network bandwidth (Windows LEDBAT)**.

memdocs/configmgr/core/get-started/2022/includes/2201/6374854.md

@@ -0,0 +1,23 @@
+---
+author: mestew
+ms.author: mstewart
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_ta"></a> Tenant attach features are generally available
+ <!--IN12976713 CM6374854-->
+
+The following [tenant attach](../../../../../tenant-attach/index.yml) features are now generally available:
+
+- Client details
+- Applications
+- Device timeline
+- Resource explorer
+- CMPivot
+- Scripts
+- Bitlocker Recovery Keys
+- Collections

memdocs/configmgr/core/get-started/2022/includes/2201/7079837.md

@@ -0,0 +1,22 @@
+---
+author: mestew
+ms.author: mstewart
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_notify"></a> Deployment Status client notification actions
+<!--7079837-->
+You can now perform client notification actions, including **Run Scripts**, from the **Deployment Status** view. To run client notification actions from the **Deployment Status** view:
+1. Go to the **Deployments** node in the **Monitoring** workspace.
+1. Select a deployment, then select **View Status**, or double-click on the deployment.
+1. Right-click on either a group of clients in a **Category** or a single client in the **Asset details** pane to display the client notification actions.
+   - Currently, any user can perform these actions, but they’ll receive a permissions error if they don't have the correct permissions.
+   - Currently, when there are no devices associated with the deployment status, the client notification actions display but won't trigger any notifications.
+    
+:::image type="content" source="../../media/70779837-client-notification.png" alt-text="Screenshot of the Deployment Status view showing the client notification actions. " lightbox="../../media/70779837-client-notification.png":::
+
+

memdocs/configmgr/core/get-started/2022/includes/2201/7759984.md

@@ -0,0 +1,34 @@
+---
+author: mestew
+ms.author: mstewart
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 01/27/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_cmgsup"></a> Prefer cloud-based software update points on switching
+
+Clients now prefer to scan against a cloud management gateway (CMG) software update point (SUP) over an on-premises SUP when the boundary group uses the **Prefer cloud based source over on-premises source** option. To reduce the performance impact of this change, clients [don't automatically switch their SUP](../../../../../sum/plan-design/plan-for-software-updates.md#BKMK_SUPSwitching) to a cloud-based SUP. The client will stay assigned to their current SUP unless their current SUP fails or the client is manually switched to a new SUP.
+
+### Try it out!
+
+Try to complete the tasks. Then send [Feedback](../../../../understand/product-feedback.md) with your thoughts on the feature.
+
+1. Ensure your [cloud management gateway](../../../../clients/manage/cmg/set-up-checklist.md?toc=/mem/configmgr/cloud-attach/toc.json&bc=/mem/configmgr/cloud-attach/breadcrumb/toc.json) is configured and functional
+1. Verify that your [software update points](../../../../../sum/get-started/install-a-software-update-point.md) are functional and synchronized.
+1. Enable the [**Allow Configuration Manager cloud management gateway traffic**](../../../../clients/manage/cmg/setup-cloud-management-gateway.md#bkmk_role) option for any SUP you want to use with CMG.
+    1. Go to **Administration** > **Site Configuration** > **Servers and Site System Roles**. Select **Properties** on the software update point site system role from the site server you want to use.
+    1. On the **General** tab, enable the **Allow Configuration Manager cloud management gateway traffic** option.
+1. [Configure the boundary group](../../../../servers/deploy/configure/boundary-group-procedures.md#configure-a-boundary-group) for this behavior by enabling the **Prefer cloud based sources over on-premises sources** option and adding the CGM SUP server to the **Site system servers** list.
+   1. Go to **Administration** > **Hierarchy Configuration** > **Boundary Groups**. Edit the boundary groups where you want clients to prefer a CMG SUP for updates scanning.
+    1. Select **Properties** for the boundary group.
+    1. In the **References** tab, select **Add...** and add the CMG SUP to the **Site system servers** list.
+    1. In the **Options** tab, select the **Prefer cloud based sources over on-premises sources**  option.
+    1. Select **OK** to save the settings and to close the boundary group properties window.
+1. To manually switch clients to a new SUP, use the **Switch to next Software Update Point** [client notification](../../../../clients/manage/client-notification.md#switch-to-the-next-software-update-point) action for a device or for a collection.
+   - Clients in the boundary group [don't automatically switch to a new SUP](../../../../../sum/plan-design/plan-for-software-updates.md#BKMK_SUPSwitching) unless scanning against their current SUP fails four times over the course of two hours.
+1. To verify that clients prefer the CMG SUP, start a software update scan cycle on some of the clients that you switched.
+   - To limit potential performance issues caused by a large number of clients scanning against a new SUP simultaneously, we recommend that if you're immediately calling a scan cycle on a large number of clients that you start with no more than 100 clients every 10-15 minutes. Increase or decrease the number of clients and the frequency once you gauge the performance impact in your environment.
+1. The client's **LocationServices.log** will show the CMG SUP listed as the first `LocationRecord WSUSURL` in the `WSUSLocationReply`. The CMG SUP will also be listed as the server for the update scan in the **WUAHandler.log**.