--- sourceDocument: Yokohama Data and Automation sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/integrate-applications Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Data and Automation ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # SCCM software revocation # SCCM software revocation {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read An administrator can revoke software without any user interaction using Microsoft System Center Configuration Manager (SCCM) if the software configuration specifies an SCCM uninstall collection, even if the software was installed by some other process or user. ## Revoke software deployed through the service catalog {#ariaid-title2} Software deployed by SCCM can be revoked, but only when the software's status is Installed and the application associated with the software configuration has an uninstall collection configured. ### Before you begin * Create an [SCCM configuration record](https://www.servicenow.com/docs/Dinv1G6xplK_VY8RJk~uzQ "To create catalog items for SCCM software deployment or to configure your instance to revoke software through SCCM, you must first associate that software with a collection through an SCCM configuration.") for the application that names an appropriate uninstall collection. * Associate the [CSD catalog item](https://www.servicenow.com/docs/Sh_wrJG9lJ70FcnXVkmpMg "Using the applications discovered on the SCCM server, create a catalog item for an application you want to offer for distribution from the service catalog.") for the application with the SCCM configuration that specifies the uninstall collection. {#t_RevokeSoftwareInstalledFromSCCM__ul_amk_trp_mv} Role required: sn_client_sf_dist.csd_admin or admin A workflow called [Revoke SCCM Application](https://www.servicenow.com/docs/55o7lms8Aw6eD_SQQR5cbg#r_SCCMSoftwareRevocationWorkflow "The Revoke SCCM Application workflow moves a user or device from an install collection to an uninstall collection to revoke software installed from Microsoft System Center Configuration Manager (SCCM).") moves either the user or the device from its respective collection and adds it to the appropriate uninstall collection. When SCCM performs an internal policy check and finds the user or device in the uninstall collection, SCCM removes the related software package from the client computer. ### Procedure 1. Navigate to AllClient Software DistributionReportsRequested Software. 2. Open the record for the SCCM software package you want to revoke. The package must have a Status of Installed to be revocable. 3. Under Related Links, click Revoke software. This action runs the Revoke Client Software workflow, which triggers the Revoke SCCM Application subflow that moves the user or device from the install collection to the uninstall collection. When SCCM performs an internal policy check and finds the user or device in the uninstall collection, SCCM removes the related software package from the client computer.{#t_RevokeSoftwareInstalledFromSCCM__p_TriggerSubflow} ## Revoke unentitled software {#ariaid-title3} An administrator can revoke software using Microsoft System Center Configuration Manager (SCCM) that a user is not entitled to use even if the software was installed by some other process or user. ### Before you begin To revoke software using SCCM, you must create an [SCCM configuration record](https://www.servicenow.com/docs/Dinv1G6xplK_VY8RJk~uzQ "To create catalog items for SCCM software deployment or to configure your instance to revoke software through SCCM, you must first associate that software with a collection through an SCCM configuration.") for the application, in which the appropriate software Discovery model is defined. See [Software discovery models](https://www.servicenow.com/docs/access?context=c_DiscoveryModels&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US). Role required: sn_client_sf_dist.csd_admin or admin Client Software Distribution (CSD) uses [Software Asset Management](https://www.servicenow.com/docs/access?context=c_SAMOverview&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) to identify unentitled software installations. Discovery detects the software on the user's machine, and SAM determines if the user or device is entitled to use that software. This might include software that was not installed through a catalog request or software that the user installed without approval. If the software installation's Discovery model is associated with an SCCM software configuration that has an uninstall collection defined, then an administrator can use CSD to revoke that software from the user's machine without involving the user. ### Procedure 1. Navigate to AllClient Software DistributionReportsInstalled Software Not Entitled. 2. Select the record for the installation that has unentitled users. 3. Under Related Links, click Revoke software. This action runs the Revoke Client Software workflow, which triggers the Revoke SCCM Application subflow that moves the user or device from the install collection to the uninstall collection. When SCCM performs an internal policy check and finds the user or device in the uninstall collection, SCCM removes the related software package from the client computer. Figure 1. Revoking a software installation ## SCCM software revocation workflow {#ariaid-title4} The Revoke SCCM Application workflow moves a user or device from an install collection to an uninstall collection to revoke software installed from Microsoft System Center Configuration Manager (SCCM). For the revocation workflow to run, the software package must have a status of [Installed](https://www.servicenow.com/docs/NaUwjLB~u_uT27Vd1rVpfA "After SCCM deploys software to a target computer, client software distribution (CSD) detects the installation and validates its status.") and must be pre-configured for an appropriate uninstall collection. See [Revoke software deployed through the service catalog](https://www.servicenow.com/docs/access?context=c_SCCMSoftwareRevocation&version=yokohama&pubname=yokohama-servicenow-platform§ion=t_RevokeSoftwareInstalledFromSCCM&ft:locale=en-US) for configuration instructions. When an administrator initiates the revocation process, the system launches the Revoke SCCM Application workflow to move the user or device collection associated with installation to the appropriate SCCM uninstall collection. When the SCCM server performs a policy check, it finds the additions to the user or device uninstall collection and revokes the software package associated with that collection. The workflow employs two custom activities, [Remove from User Collection](https://www.servicenow.com/docs/pb6aqMofl3JqfSz~GQCxPw "The Remove from User Collection activity removes a user from a Microsoft System Center Configuration Manager (SCCM) user collection.") and [Remove from Device Collection](https://www.servicenow.com/docs/IF0rWFoDqNu8lI2W8xCCZQ "The Remove from Device Collection activity removes a device from a Microsoft System Center Configuration Manager (SCCM) device collection."), to remove either the user or the device from its original collection. The workflow then adds the user or device to the appropriate uninstall collection on the SCCM server with the [Add to User Collection](https://www.servicenow.com/docs/xeiGNH7SjVvlpIRcRweLZg "The Add to User Collection activity adds a user to a Microsoft System Center Configuration Manager (SCCM) user collection.") or [Add to Device Collection](https://www.servicenow.com/docs/pl0AnubYkPv1PQFSkei6Zg "The Add to Device Collection activity adds the specified device into a Microsoft System Center Configuration Manager (SCCM) device collection.") activity. Note: This workflow is triggered by the Revoke Client Software workflow as a subflow. *[\>]: and then