Home >

About License Revocation

License revocation can be useful in the following scenarios:

>Returning unused licenses – For example, you may want to return/exchange the licenses you bought earlier but are no longer required.     

>Transferring licenses from one network to another – For example, you may want to distribute some of your licenses to another office/division without setting up any connectivity between them. The new licenses received from the vendor—in lieu of the revoked licenses—can be deployed at the relocated network.

Important      

This section introduces the license revocation option in general. Since license revocation is a customizable bilateral process—driven mainly by your vendor. The actual process may vary from the one described here. If the revocation process makes use of the WlmAdmin utility, the information provided in this section may be helpful for you. Contact your vendor for exact terms and process of revoking licenses.

Notes

If your vendor has allowed you to use the option of deferred revocation (where a grace period is provided between instigating a license revoke and actual revoke), then it cannot be performed in the following situations:

>If any commuter tokens are checked out at that time

>The license happens to be a repository license and has been requested successfully.

Furthermore, licenses marked for deferred revocation cannot be commuted or requested (if repository licenses).

See Also:

>License Revocation Using Permission Ticket Option in WlmAdmin