Feature Overview: Software Packages and Deployments
Lanview packages and deployments provide a managed way to prepare software package content and deploy install or uninstall actions to managed Windows devices.
This feature area covers package authoring, validation, repository management, deployment targeting, package status and troubleshooting.
What this feature area includes
Software package management includes:
- Package import and validation.
- Server package repository management.
- Package version states such as approve, block and retire.
- Device and group install deployments.
- Device and group uninstall deployments.
- Deployment history and status.
- Deployment and status overrides with reasons where supported.
- Package cleanup and package version cleanup.
- Package policy and automatic enforcement settings.
Package lifecycle
A typical package process is:
- Prepare or import a package.
- Validate the package.
- Publish or make it available in the Server repository.
- Deploy it to selected devices or groups.
- Review deployment status and task results.
- Troubleshoot failures or update recorded status where appropriate.
Validation is useful, but it does not guarantee every endpoint will install successfully. Endpoint state, prerequisites, installer behaviour and permissions can still affect the result.
Where to find it
Package features are available from:
- Studio > Packages/Deployments.
- Device Window > Packages.
- Studio > Tasks for deployment task status.
- Studio Console for package commands where permitted.
Permissions and access
Package permissions cover several separate responsibilities:
| Permission area | Controls |
|---|---|
| Repository viewing | View package repository and versions. |
| Authoring and publishing | Create, import, validate and publish packages. |
| Version management | Approve, block or retire package versions. |
| Deployment creation | Create install or uninstall deployments. |
| Deployment management | View, cancel, retry or reset deployment/failure state. |
| Policy | Manage package policy and automatic enforcement settings. |
Separate permissions allow package install and uninstall targeting at devices or groups.
Policy and settings
Package policy settings are Server-level. Deployment targeting can be device-based or group-based.
Desired-state package policy and one-off deployments should be understood as related but separate concepts.
Audit behaviour
Package add, validate, delete, cleanup, deploy, uninstall, status override, deployment override and policy actions are audited where catalogued. Reason prompts may apply to sensitive package changes.
Package command lines, logs and installer output can contain sensitive information. Do not include licence keys, credentials, private URLs or internal file shares in package definitions or examples.