Licensing
Lanview licensing is enforced by Lanview Server.
The Server validates licence state, applies device limits and controls restricted behaviour when the licence state does not allow an action.
This article describes visible licensing behaviour for administrators.
Licence summary
Lanview Studio can show licence summary information where the user has permission.
The summary may include visible licence state, compliance status and operational messages needed by administrators.
Adding and removing licences
Licence add and remove actions are performed through Lanview Studio where available.
Lanview Server validates the supplied licence and records whether it was accepted or rejected.
If a licence is rejected, use the visible error state or support process. Do not attempt to edit Server licensing state directly.
Device limits
Licensing can affect device approval and management.
If the managed device count exceeds the licensed limit, Lanview Server may block approval or restrict actions depending on the current licence state and configured behaviour.
A device approval failure caused by licensing should be treated as a licensing issue, not a Lanview Client problem.
Restricted behaviour
When the licence state is not compliant, Lanview may restrict selected actions.
Visible behaviour can include warnings, blocked restricted actions, blocked console access or refusal to approve additional devices.
The exact behaviour depends on the current licence state and product configuration.
Permissions
Use the current permission catalog to confirm licensing management permissions.
Device approval still requires normal device management permissions, but the Server can refuse the action if licence limits are exceeded.
Audit behaviour
Lanview audits licensing related events.
Audit records can include:
- licence added
- licence rejected
- licence removed
- licence validation failed
- licence grace state over limit
- licence restricted state over limit
- licence compliance restored
- restricted action blocked
- console blocked by licence state
- device approval blocked by licence limit
Audit records should not expose raw licence tokens or protected validation data.
Common problems
A licence is rejected
Check that the correct licence has been supplied and that the key is not missing characters from the beginning or end if it has been copied and pasted.
Let us know if the licence should be valid but is not working.
Device approval is blocked
The licence limit may have been reached. Review the licence summary and current managed device count.
Console access is blocked
Some licence states can restrict console behaviour. Review the licence summary and audit log for the reason.
Security boundaries
Keep licence material and validation details out of examples, logs, screenshots and support material. Use the normal licence import and support process rather than copying or editing licence data manually.
Guidance
Keep licence management limited to authorised administrators.
Review licensing state before large-scale Client deployment or device approval work. It is easier to resolve licensing limits before a large number of devices are waiting for approval.