Deactivating a Protected Application

Deactivating an application disables use of the software on the current computer, and frees up the activation to be used on another computer. This allows a customer to securely transfer a license.

You can allow unlimited deactivations per License ID, or allow a set number of deactivations. Limiting the number of deactivations stops a customer from abusing the transfer feature, such as sharing one license between two computers when the customer needs to purchase two licenses. You can manually add additional deactivations to a License ID on the SOLO Server Automation License Details page if needed.

There are multiple way to initiate a deactivation, either remotely through SOLO Server Automation or directly through the protected application. If initiated remotely, the software will deactivate locally the next time it validates with SOLO Server Automation based on the Automated License Validation options. A required validation stops a user from simply running disconnected from the Internet to avoid the validation. If initiated from the protected software, a successful deactivation will immediately deactivate the software locally, and a required validation stops a user from restoring a backup to an activated state.

For a deactivation request to be successful, the Allow Deactivations Product Option setting needs to be enabled, and there needs to be at least one Deactivation Left on the License ID that was used for the original activation. If so, a deactivation will decrement the Deactivations Left count and increment the Activations Left count, which is what allows the activation to be used on another computer. You can search for the License ID in SOLO Server Automation to bring up the License Details page which shows these fields.

It is possible to allow unlimited deactivations, but this blog posts details reasons to limit the number of deactivations.