Renew licenses transfer installations and manage seats
Overview
Section titled “Overview”Renewal and transfer use newly signed license documents with the correct installation identity and supersession lineage. Named-user licensing counts active user accounts rather than concurrent sessions. Deactivating an account and reactivating it have different seat effects.
Purpose
Section titled “Purpose”Keep entitlement current while avoiding seat-allocation failures or an unsupported transfer to a different installation.
Prerequisites
Section titled “Prerequisites”-
Authorized License Management and user-administration access for the intended actions.
-
The current license identity and a current installation request.
-
An approved renewal, seat change or transfer from the issuer.
Procedure
Section titled “Procedure”-
Review Named users in License Management. Compare active users with licensed users and remaining seats before creating or reactivating accounts.
-
For additional seats or a renewal, obtain a signed replacement through the approved issuer process. The replacement must preserve the required license lineage and identify the installed license it supersedes.
-
Select the new file, choose Verify License, then Upload / Apply Renewal. Recheck dates, edition, seat capacity and capabilities after application.
-
For a seat reduction, reconcile the legitimate active-user population first. The system rejects a limit below current active use; do not delete business history to make an entitlement fit.
-
For replacement hardware or a new installation identity, generate a request from the replacement installation and follow Transfer / Recovery guidance. Obtain an authorized superseding license rather than copying or editing an old file.
-
After an upgrade or normal restore that preserves the installation identity, verify the installed license and seat count. Retain the approved recovery and entitlement records together for handover.
Expected result
Section titled “Expected result”The current installation has a valid replacement entitlement, accurate named-user capacity and a recorded renewal or transfer history.
Important notes
Section titled “Important notes”-
Each active user counts once; disabled users do not count, and the number of sessions is irrelevant.
-
Creation and reactivation allocate seats on the server. Concurrent administrators cannot safely bypass a full seat limit by submitting at the same time.
-
Role changes do not consume another seat. The current CRM has no pending-invitation seat model.
-
Offline revocation is governed by replacement and expiry. Do not describe it as immediate online revocation.
Troubleshooting
Section titled “Troubleshooting”-
If a user cannot be created or reactivated, check available seats and the active-user count before changing role permissions.
-
If renewal fails, compare the replacement’s installation and superseded-license identity with the current installation and contact the issuer.
-
If a restored system has unexpected entitlement state, preserve the recovery evidence and involve the license/recovery owner. Do not generate a new identity merely to bypass validation.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗