File Transfer
Lanview File Transfer allows authorised users to send files to managed Windows devices.
It is used for support files, installers, configuration files and other controlled payloads that need to be delivered to one or more devices.
How file transfer works
Lanview Studio uploads the selected payload to Lanview Server.
Lanview stores eligible uploaded payloads in its managed cache, applies upload and transfer limits, and sends file transfer instructions to the target devices.
Lanview Client receives the file. Once a file has been uploaded to the Server cache from Studio, Studio can be closed and the file transfer will continue to the end devices.
If a client device is not online when the file is sent, the transfer is queued for when it is next online when the file transfer is sent to a Group.
File transfers are resumable in the event of error or the server and/or client device becoming offline during transfer.
Device and group targeting
File Transfer may target a single device or a group where supported.
Group file transfers should be reviewed carefully before submission. Check the target group membership and destination path before sending the file.
Server cache relationship
File Transfer and Server File Cache are related, but they are not the same topic.
File Transfer is the action of sending a file to devices.
Server File Cache is the managed storage used to hold uploaded payloads for file transfer and related features.
Cached files are managed by Lanview Server and may be removed by retention or cleanup settings.
Transfer limits
Lanview Server can apply upload and transfer limits, including limits for active uploads, single upload size, total active upload size, disk reserve and transfer rate.
These limits protect the Server and the local network from uncontrolled file transfer activity.
Permissions
Use the current permission catalog to confirm file transfer permissions.
Depending on the action, related permissions may include device targeting, group targeting and console access when the action is invoked through the Lanview console.
Audit behaviour
Lanview audits file transfer related activity.
Audit records can include:
- file send requested
- file send result
- upload completed
- file cache cleared
- file cleanup activity
Audit records should describe the transfer safely without exposing file contents.
Sensitive files
Avoid examples that transfer:
- passwords
- private keys
- recovery codes
- licence material
- credential files
- unredacted configuration files
- files containing personal or confidential information
Real environments may transfer sensitive files for legitimate reasons, but that should be governed by internal procedures.
Common problems
Upload is rejected
The file may exceed the configured upload limit, active upload limit or available Server cache capacity.
Transfer does not complete
The target device may be offline, disconnected or unable to write to the destination.
Check the task result and target device state.
Cached file is no longer available
Cached payloads are not a permanent document store. They can be removed by retention or cleanup settings.
Console commands
File transfer and cache commands are listed in the command reference.
Guidance
Use File Transfer for controlled device delivery, not as a general file sharing system.
For repeatable software delivery, use Packages and Deployments where appropriate.