Merge branch 'main' of https://github.com/MicrosoftDocs/memdocs-pr into main

Author: MandiOhlinger

memdocs/analytics/app-reliability.md

@@ -66,6 +66,8 @@ For each application in the report, the following data is provided:
 
 > [!NOTE]
 > A maximum of 10 application crash events per application, per device, per day is used. This prevents excessive data collections from devices with severe application issues and helps prevent outlier devices from having undue influence over the reliability scores for individual applications.
+> 
+> Applications with an insignificant amount of foreground usage (about 10 minutes or fewer) on a particular device may not be captured. 
 
 ### App performance details
 

memdocs/autopilot/autopilot-device-guidelines.md

@@ -36,6 +36,7 @@ The following best practices ensure that devices can easily be provisioned as pa
 - Before shipping devices to an Autopilot customer or channel partner, the OEM should upload 4K Hardware Hashes to Microsoft by using the CBR report. The hashes should be collected using the OA3 Tool RS3+ run in Audit mode on full OS.
 - Microsoft requires that OEM shipping drivers get published to Windows Update within 30 days of the CBR submission date. System firmware and driver updates are published to Windows Update within 14 days.
 - The OEM ensures that the PKID provisioned in the SMBIOS is passed on to the channel.
+- When using a VM for Autopilot testing, assign at least 2 processors and 4gb of memory. This will help to prevent application install issues in Windows 10 devices with the [May 11, 2021 cumulative update](https://support.microsoft.com/topic/may-11-2021-kb5003173-os-builds-19041-985-19042-985-and-19043-985-2824ace2-eabe-4c3c-8a49-06e249f52527) installed. *Note: The [minimum system requirements](/windows/whats-new/windows-11-requirements#virtual-machine-support) for Windows 11 are 2 processors and 4gb memory.
 
 ## Software best practice guidelines for Windows Autopilot
 
@@ -47,4 +48,4 @@ The following best practices ensure that devices can easily be provisioned as pa
 ## Next steps
 
 [Windows Autopilot customer consent](registration-auth.md)<br>
-[Motherboard replacement scenario guidance](autopilot-mbr.md)<br>
+[Motherboard replacement scenario guidance](autopilot-mbr.md)<br>

memdocs/configmgr/apps/deploy-use/learn-script-security.md

@@ -32,9 +32,9 @@ The Configuration Manager scripts feature lets you visually review and approve s
 
 This collection of links was chosen to give Configuration Manager administrators a starting point for learning about PowerShell script security recommendations.
 
-[PowerShell Security Best Practices](https://devblogs.microsoft.com/powershell/powershell-security-best-practices/)
+<!-- [PowerShell Security Best Practices](https://devblogs.microsoft.com/powershell/powershell-security-best-practices/)
 
-> [!VIDEO https://channel9.msdn.com/Events/Blue-Hat-Security-Briefings/BlueHat-Security-Briefings-Fall-2013-Sessions/PowerShell-Best-Practices/player]
+> [!VIDEO https://channel9.msdn.com/Events/Blue-Hat-Security-Briefings/BlueHat-Security-Briefings-Fall-2013-Sessions/PowerShell-Best-Practices/player] -->
 
 [Defending Against PowerShell Attacks](https://devblogs.microsoft.com/powershell/defending-against-powershell-attacks/)
 

memdocs/configmgr/comanage/faq.yml

@@ -7,7 +7,7 @@ metadata:
   ms.author: aaroncz
   ms.reviewer: crosorio
   manager: dougeby
-  ms.date: 01/10/2021
+  ms.date: 01/26/2022
   ms.topic: reference
   ms.prod: configuration-manager
   ms.technology: configmgr-comanage
@@ -122,6 +122,9 @@ sections:
 
           For more information, see [How to prepare internet-based devices for co-management](how-to-prepare-win10.md).
 
+          > [!NOTE]
+          > You can't deploy the Configuration Manager client while provisioning a new computer in Windows Autopilot user-driven mode for hybrid Azure AD join. This limitation is due to the identity change of the device during the Azure AD-join process. Deploy the Configuration Manager client after the Autopilot process.<!-- CMADO-10205503 --> For alternative options to install the client, see [Client installation methods in Configuration Manager](../core/clients/deploy/plan/client-installation-methods.md).
+
       - question: |
           How do I manage updates for Windows and Microsoft 365 apps?
         answer: |

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/clients/manage/cmg/configure-clients.md

@@ -48,7 +48,7 @@ Get-WmiObject -Namespace Root\Ccm\LocationServices -Class SMS_ActiveMPCandidate
 This command displays any internet-based management points the client knows about. While the CMG isn't technically an internet-based management point, clients view it as one.
 
 > [!NOTE]
-> To troubleshoot CMG client traffic, use **CMGHttpHandler.log**, **CMGService.log**, and **SMS_Cloud_ProxyConnector.log**. For more information, see [Log files](../../../plan-design/hierarchy/log-files.md#cloud-management-gateway).
+> To troubleshoot CMG client traffic, use **CMGService.log** and **SMS_Cloud_ProxyConnector.log**. For more information, see [Log files](../../../plan-design/hierarchy/log-files.md#cloud-management-gateway).
 
 ## Install off-premises clients using a CMG
 

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.":::