Merge pull request #7351 from MicrosoftDocs/main

Publish 04/12/2022, 10:30 AM

Author: v-dihans

memdocs/configmgr/core/clients/manage/upgrade/test-client-upgrades.md

@@ -2,7 +2,7 @@
 title: Test client upgrades
 titleSuffix: Configuration Manager
 description: Test client upgrades in a pre-production collection in Configuration Manager.
-ms.date: 07/23/2021
+ms.date: 04/12/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: how-to
@@ -46,7 +46,7 @@ There are three steps to test clients in pre-production:
 
 :::image type="content" source="media/test-client-upgrades.png" alt-text="Hierarchy settings window, client upgrade tab, highlighting pre-production collection.":::
 
->[!NOTE]
+> [!NOTE]
 > Only a user with the **Full Administrator** security role and the **All** security scope can change these settings.
 
 ## Configure client upgrades during site update
@@ -78,7 +78,29 @@ The updated client version now replaces the client version in use in your hierar
 > [!NOTE]
 > To enable the pre-production client, or to promote a pre-production client to a production client, your account must be a member of a security role that has **Read** and **Modify** permissions for the **Update Packages** object.
 >
-> Client upgrades honor any Configuration Manager maintenance windows you have configured.
+> Client upgrades honor any Configuration Manager maintenance windows you configure. For more information on a known issue, see [Client upgrade and maintenance windows](upgrade-clients-for-windows-computers.md#client-upgrade-and-maintenance-windows).
+
+## Known issues
+
+### Pre-production client and site server high availability
+
+<!-- 13846674 -->
+Consider the following scenario:
+
+- You enable the pre-production client.
+- The site has a [site server in passive mode](../../../servers/deploy/configure/site-server-high-availability.md).
+- You update the site to the latest version.
+- You promote the passive mode site server to the active site server.
+
+After you promote the site server, the pre-production client version shows as the production version. Depending on your configuration, it may automatically deploy to all systems.
+
+When you install an update, Configuration Manager currently updates the **Client** folder of the site server in passive mode with the pre-production client version.
+
+To work around this issue:
+
+- Wait to promote the site server in passive mode until after you promote the pre-production client version to production version.
+
+- If you have to fail over for high availability, manually correct the client version in the **Client** folder.
 
 ## Next steps
 

memdocs/configmgr/core/clients/manage/upgrade/upgrade-clients-for-windows-computers.md

@@ -2,7 +2,7 @@
 title: Upgrade clients on Windows
 titleSuffix: Configuration Manager
 description: Upgrade clients on Windows computers in Configuration Manager.
-ms.date: 08/23/2021
+ms.date: 04/12/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: how-to
@@ -89,7 +89,24 @@ Use the following procedure to configure automatic client upgrade at the CAS. Th
 Clients receive these settings when they next download policy.
 
 > [!NOTE]
-> Client upgrades honor any Configuration Manager maintenance windows you've configured. The ClientServicing thread only runs the client setup bootstrap program (ccmsetup.exe) during a maintenance window. If the device runs an edition of Windows with a write filter, ccmsetup tries to download and install at the same time. Otherwise, ccmsetup randomizes a time to download content. After it downloads content and compiles the local policy, ClientServicing schedules the client upgrade during the next maintenance window.<!-- SCCMDocs#896, MEMDocs#1920 -->
+> Client upgrades honor any Configuration Manager maintenance windows you've configured. The ClientServicing thread only runs the client setup bootstrap program (ccmsetup.exe) during a maintenance window. For more information on a known issue, see [Client upgrade and maintenance windows](#client-upgrade-and-maintenance-windows).<!-- 13901385 -->
+>
+> If the device runs an edition of Windows with a write filter, ccmsetup tries to download and install at the same time. Otherwise, ccmsetup randomizes a time to download content. After it downloads content and compiles the local policy, ClientServicing schedules the client upgrade during the next maintenance window.<!-- SCCMDocs#896, MEMDocs#1920 -->
+
+## Known issues
+
+### Client upgrade and maintenance windows
+
+<!-- 13901385 -->
+
+For clients version 2111 or earlier, when you upgrade them to a later version, the process only honors any _business hours_ that the user defines. It doesn't use the administrator-defined maintenance window. For example:
+
+- Administrator-defined maintenance window: 12 AM - 5 AM
+- User-defined business hours: 5 AM - 10 PM
+
+The client upgrade starts at 10 PM after the business hours. It doesn't wait until the start of the maintenance window at 12 AM.
+
+This issue is fixed with the version 2203 client. When you upgrade clients from version 2203 to a later version, they will honor maintenance windows.
 
 ## Next steps
 

memdocs/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md

@@ -5,7 +5,7 @@ description: Learn about the features that Configuration Manager no longer suppo
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
-ms.date: 04/08/2022
+ms.date: 04/11/2022
 author: mestew
 ms.author: mstewart
 manager: dougeby
@@ -29,8 +29,9 @@ The following features are deprecated. You can still use them now, but Microsoft
 > Starting in November 2021, this feature of Configuration Manager is [deprecated](../../core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md). <comment the work item ID> (refer to alternative or blog with more info)Use Microsoft Intune to [deploy resource access profiles](../../../intune/configuration/device-profiles.md).
  -->
 
-|Feature|Deprecation first announced|Support&nbsp;removed|
-|-------|---------------------------|--------------------|
+|Feature|Deprecation first announced|Planned end of support|
+|-------|---------------------------|----------------------|
+| Upgrade from any version of System Center 2012 Configuration Manager to current branch. For more information, see [Upgrade to Configuration Manager current branch](../../../servers/deploy/install/upgrade-to-configuration-manager.md)<!-- 13846745 --> | April 2022 | Version 2303 |
 | The Configuration Manager client for **macOS** and Mac client management. For more information, see [Supported clients: Mac computers](../../configs/supported-operating-systems-for-clients-and-devices.md#mac-computers).<!-- 12927803 --> Migrate management of macOS devices to Microsoft Intune. For more information, see [Deployment guide: Manage macOS devices in Microsoft Intune](../../../../../intune/fundamentals/deployment-guide-platform-macos.md). | January 2022 | December 31, 2022 |
 | The site system roles for on-premises MDM and macOS clients: **enrollment proxy point and enrollment point**.<!-- 12454901,12927803 --> | January 2022 | December 31, 2022 |
 | The **Microsoft Store for Business and Education**. For more information, see [Manage apps from the Microsoft Store for Business and Education with Configuration Manager](../../../../apps/deploy-use/manage-apps-from-the-windows-store-for-business.md).<!-- 10884039 --> | November 2021 | The first release after March 1, 2023 |

memdocs/configmgr/core/plan-design/changes/whats-new-in-version-2002.md

@@ -89,7 +89,7 @@ The site system's proxy settings, including authentication, are now used by:
 - Azure AD user group discovery
 - Synchronizing collection membership results to Azure Active Directory groups
 
-For more information, see [Proxy server support](../network/proxy-server-support.md#bkmk_other).
+For more information, see [Proxy server support](../network/proxy-server-support.md#other-features-that-use-the-proxy).
 
 ## <a name="bkmk_cloud"></a> Cloud-attached management
 

memdocs/configmgr/core/plan-design/configs/site-and-site-system-prerequisites.md

@@ -2,7 +2,7 @@
 title: Site prerequisites
 titleSuffix: Configuration Manager
 description: Learn how to configure a Windows computer as a Configuration Manager site system server.
-ms.date: 03/29/2022
+ms.date: 04/11/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: reference
@@ -63,6 +63,9 @@ If the site server doesn't have any collocated roles that require .NET, it still
 
 ### Site systems
 
+> [!IMPORTANT]
+> If you're upgrading from System Center 2012 Configuration Manager R2 Service Pack 1, you need to manually verify that remote site systems have at least .NET version 4.6.2. Configuration Manager current branch setup skips the check in this scenario.<!-- 13846610 -->
+
 During Configuration Manager setup, if site systems have a version earlier than 4.6.2, you'll see a prerequisite check warning. This check is a warning instead of an error, because setup will install version 4.6.2. When .NET updates, it usually requires Windows to restart. Site systems will send status message 4979 when a restart is required. Configuration Manager suppresses the restart; the system doesn't restart automatically.
 
 The behavior will differ for different types of site roles that require .NET: