Packages and Deployments

Lanview packages are used to stage software and deploy or remove it across managed Windows devices.

The package repository holds package information and uploaded package content. Deployments define which devices should have packages installed or removed and allow administrators to review progress and results.

Package repository

Administrators use Lanview Studio to add, edit, view and manage packages.

A package normally contains the files and metadata needed for Lanview Client to perform an install or uninstall action on a target device.

Deployments

A deployment sends package work to one or more devices.

Deployments may target individual devices or groups, depending on the action and permissions.

Package deployment should be treated as a controlled administrative action. It can install software, remove software or change device state across many computers.

Validation

Package validation checks whether a package appears to meet Lanview's expected package format and metadata requirements.

Validation does not guarantee that installation will succeed on every device.

A package can validate successfully and still fail during deployment because of device state, installer behaviour, missing prerequisites, Windows permissions, reboot requirements or application-specific errors.

Package Policy

Package Policy defines the package state Lanview should maintain for a device or group.

For example, a policy may require a package to be installed, require it to be absent, or leave the package unmanaged. Lanview compares the recorded package state with the applicable policy and reports where action or review is required.

Package Policy is separate from a one-off deployment:

• Use a deployment when you want to install or remove a package as a specific administrative action.
• Use Package Policy when Lanview should continue checking that the selected package state is maintained.

Review policy targeting carefully before applying it to a large group. A policy can continue to affect devices after the initial action has completed.

Where to manage packages

Packages, deployments and Package Policy are managed from the Packages/Deployments module in Lanview Studio.

A selected device may also show package information from the Packages page in the Device Window.

Permissions

Package and deployment actions use separate permissions.

Group targeting may require additional group permissions.

Audit behaviour

Lanview audits package management and deployment actions.

Audit records can include package add, validation, deletion, cleanup, deployment, uninstall, deployment override and status override events.

Reason prompts may apply depending on the Server configuration and the action being performed.

Package names, deployment targets and result summaries may appear in audit records. Keep product keys, credentials and private URLs out of examples and package command lines.

Console commands

Related console commands include:

package.add
package.validate
package.list
package.show
package.deploy
package.uninstall
package.deployment.list
package.deployment.show
package.deployment.override
package.status.list
package.status.show
package.status.override
package.delete
package.cleanup

Common problems

A deployment affects more devices than expected

Review the target carefully before submitting group deployments. Group membership controls which devices are included.

A package validates but does not install

Validation checks the package structure. Installation still depends on the target device, installer requirements, command line, permissions and any required restart.

Policy status does not match the device

Refresh or review the package status before changing policy or using a status override. A status override changes Lanview's recorded state; it does not install or remove software.

Guidance

Use clear package names and version information, and record enough detail for another administrator to understand what the package does.

Test new or changed packages on a small set of devices before wider deployment. Review install and uninstall behaviour, restart requirements and task results before applying Package Policy to a large group.