Contents
-
Introducing AppClarity
-
Implementing AppClarity
-
Configuring AppClarity
-
Using AppClarity
-
AppClarity user roles
-
Running your first License Compliance Summary
-
Viewing software install counts across all devices
-
Viewing product usage
-
Viewing product compliance
-
Viewing your effective license position
-
Creating a license entitlement
-
Creating and linking a maintenance entitlement
-
Creating an entitlement using a SKU
-
Creating an agreement entitlement
-
Importing entitlements from a folder
-
Managing compliance for user-based licenses
-
Calculating license demand
-
Excluding devices from License Demand Calculation using Management Groups
- Reclaiming a product based on its usage
-
Stopping a reclaim policy
-
Viewing the software reclaim reports
-
Scheduling AppClarity reports
-
AppClarity user roles
-
Troubleshooting
-
Training
-
Reference
Inventory fetches information from its data sources to return details of how products are being used, wherever available. Reclaim Administrators who are interested in reclaiming unused software in order to recycle licenses can use this information to set their reclaim policies.
Reclaiming a product based on its usage
We'll start with a simple example based on reclaiming unused versions of a software. In this case the policy we set up will be soft (optional) in that it will only trigger a reclaim that allows the user to opt out and keep the software, as long as they provide suitable justification. In this example we use the global management group, more on that later.
This example assumes that you have already run a sync on your selected inventory repository to retrieve inventory data from one or more connector sources. As a result of doing this a number of reports are automatically run. The essential one, particularly for reclaim, is:
- Reclaim Product Usage is run on the compliance repository associated with your chosen inventory repository. In our example we use the Default Compliance repository (which is automatically associated with the Default Inventory).
When setting up a reclaim policy, for example for Notepad++, if you know uninstall command line, then you may enter it inside Uninstall string box for the version. Please follow these rules.
Each uninstall command line must be enclosed in double quotes - for example:
"C:\Program Files (x86)\Notepad++\Uninstall.exe"
You can use multiple command lines for same product version which are tried in succession. Ensure each command line is enclosed in double quotes, and separated by double pipe character ("||"). For example:
"C:\Program Files (x86)\Notepad++\Uninstall.exe"||"C:\All Softwares\Notepad++\Uninstall.exe"||"C:\Tools\Notepad++\Uninstall.exe"||"D:\Softwares\Notepad++\Uninstall.exe"
Responding to an end-user request to retain reclaimable software
After you've created some opt-out reclaim policies you will need to keep track of the ones that are currently in operation and requires attention from reclaim administrator.
To administer software reclaim policies:
- Navigate to the AppClarity→Reclaim→Policies page, you may need to refresh the page if you are already there.
- Locate the required reclaim policy, you should see that the Admin Actions column shows 1, indicating that there is one pending request to be processed.
- Clicking on the number in the Admin Actions column displays the Administration page for that reclaim policy, please refer to Administration page for more details.
- Here you can see the reclaims that have been completed for this policy and the reclaims still in progress. At the bottom of the page is the Reclaim Override Management table that lets you respond to requests for retaining software. To respond to a particular request you do the following:
- Check the checkbox at the start of the request entry in the table
- You then have the option of:
- Clicking the Accept button to accept the end-user request to retain the software
- Clicking the Reject button, in which case the optional software reclaim will be converted to a mandatory reclaim and the software will be removed without any further interaction with the end-user in very next cycle.
- In our example we click the Accept button to allow the end-user to start using the software again, as they indicated in their reason.
- A notification popup appears saying that the user's opt out request has been accepted and that the software will not be reclaimed at this time. Click on OK to close the notification.
- Clicking on the AppClarity→Reclaim→Polices page shows that there are now 0 Admin Actions for this software reclaim policy.
Resolving overlapping reclaim policies
As a result of defining reclaim policies you may find that they overlap in terms of the devices and products they apply to. Only one policy can be applied for a given device and product and to resolve the conflict you can set the precedence to decide which of your policies are preferred. This becomes significant when management groups are involved.
In this example we create three reclaim policies that target unused installations of Microsoft Project Professional. These overlapping policies will have different reclaim actions for unused software depending on the management groups, that come from the management group example above.
We will use three management groups which correspond to OU configured on our example ACME AD site. The first one, Workstations contains all the devices that are present in the other two, Executive and Finance, but those two sub OU are mutually exclusive. This means that devices in the Executive management group are also in the Workstations management and likewise devices in the Finance management group are also in the Workstations management group.
The purpose of this example is to create three reclaim policies for unused installations of Microsoft Project Professional for each of the Workstations, Executive and Finance management groups. Each reclaim policy will have a different reclaim action according to the management group they are associated with. However, in practice this means that the devices in the Executive and Finance management groups with their own reclaim policies will also be eligible for the reclaim policy associated with the Workstations management group.
For this reason a mechanism exists to set the precedence for the reclaim policies associated with a particular program so that you can ensure that the devices in each management group get the right reclaim policy.
By the end of this example you will have defined 3 new reclaim policies:
- In the Workstations management group we will create a general policy that performs a mandatory uninstallation.
- In the Finance management group we will create an opt-out uninstallation where the end-user can choose to keep the software.
- For the Executive management group we will create a do not uninstall action for Microsoft Project Professional.
You will then have set the precedence for the policies so that they are selected in the correct order when a device runs its scheduled reclaimer policy retrieval.