Client Software Distribution 2.0 application
Summarize
Summary of Client Software Distribution 2.0 application
The Client Software Distribution 2.0 (CSD 2.0) application allows administrators to distribute software via the service catalog using third-party management systems. It automates software deployment and revocation, enabling the creation of necessary records like software models and catalog items. CSD 2.0 integrates with Software Asset Management (SAM) to manage software licenses efficiently.
Show less
Key Features
- Third-Party Integration: Supports Microsoft Endpoint Configuration Manager, Jamf, and Microsoft Intune for deployment and revocation.
- Custom Flows: Automate deployment and revoke software using specific flows, subflows, and actions.
- Lease Management: Defines lease periods for software, including options for lease extensions with approval.
- License Management: Allows tracking of licenses and entitlements associated with distributed software.
- Improved Data Discovery: Utilizes REST protocols for data discovery, enhancing performance and reducing server load.
Key Outcomes
With CSD 2.0, customers can streamline software distribution, ensuring compliance with licensing, and improve operational efficiency through automation. The ability to integrate with existing software management tools enables better oversight and control of software assets across the organization.
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.
Important considerations
| 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 Flow Designer. 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 are not supported currently) when revocation is triggered from the reclamation candidates. |
Application version
CSD 2.0 v1.2.2 is the latest version.