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 a3a68244a22..fec44d9b94d 100644 --- a/memdocs/configmgr/sum/deploy-use/third-party-software-updates.md +++ b/memdocs/configmgr/sum/deploy-use/third-party-software-updates.md @@ -21,10 +21,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] -> - Microsoft does not test or verify third party update catalogs or their contents in any way. Before deploying you should verify that any updates downloaded from third party update catalogs are free from malicious software and verify them in a testing environment prior to deploying them in your environment. -> - 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.