--- title: Client Software Distribution 2.0 application description: Client Software Distribution 2.0 application \(CSD 2.0\) application enables administrators to distribute software from the service catalog using third-party management systems. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/integration-hub/csd-app-2.html release: australia product: Integration Hub classification: integration-hub topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 7 breadcrumb: [Integration Hub solutions, Build integrations, Integration Hub, Workflow Data Fabric] --- # Client Software Distribution 2.0 application Client Software Distribution 2.0 application \(CSD 2.0\) application enables administrators to distribute software from the service catalog using third-party management systems. CSD 2.0 enables an administrator to create all the records necessary to deploy software from service catalog requests, including software models and catalog items. You can use the CSD 2.0 application to automate the deployment and revocation of software from a third-party software provider using the custom flows. You can define lease periods for software distributed from the Service Catalog and allow lease extensions in some cases, pending approvals. Deployment is accomplished using provider-specific spoke flows, subflows, and actions. For example, deployment is accomplished using Microsoft Endpoint Configuration Manager spoke. CSD 2.0 also integrates with Software Asset Management \(SAM Professional or SAM Foundation\) to manage license information of the deployed software. **Note:** CSD 2.0 is different from [Client Software Distribution using Integration Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/csd-integrationhub.md). CSD 2.0 is available on ServiceNow Store. \[Omitted image "CSDProcess.png"\] Alt text: CSD 2.0 process flow **Note:** To integrate CSD 2.0 with SAM, navigate to **Client Software Distribution 2.0** > **Properties** and select the check box for **Determines whether to use SAM plugin\(SAM Foundation or SAM Professional\) tables for managing software models and licensing information**.\[Omitted image "CSD2-props.png"\] Alt text: Option to integrated with SAM. ## Important considerations Ensure that you are aware of these differences between CSD and CSD 2.0:
| CSD | CSD 2.0 | |
|---|---|---|
| Supported providers | Microsoft System Center Configuration Management \(SCCM\). | Microsoft Endpoint Configuration Manager, Jamf, and Microsoft Intune. |
| Procedure to add new provider | User must write extension point scripts. | User can use subflows in Workflow Studio. This is easier than writing extension point scripts in CSD. |
| License compliance check and entitlements | Tightly coupled with the SAM license data. | Flexibility to choose either the SAM tables or CSD 2.0 tables. |
| Data discovery | Microsoft SCCM provider uses PowerShell cmdlets for data discovery. | Microsoft Endpoint Configuration Manager spoke is updated to use the REST protocol for data discovery. This improves the performance and reduces load on MID Server as REST supports pagination. |
| Software revocation | CSD can revoke software requested using the CSD catalog. CSD can also uninstall software using SCCM when revocation is triggered from the reclamation candidates for SCCM provider. | CSD 2.0 can revoke software requested using the CSD 2.0 catalog. CSD 2.0 can also uninstall software using Microsoft Endpoint Configuration Manager, Microsoft Intune, and Jamf when revocation is triggered from the reclamation candidates. |
| AI agent | Description |
|---|---|
| Catalog item creation AI agent | Automates the creation of catalog items for applications provided by service providers like Microsoft Intune and Jamf. The agent also manages software models, configurations, group associations, and catalog item generation.**Note:** This version of CSD 2.0 supports Microsoft Intune and Jamf providers only. |
| Microsoft Endpoint Configuration Manager collection creation management AI agent | Creates collections in Microsoft Endpoint Configuration Manager. The agent prompts for required collection details, validates inputs, and requests confirmation before creating the collection. The agent also handles common errors and reports the outcome of the operation. |
| Microsoft Endpoint Configuration Manager collection deletion management AI agent | Deletes collections in Microsoft Endpoint Configuration Manager. The agent collects the required inputs, checks for dependencies, and requests confirmation before deletion. The agent also attempts to resolve dependencies automatically and reports the result. |
| Microsoft Endpoint Configuration Manager collection membership addition AI agent | Adds collections as deployment targets for applications in Microsoft Endpoint Configuration Manager. The agent gathers the required information, confirms the action, and handles errors that occur during the operation. |
| Microsoft Endpoint Configuration Manager collection membership removal AI agent | Removes device or user members from collections in Microsoft Endpoint Configuration Manager. The agent guides users through the required inputs, confirms the action before execution, and handles errors during the process. |
| Microsoft Endpoint Configuration Manager application targets addition AI agent | Adds device or user targets to collections in Microsoft Endpoint Configuration Manager. The agent prompts for the required details, validates inputs, requests confirmation, and reports the result of the operation. |
| Microsoft Endpoint Configuration Manager application targets removal AI agent | Removes collections as targets from applications in Microsoft Endpoint Configuration Manager. The agent gathers the required inputs, confirms the action, and handles errors while performing the removal. |
| Sample agentic workflow | Description | AI agents used | Always ON by default? |
|---|---|---|---|
| Microsoft Endpoint Configuration Manager Collection Management Agentic Flow | Manages Microsoft Endpoint Configuration Manager device and user collections and their application assignments. This agentic workflow interprets user requests, separates them into discrete collection and deployment tasks, and coordinates the required operations to create or delete collections, manage membership, and assign or remove application targets in a controlled, sequential manner. | - Microsoft Endpoint Configuration Manager collection deletion management AI agent - Microsoft Endpoint Configuration Manager application targets removal AI agent - Microsoft Endpoint Configuration Manager collection membership addition AI agent - Microsoft Endpoint Configuration Manager collection creation management AI agent - Microsoft Endpoint Configuration Manager application targets addition AI agent - Microsoft Endpoint Configuration Manager collection membership removal AI agent | No**Note:** To activate the workflow, see [Activate an agentic workflow template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/activate-aia-use-case.md). |