Are you leaving money on the table by allowing license deactivation?
When you allow customers to deactivate a license and move it between computers, a common question follows: how do you give customers the freedom to transfer a license while still requiring them to purchase a license for each computer that runs the software at the same time? These two goals can seem mutually exclusive, but limiting the number of times a customer can deactivate a license lets you support both. This article explains how license activation and deactivation work and why setting a deactivation limit protects your revenue without inconveniencing legitimate customers.
Electronic license activation and management
Traditional copy protection (license enforcement) means a customer cannot run the software on more machines than their license allows. Every copy of the software must be activated against a central licensing server, and that server tracks the number of activated computers. For example, if Mary and Steve both need to run the software on their own computers at the same time, they each need their own activated license.
Electronic License Management (ELM) lets you and your customers manage a license after it has been activated. If a customer has both a desktop and a laptop, or is moving to a new computer, they can deactivate the license on one computer and activate it on another, within the limits of their single-computer license. The trade-off is that this same flexibility lets users like Mary and Steve transfer one license back and forth if they do not need to run the software at the same time.
Why limit license deactivations
Activation policies and deactivation policies work together to set boundaries for how your software is used.
An activation limit stops a user from grossly abusing your activation policy by installing on more computers than their license permits. There will always be legitimate exceptions, such as a computer failing and the customer needing to activate on a replacement machine. When that happens, the customer contacts your customer service department, and a staff member can review the license server logs and assess the situation before granting an exception.
A deactivation limit works the same way for license transfers. It would be easy for two users to share a single activation by passing it back and forth between their computers. By setting a deactivation limit, you ensure that once the central license server reaches that limit, the customer has to contact your customer service department to continue. At that point your team can review the license history, discuss how the software is being used, and determine whether a second license is a better fit.
Asking a few simple questions at that moment can lead to additional sales, while still giving genuine customers a clear path to keep working.
How to apply deactivation limits
- Decide how many activations each license should allow, based on how your customers actually use the software.
- Set a deactivation limit alongside the activation limit so customers cannot transfer a single license between machines without bound.
- Adjust these limits over time as a customer's needs change, rather than treating them as fixed.
- Use the license server logs to review activation and deactivation history before granting exceptions or recommending an additional license.
Choosing a licensing system
Most license activation systems let you track and limit the number of activations assigned to each license, and these limits can usually be adjusted over time as your customers' needs change. When you evaluate a licensing system, confirm that it can also limit the number of deactivations. Both controls are needed to set complete boundaries: activation limits cap how many machines can run the software at once, and deactivation limits prevent a single license from being shuttled between users indefinitely.
SOLO Server, used with Protection PLUS 5 SDK and Instant Protection PLUS 3 (IPP3), supports both activation and deactivation limits so you can enforce these policies and review license history when a customer reaches a limit.