Device Approval
Device Approval controls when a newly connected Lanview Client becomes available for management.
When a device first connects to Lanview Server, Lanview records it and shows it for review. An authorised Lanview user can then approve or reject the device.
Approval helps prevent unexpected or unauthorised devices from being managed automatically.
Approval status
A device can have different lifecycle states depending on how it has been handled in Lanview.
Common states include:
| Status | Meaning |
|---|---|
| Pending | The device has connected and is waiting for review. |
| Approved | The device has been accepted for management. |
| Rejected | The device has been rejected and is not available for normal management. |
| Blocked | The device identity has been blocked from use. |
| Deleted | The device record has been removed from active management. |
The exact actions available depend on the user’s permissions and the current device state.
Viewing pending devices
To review pending devices:
- Open Lanview Studio.
- Go to Devices.
- Open the Pending Approval view.
- Review the devices waiting for approval.
Only approve devices that are expected and recognised.
Approving a device
To approve a device:
- Select the pending device in Lanview Studio.
- Choose the approval action.
- Enter a reason if Lanview prompts for one.
- Confirm the approval.
After approval, the device becomes available for normal management according to the user’s permissions and the device’s connection state.
Rejecting a device
Reject a device when it is not expected, should not be managed, or needs to be investigated before approval.
Rejected devices can be reviewed later by an authorised administrator.
Blocking and unblocking a device
Blocking is stronger than rejection. Use it when a device identity should not be allowed to participate in Lanview management.
An authorised administrator can later unblock the device from the Devices module. Unblocking removes the block, but it does not automatically approve a pending or rejected device.
Review the original reason for the block before restoring access.
Rebuilds and replacement devices
Device Approval can also be required when a device is rebuilt or replaced. However, when Windows has been reinstalled on the device and reconnected to Lanview, some hardware metrics will be used to determine if the device should be automatically reassociated with a previous device in Lanview. Where Lanview is not completely certain, manual reassociation is possible by an administrator.
Reassociation should be used when an administrator is satisfied that the newly connected Client represents the expected physical or logical device.
Reassociation options are available in the context menu of the Pending Approval device group.
Required permissions
| Permission | Allows |
|---|---|
devices.view | View devices in Lanview Studio. |
devices.manage | Approve, reject and manage device records. |
device.reassociate | Approve pending devices as rebuild or replacement reassociations. |
devices.delete | Delete device records from active management. |
devices.block | Block device access to Lanview. |
Additional target permissions may apply when performing actions against approved devices.
Reasons and audit prompts
Lanview can require a reason before allowing device lifecycle actions such as approval, rejection, deletion or blocking.
Reasons are stored with the audit record so the action can be reviewed later. They are commonly used to link administrative decisions to a deployment record, support request, rebuild process or security investigation.
The organisation using Lanview decides what is considered a valid reason. Lanview records the reason supplied by the operator and applies the minimum reason length configured on Lanview Server.
What gets audited
Lanview Server records audit events for device lifecycle activity.
Audit records may include:
- Device approved.
- Device rejected.
- Device deleted.
- Device blocked.
- Device renamed.
- Device identity policy changes.
- Device reassociation activity where applicable.
Audit records are designed to show who performed the action, which device was involved, what action was taken and what reason was supplied where required.
Console commands
Related Lanview console commands may be available for authorised administrators, including:
device.approve <DeviceId>
device.reject <DeviceId>
device.delete <deviceId|machineName>
device.block <deviceId|machineName>Broad approval commands should be used with particular care because they can affect multiple pending devices.
Troubleshooting
The Device Window will not open
Lanview Studio does not open the full Device Window for an unapproved device. Approve the device first if it is expected and should be managed.
A device is still pending after installation
This is normal until an authorised Lanview user approves it.
A device appears with an unexpected name
Do not approve the device until it has been checked. Review the device details and follow the organisation’s approval process.
A rebuilt device appears as pending
Review the reassociation information presented by Lanview. Reassociation should only be approved when the administrator is satisfied that the device should continue under the existing Lanview record.