Streamlining Software Management with Removal Candidates in ServiceNow

[Sean_Walker]

Streamlining Software Management with Removal Candidates in ServiceNow

Effective software asset management (SAM) is crucial for maintaining an efficient and compliant IT environment. One important component of this process is managing Removal Candidates, which are software installations identified for potential uninstallation. Properly handling these candidates can optimize software usage, reduce costs, and enhance compliance.

For a deeper understanding of how to leverage Removal Candidates, be sure to watch the “Ask a Ranger: Software Asset Management” video series Identifying Removal Candidates and Reclaiming Software Installations

What Are Removal Candidates?

Removal Candidates refer to software installations that have been flagged for removal from the environment. Identifying and managing these candidates ensures that software inventory remains relevant and compliant with organizational policies.

How Are Removal Candidates Created?

Removal Candidates are added to the list through several key processes:

1. Reclamation Rules:
• Automated Creation: Reclamation Rules automatically generate Removal Candidates when specific conditions are met. These rules help identify software that is underused or no longer needed, facilitating timely and efficient software management.
2. Remediation Options:
• Proactive Management: When a SAM Manager uses a remediation option, Removal Candidates are created to address identified software issues. This proactive approach helps in managing software inventory more effectively.
3. Restricted Software Installations:
• Automatic Detection: Software Models flagged as Restricted will automatically generate Removal Candidates when installations are detected. This feature ensures that unauthorized or non-compliant software is identified and managed promptly.
4. Manual Creation:
• Custom Management: Removal Candidates can also be manually created from the License Usage workspace, providing flexibility in addressing specific software removal needs.

Managing Removal Candidates

Once Removal Candidates are identified, the SAM Manager has several options for handling them:

• Reclaim or Ignore:
• Reclaim: Selecting the Reclaim option triggers the Reclamation Workflow, which initiates the process of reclaiming the software. If the Reclamation Rule includes a notification, the user will be notified and the approval process will begin.
• Close or Skip: If the candidate is deemed unnecessary for removal, the SAM Manager can choose to ignore it by closing or skipping the task.
• Removal Methods:
• On-Premises Software:
• Manual Removal: Generate a task for manual uninstallation.
• Automatic Removal: Utilize Client Software Distribution (CSD 2.0) for automatic uninstallation. Note that CSD 2.0 must be set up within the instance, and the SCCM environment must be configured to support removal using uninstall packages. This setup requires thorough planning and testing.
• SaaS Subscriptions:
• Manual Removal: Generate a task to remove user subscriptions.
• Automatic Removal: Execute removal via an API call to the publisher's API. It is crucial to understand what the specific Publisher API allows, as automatic removal might lead to data loss. Ensure that the default behavior aligns with your organization’s data retention policies.

For more detailed guidance on reclaiming user subscriptions, refer to the ServiceNow Docs on Reclaiming User Subscriptions

Conclusion

Effectively managing Removal Candidates is essential for maintaining a well-optimized and compliant software environment. By leveraging automated processes, manual management options, and understanding the specific requirements of on-premises and SaaS software, organizations can streamline their software asset management efforts. This approach ensures that software installations are efficiently handled, reducing costs and enhancing overall compliance.

For a deeper delve into this topic please watch the following video provided below.

Identifying Removal Candidates and Reclaiming Software Installations