Client software distribution ordering process
Summarize
Summary of Client Software Distribution Ordering Process
The Client Software Distribution (CSD) 2.0 process allows users to order software through the service catalog. Orders can be placed by individual users or by approved users on behalf of others. The configuration options for catalog items vary based on the setup, specifically regarding access types and lease terms.
Show less
Key Features
- Lease Dates: Users must specify a lease start date for the software. If configured for revocation, an optional lease end date can also be set, with validation ensuring future dates are selected.
- Access Types:
- Restricted: The logged-in user orders software only for their own device, which is selected from a list of assigned devices.
- Delegated: The logged-in user can order software for another user. The order form includes a User field to select the recipient and lists devices assigned to that user.
- Approval Workflow: Software ordered on behalf of another user triggers an approval request to the user’s manager, except when the requester is the manager.
- End Date Management: Managers can set lease end dates tied to contract expirations, with automatic uninstallation via Microsoft Endpoint Configuration Manager upon expiration.
Key Outcomes
By utilizing CSD 2.0, ServiceNow customers can efficiently manage software orders, ensuring proper deployment and compliance with organizational policies. The system automates approval processes and lease management, streamlining the ordering experience for users and managers alike.
Software deployed by CSD 2.0 can be ordered from the service catalog by individual users or by approved users on behalf of others.
CSD 2.0 catalog items have different options, depending on how ordering is configured.
Lease start and end dates
All software deployed by CSD 2.0 requires users to specify the beginning date for the lease.
If the catalog item is configured for revocation (uninstall), the form displays the Lease end field, which allows the requester to define an end date and time for the lease. The system validates user input in these fields to ensure that the dates selected define a future window. The Lease end field is not mandatory and can be left blank to order software with no end date.
Software offered only to the logged in user
If the software catalog item is configured with Access Type as Restricted, the User field does not appear on the order form. The logged in user selects the device on which to deploy the software from the Device to install this software on field. Only those devices assigned to the logged in user appear in the list.
In this example, a user has logged into the service catalog to order Google Chrome for the assigned computer. User selects the machine from a list of devices and selects the date and time the lease should begin.
Software ordered on behalf of another user
If the software catalog item is configured with Access Type as Delegated, the User field appears on the form. The logged in user can select any user from this field. The Device to install this software on field only lists the devices assigned to the user selected in the User field. If an approval is required for software ordered on behalf of another user, the system automatically sends an approval request to the manager of the user receiving the software. The approval is skipped if the requester is the named user's manager.
In this example, a manager is ordering Google Chrome for a contractor. The manager selects the contractor from the User field and then chooses a computer from the list of devices assigned to the contractor. This software has a Microsoft Endpoint Configuration Manager uninstall collection configured, which enables the manager to select an end date for the lease that coincides with the end of the user's contract. When the lease expires, Microsoft Endpoint Configuration Manager automatically uninstalls the software from the device.
- For Jamf, the device must have its serial number populated in the device table.
- For Microsoft Endpoint Configuration Manager, the name must be populated.