Administer
Register or renew an offline installation
Transfer the correct request and activation through Support while retaining the original installation identity.
Prepare the exchange
Use the original installation, the authorised owning account, a connected device and an approved file-transfer method. Keep the installation and its protected state available throughout the exchange. The same 720 powered-on-hour allowance applies offline.
Follow the matching request
- As System Owner, review Registration & licence and select the applicable offline registration or renewal operation.
- Export the request from that installation and transfer its encrypted file unchanged.
- Open the configured Support destination, sign in where required, review the terms and complete the requested approval.
- Return the approved activation to the original installation and import it through the corresponding Product operation.
- Check that Product accepted the activation and recorded the expected term.
The compiled production default for initial offline registration is Pūnaha offline registration. Registration, renewal and recovery file purposes must match the action. Final end-to-end acceptance and visible action labels remain pending.
If the exchange fails
Keep the request reference and safe error message. Preserve the installation’s identity, accepted terms and original evidence. Ask the authenticated Support case area for the correct next step. A new export cannot reset the allowance.
Renew or export before the 720 powered-on-hour cutoff. At the cutoff, normal processing, tenant functions, administration, customer-data access and exports stop. Customer data is retained. Sign-in and the registration, renewal and identity functions needed to restore registration remain available.
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.