Merge branch 'main' into release-win365-gcc

Author: v-alje

memdocs/autopilot/dfci-management.md

@@ -13,7 +13,7 @@ author: aczechowski
 ms.author: aaroncz
 ms.reviewer: jubaptis
 manager: dougeby
-ms.date: 09/24/2021
+ms.date: 09/19/2022
 ms.collection: M365-modern-desktop
 ms.topic: conceptual
 ---
@@ -73,8 +73,9 @@ You can also [change existing DFCI settings](/intune/configuration/device-firmwa
 ## OEMs that support DFCI
 
 - [Microsoft Surface](/surface/surface-manage-dfci-guide)
+- Acer
 
-Additional OEMs are pending.
+Other OEMs are pending.
 
 ## See also
 

memdocs/configmgr/hotfix/2207/15498768.md

@@ -0,0 +1,77 @@
+---
+title: NTLM connection fallback update for Microsoft Endpoint Configuration Manager
+titleSuffix: Configuration Manager
+description: NTLM connection fallback update for Configuration Manager
+ms.date: 09/20/2022
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: reference
+ms.assetid: 3c93a332-e818-46fe-860f-cbebf4dd9ab3
+author: bhuney
+ms.author: brianhun
+manager: dougeby
+---
+# NTLM connection fallback update for Microsoft Endpoint Configuration Manager
+
+*Applies to: Configuration Manager (current branch, versions 2103, 2107, 2111, 2203, 2207)*
+
+## Summary of KB15498768
+Disabling the **Allow connection fallback to NTLM** option in *Client Push Installation Properties* is not honored under either of the following conditions:
+- If there are Kerberos authentication failures the client push account will attempt an NTLM connection instead.
+- The site server computer account will attempt a connection using NTLM if Kerberos authentication fails for all defined client push installation accounts.
+
+This update prevents any attempt at NTLM authentication for client push installation when the **Allow connection fallback to NTLM** option is disabled.
+
+Installation of this update resolves the following security issue:
+- [CVE-2022-37972](https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2022-37972)
+
+Beginning with Configuration Manager current branch, version 2207, the **Allow connection fallback to NTLM** option is *disabled* by default on new site installations.
+
+It is recommended to disable this option in existing environments, where possible, to increase security.
+
+Refer to the following documents for more detail on client and NTLM security:
+- [Security and privacy for Configuration Manager clients](../../core/clients/deploy/plan/security-and-privacy-for-clients.md#security-guidance-for-clients)
+- [KB5005413: Mitigating NTLM Relay Attacks on Active Directory Certificate Services](https://support.microsoft.com/topic/kb5005413-mitigating-ntlm-relay-attacks-on-active-directory-certificate-services-ad-cs-3612b773-4043-4aa9-b23d-b87910cd3429)
+- [Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers](https://learn.microsoft.com/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-outgoing-ntlm-traffic-to-remote-servers)
+
+Environments using versions of Configuration Manager current branch prior to 2103 are encouraged to update to a later supported version. Administrators can also disable use of automatic and manual client push installation methods to remove the risk of exposure to this issue.
+For more information, see [Support for Configuration Manager current branch versions](../../core/servers/manage/current-branch-versions-supported.md).
+ 
+## Update information for Microsoft Endpoint Configuration Manager, versions 2103-2207
+An update to resolve this issue is available in the **Updates and Servicing** node of the Configuration Manager console for environments that have versions 2103-2207 installed. 
+
+#### Update replacement information
+This update does not replace any previously released updates.
+
+#### Restart information
+For Configuration Manager versions 2107 and later, this update does not require a computer restart or a [site reset](../../core/servers/manage/modify-your-infrastructure.md#bkmk_reset) after installation.
+
+Configuration Manager version 2103 will require a site reset after update installation.
+
+### Additional installation information
+After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, select **Administration** > **Site Configuration** > **Sites** >  **Recover Secondary Site**, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
+
+Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
+   ```sql
+   select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
+   ```
+If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.
+
+If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the **Recover Secondary Site** option to update the secondary site.
+
+## Version information
+No major components are updated with this release.
+
+## File information
+File information is available in the following version-specific file lists (KB15498768_FileList.txt):
+- [Configuration Manager 2103](https://aka.ms/KB15498768_2103_FileList)
+- [Configuration Manager 2107](https://aka.ms/KB15498768_2107_FileList)
+- [Configuration Manager 2111](https://aka.ms/KB15498768_2111_FileList)
+- [Configuration Manager 2203](https://aka.ms/KB15498768_2203_FileList)
+- [Configuration Manager 2207](https://aka.ms/KB15498768_2207_FileList)
+
+## Release history
+- September 20, 2022: Initial hotfix release
+
+## References
+[Updates and servicing for Configuration Manager](../../core/servers/manage/updates.md)

memdocs/configmgr/hotfix/TOC.yml

@@ -9,6 +9,8 @@ items:
     href: 2207/14959905.md
   - name: KB 14978429  Connected cache update for Microsoft Endpoint Configuration Manager version 2207
     href: 2207/14978429.md
+  - name: KB 15498768 NTLM connection fallback update
+    href: 2207/15498768.md
 - name: Version 2203
   items:
   - name: KB 13174460 Summary of changes in 2203
@@ -19,6 +21,8 @@ items:
     href: 2203/14480034.md
   - name: KB 14244456 Update rollup for Microsoft Endpoint Configuration Manager version 2203
     href: 2203/14244456.md
+  - name: KB 15498768 NTLM connection fallback update
+    href: 2207/15498768.md
 - name: Version 2111
   items:
   - name: KB 10096997 Summary of changes in 2111
@@ -31,6 +35,8 @@ items:
     href: 2111/12819689.md
   - name: KB 12896009 Update rollup for Microsoft Endpoint Configuration Manager version 2111
     href: 2111/12896009.md
+  - name: KB 15498768 NTLM connection fallback update
+    href: 2207/15498768.md
 - name: Version 2107
   items:
   - name: KB 10096997 Summary of changes in 2107
@@ -41,6 +47,8 @@ items:
     href: 2107/11121541.md
   - name: KB 12636660 Network access account update
     href: 2107/12636660.md
+  - name: KB 15498768 NTLM connection fallback update
+    href: 2207/15498768.md
 - name: Version 2103
   items:
   - name: KB 9210721 Summary of changes in 2103
@@ -59,6 +67,8 @@ items:
     href: 2103/10589155.md
   - name: KB 10582136 Tenant attach update
     href: 2103/10582136.md
+  - name: KB 15498768 NTLM connection fallback update
+    href: 2207/15498768.md
 - name: Version 2010
   items:
   - name: KB 4599442 Summary of changes in 2010

memdocs/configmgr/hotfix/index.yml

@@ -25,6 +25,8 @@ landingContent:
             url: 2207/14840616.md
           - text: KB 14959905 Early update ring
             url: 2207/14959905.md
+          - text: KB 15498768 NTLM connection fallback update
+            url: 2207/15498768.md
 
   - title: Configuration Manager 2203
     linkLists:

memdocs/intune/apps/app-sideload-windows.md

@@ -35,6 +35,8 @@ ms.collection:
 As an Intune administrator, you can deploy line-of-business (LOB) Universal apps to Windows 8.1 Desktop or Windows 10/11 Desktop & Mobile devices, including the Company Portal app. To deploy *.appx* apps to Windows 8.1 Desktop or Windows 10/11 Desktop & Mobile devices you can use code-signing certificate from a public certification authority already trusted by your Windows devices, or you can use your own certificate authority.
 
  > [!NOTE]
+ > Microsoft Intune will be ending support on October 21, 2022 for devices running Windows 8.1. Intune will no longer support Windows 8.1 sideloading.
+ > 
  > Windows 8.1 Desktop requires either an enterprise policy to enable sideloading or the use of Sideloading Keys (automatically enabled for domain-joined devices). For more information, see [Windows 8 sideloading](/archive/blogs/scd-odtsp/windows-8-sideloading-requirements-from-technet).
 
 ## Windows 10/11 sideloading
@@ -43,7 +45,7 @@ In Windows 10/11, sideloading is different than in earlier versions of Windows:
 
 - You can unlock a device for sideloading using an enterprise policy. Intune provides a device config policy called "Trusted app installation". Setting this to **allow** is all that is needed for devices that already trust the certificate used to sign the appx app.
 
-- Symantec Phone certificates and Sideloading License keys are not required. However if an on-premise certificate authority is not available then you may need to obtain a code signing certificate from a public certification authority. For more information, see [Introduction to Code Signing](/windows/desktop/SecCrypto/cryptography-tools#introduction-to-code-signing).
+- Symantec Phone certificates and Sideloading License keys are not required. However if an on-premises certificate authority is not available then you may need to obtain a code signing certificate from a public certification authority. For more information, see [Introduction to Code Signing](/windows/desktop/SecCrypto/cryptography-tools#introduction-to-code-signing).
 
 ### Code sign your app