Client Software Distribution (CSD) 2.0 – End-to-End Setup & Workflow for Intune & Jamf

[monica190]

Prerequisites

Before beginning the setup for CSD 2.0, ensure the following plugins are installed:

• CSD 2.0 Plugin

• Microsoft Intune Spoke

• Jamf Spoke

Additionally, verify that your selected providers (e.g., Intune, Jamf) are properly integrated and enabled.

---

Microsoft Intune Integration Steps

a) Server Instances Setup

• Navigate to: Server Instances

• Click: Connection & Credential Alias

• Create an HTTPS connection using the alias to securely link credentials.

b) OAuth Token Creation

• Set up OAuth tokens for Intune.

• Once configured, click the “Discover Now” related link to trigger a sync.

c) Application Data Population

• Once discovery completes (track from flow execution sorted by created date), the following are automatically populated:

  • Applications

  • Groups

  • Deployments

---

Application Configuration in CSD

a) Software Model Association

Navigate to:
🡺 Applications > Open a Record > Associate SAM Software Model

From the related links:

• Click “Create Catalog Item”

• Fill in application details.

• Set Access Type as:

  • Restricted

  • Delegated

b) Software Configuration

• Click “Create Software Configuration”

• Enter:

  • Application Name

  • Install Group

  • Uninstall Group

  • Deployment Type

• Repeat this step for all applications required.

All configurations are stored in the CSD Catalog Item Fulfillment Configuration table.

---

Catalog Item and Lease Fields

On the catalog form, the following fields are available:

• Lease Start Date

• Lease End Date

• User (only visible if Access Type is set to Delegated)

Field Validation Rules:

• Lease Start Date must be > current date

• Lease End Date must be > current date & > Lease Start Date

---

CSD Workflow Execution

When the request form is submitted, the following process is triggered:

a) Approval & License Validation

• First step: Approval to the Manager

• Next: License Compliance Check

• If license is available → CSD moves to deployment phase

---

Records Created Post-Submission

After approval, the system creates:

Table Purpose

sn_csd_lease_schedule	Stores RITM, application metadata
sn_csd_lease_execution	Triggers the software deployment
sn_csd_lease_manager	Links RITM to schedule & execution
cmn_schedule_span	Defines scheduled duration

cmn_schedule_span:

• Name: start

• Start Time = Lease Start Date

• End Time = Lease End Date

• Notes: scheduled

---

Scheduling Logic

If Lease End Date is provided:

Two schedule entries are created:

1. Name: end notification

   • Start & End Time = Lease End Date - 5 days

2. Name: end

   • Start & End Time = Lease End Date

The Lease Execution record is set to Ready, and a script is triggered to initiate Deploy Client Software.

---

Deployment Execution

• Deploy Client Software flow is executed.

• A dynamic flow is triggered based on provider (e.g., Intune, Jamf).

• A record is created in:

  • Requested Software → sn_csd_req_software

If deployment fails:

• A tracking email is sent

• A catalog task is created with the error

• After task closure → deployment flow is retriggered.

---

Deployment Post-Processing

• Email sent to the requester confirming software is deployed.

• Lease Execution Notification is configured via a scheduled entry using Lease End Time.

• Execution status set to Ready, with script to call Lease End Notification subflow.

---

Lease End Notification

• Email reminder sent to the requester

• Lease Execution record triggers:

  • Software Revocation Subflow

---

Software Revocation Flow

• Revoke Client Software subflow is called.

• The dynamic flow calls the respective revocation flow (Intune or Jamf) based on provider.

• Software is uninstalled or access is revoked accordingly.