Agent Policy
Agent Policy controls selected Lanview Agent behaviour in the logged-in user session on managed Windows devices.
The Lanview Client service remains the machine-level runtime and maintains the connection to Lanview Server. The Lanview Agent handles supported user session features, such as user visible prompts and Remote View related behaviour.
Agent Policy allows administrators to decide which Agent behaviours are available globally, by group or for an individual device where supported.
Currently, Agent policies can only be assigned to devices or device groups. We will consider adding Agent policies to user levels if the demand is there.
Changes to Agent Policies are sent immediately to online devices and where a device is offline, it will recieve the new policy package when it connects to Lanview Server.
Client and Agent roles
Lanview Client runs as the device-side service.
Lanview Agent runs in the logged-in user session.
What Agent Policy can control
Agent Policy can control user session behaviour such as:
- whether Agent Icon is shown in the system tray
- whether Remote View related user notifications are shown
- whether a user can decline a Remote View or Remote Control request where supported
- device or group specific overrides for supported Agent behaviour
Where to configure it
Agent Policy can be managed from:
- Server settings for global defaults
- group settings for group level overrides
- Device Window settings for device level overrides
Use Studio to view and change these settings. Lanview resolves the effective value for the device or group.
Inheritance
Agent Policy can use global, group and device values.
A typical model is:
- Server default or global value
- group override where configured
- device override where configured
Lanview uses the final effective value for the device or group.
Remote View relationship
Agent Policy is closely related to Lanview-native Remote View and Remote Control because user session behaviour may be required for prompts, indicators and visible desktop interaction.
Remote View permissions and Remote View policy are still separate controls.
A user may have permission to request Remote View, but the current policy and Agent behaviour must also allow the session to proceed.
Permissions
Use the current permission catalog to confirm Agent Policy settings permissions.
Remote support permissions such as remote.view and remote.control are related but do not replace Agent Policy management permissions.
Audit behaviour
Use the audit documentation for the installed version before relying on Agent Policy changes for compliance reporting.
Remote View and Remote Control actions have their own audit records and reason behaviour.
Common problems
The user cannot decline a request
User decline behaviour is policy controlled. Check the effective Agent Policy for the device.
Notifications are not shown
Check the effective Agent Policy and whether the Agent is running in the logged-in user session.
A device behaves differently from its group
The device may have a device level override. Review the effective value shown in Studio in the Device window, Settings page.
Guidance
Use Agent Policy to match support behaviour to the type of device and the organisation's user awareness requirements.