From 75a09940783df3ab9430533b5f2aeed6fe5dd2ee Mon Sep 17 00:00:00 2001 From: Larry Mosley <38725311+lamosley@users.noreply.github.com> Date: Mon, 7 Oct 2024 06:23:33 -0400 Subject: [PATCH] Remove note about CM 2006 CM 2006 and earlier has been out of support for more than 3 years; TP updates are enabled by default now, so we should remove this note. --- .../configmgr/sum/deploy-use/third-party-software-updates.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/memdocs/configmgr/sum/deploy-use/third-party-software-updates.md b/memdocs/configmgr/sum/deploy-use/third-party-software-updates.md index e04703b5ea6..9b1abeef8e8 100644 --- a/memdocs/configmgr/sum/deploy-use/third-party-software-updates.md +++ b/memdocs/configmgr/sum/deploy-use/third-party-software-updates.md @@ -20,9 +20,6 @@ ms.collection: tier3 The **Third-Party Software Update Catalogs** node in the Configuration Manager console allows you to subscribe to third-party catalogs, publish their updates to your software update point (SUP), and then deploy them to clients. -> [!Note] -> In version 2006 and earlier, Configuration Manager doesn't enable this feature by default. Before using it, enable the optional feature **Enable third party update support on clients**. For more information, see [Enable optional features from updates](../../core/servers/manage/optional-features.md). - ## Prerequisites - Sufficient disk space on the top-level software update point's `WSUSContent` directory to store the source binary content for third-party software updates.