Description: This article describes the overall purpose and process of the Software workflows in ALM/LPM and how to configure them. The overall process has the ability to bring software licenses and usage information from LDMS and automatically build distribution packages in LDMS to remove software that's not being used and reclaim the licenses. All of these processes rely on a properly configured implementation of Software License Monitoring (SLM) or software monitored through Data Analytics (DA) in LDMS.
Software Synchronization Workflows (Software Entitlement Sync and Software Usage Sync)
These two workflows start the process. As such they should be scheduled on a periodic basis. How often they are scheduled will depend on how often devices and software change in the environment. Each workflow runs a series of synchronization packages and then calls the Software Compliance workflow.
Software Compliance Workflows (Software Compliance and Software Compliance 2)
These are sub-workflows that are called by the Software Synchronization Workflows. They are designed to perform a large number of calculations and other actions needed after data is collected from the LDMS Core with the Software Synchronization workflows.
Software Reclamation Workflows (Remove Software and Software Reclamation Request)
The Software Reclamation workflow is launched via the Software Reclamation Event Listener. The reclamation workflow will go through a series of actions before calling the Remove Software workflow that creates the distribution task in LDMS where the removal of the software will take place.
Setup and Configuration:
Each of the following Workflows should be verified with the green button to check the workflow for errors. If there are any errors double-click the error and it will take you to the action/portion of the workflow that needs configuration. (See screenshot below)
Workflows to be checked:
- Software entitlement sync
- Software usage sync
- Software Compliance
- Software Compliance 2
- Remove software
- Software reclamation request
After clicking the green check mark you may see some messages at the bottom of the Designer Console:
Double-clicking the green checkmark will take you to the location that needs configuration:
Fill out the box with a user desired to run the synchronization package. A good user will be a service account or other account that was used to configure ALM. This user will also need to have the proper rights on resources used in the synchronization package. More details in the next section.
In addition to Run As other configuration settings need to be taken into account. As shown in the screen shot above Success Criteria needs to be accounted for. Leaving it the default 100% will cause the synchronization package to fail if it encounters 1 error which will result in the entire workflow to stop. Stopping for all errors may be good for initial setup and configuration but may not be desired all of the time.
Synchronization Package Configuration
Configuration of the Synchronization Packages takes place inside the web console. Most of the details of these synchronization packages are already set by default. An ODBC connection to the LDMS Core will need to be established. (See link below for details) Once the connection is established the "test" buttons should work and allow access to the other portions of the synchronization package however as mentioned before changing the other areas is not needed. The test only needs to pass. (Note: Packages 9 and 10 for software downgrade will need an ODBC connection to the ALM database and not the LDMS Core).
Packages to be edited:
- LANDesk Management Suite software manufacturers
- LANDesk Management Suite monitored products
- LANDesk Management Suite software licenses
- LANDesk Management Suite software
- LANDesk Management Suite software license mapping
- LANDesk Management Suite Computers
- LANDesk Management Suite product usage
- LANDesk Management Suite computer usage mapping
- Software downgrade rights log 1
- Software downgrade rights log 2
Each of the synchronization packages needs to write/modify the destination Asset or Resource. The user configured in the package (or as part of the Run As mentioned above) will need security rights to perform the actions. The supporting resource "Product" and "Manufacturer" are two examples. The screenshot below shows the properties screen of the Product supporting resource. On the Security Tab you can add the desired user and add at least Create and Modify rights.
In order to launch the two parent workflows (Software entitlement sync and Software usage sync) they will need to be scheduled. The screenshot below shows an example of the scheduling screen. When and how often these workflows are scheduled will depend on the amount of data changed in devices and software in the environment. Also, these workflows launching all of the previously mentioned synchronization packages which will take a lot of time and access the database. After hours is recommended after configuration is finished. When you are ready to test the workflows you can change the Start Time to within 5 minutes of the current time and set the "Range of recurrence" to end after 1 occurence. These settings are good for testing purposes so once any problems are worked out the schedule can be updated to a regular occuring schedule each day or week etc.