Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove note about CM 2006 #4646

Merged
merged 2 commits into from
Nov 12, 2024
Merged

Remove note about CM 2006 #4646

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
75a0994
Remove note about CM 2006
lamosley Oct 7, 2024
a2f8ef0
Merge branch 'main' into patch-5
dougeby Nov 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions memdocs/configmgr/sum/deploy-use/third-party-software-updates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. <!--1357605, 1352101, 1358714-->

> [!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.
Expand Down