Package Authoring

Lanview packages prepare software and the instructions needed to install or remove it from managed Windows devices.

Package authoring should be completed and tested before a package is used in a wider deployment or Package Policy.

Before creating a package

Collect the following information before opening the package editor:

• product name
• version
• publisher
• installer files and any supporting files
• silent install command
• silent uninstall command, where supported
• expected success exit codes
• restart requirements
• prerequisites
• supported Windows versions and architectures
• a reliable way to confirm whether the software is installed

Test the install and uninstall commands manually on a representative test device before adding them to Lanview.

Do not include credentials, product keys or private access tokens in installer arguments.

Creating a package in Studio

To create a package:

1. Open the Packages/Deployments module in Lanview Studio.
2. Open the package repository.
3. Choose the option to create or import a package.
4. Enter the product and version information.
5. Add the installer and any supporting payload files.
6. Enter the install command and, where required, the uninstall command.
7. Configure the package's detection, success and restart behaviour using the fields available in the current Studio version.
8. Add a clear description and any administrator notes.
9. Save the package.
10. Run package validation.

Use paths relative to the package payload where the package format supports them. Avoid assumptions about drive letters, current folders or interactive user input.

Validation

Validation checks that the package structure and required metadata are acceptable to Lanview.

Resolve validation errors before publishing the package.

Validation does not run the installer and does not guarantee successful deployment. The target device can still fail because of prerequisites, operating system state, permissions, command syntax or installer behaviour.

Publishing and version state

After validation, publish the package so it is available for permitted deployments.

Where version state is available, review whether the version should be:

• Approved for normal deployment
• Blocked to prevent new deployment
• Retired because it is no longer intended for use

Do not approve a version for wider use until it has been tested on a small, controlled set of devices.

Test deployment

Before wider deployment:

1. Select one or more representative test devices.
2. Create an install deployment.
3. Review the task result and installer output.
4. Confirm the application is installed and usable.
5. Test uninstall where the package supports it.
6. Confirm any restart behaviour.
7. Check the recorded package status.
8. Correct the package and repeat the test if necessary.

A successful task result should be checked against the actual device state before the package is used more widely.

Updating a package

Create a new package version rather than silently replacing an existing tested version where versioning is supported.

Record what changed, including installer files, command lines, detection behaviour and restart requirements.

Retain the previous version until the new version has been tested and the rollback position is understood.

Permissions

Common package authoring permissions include:

Useful commands

package.validate "<path-to-package-zip>"
package.add "<path-to-package-zip>"
package.list
package.show <product>
package.delete <product> /version <version>
package.cleanup
package.cleanup.versions

Common authoring problems

The installer waits for user input

Use the vendor's supported silent installation options. Test the exact command outside Lanview first.

The installer works manually but fails through Lanview

Check execution context, working directory, relative paths, prerequisites and whether the installer depends on an interactive desktop.

The package validates but deployment fails

Validation checks the package format. Review the deployment task result and installer exit code.

Uninstall does not work

Confirm that the uninstall command matches the installed version and can run silently in the same execution context.

Related topics

• Packages and Deployments
• File Upload and Transfer Limits
• Script Repository