Using the Omnissa App Volumes Package Editor Tool

Package Editor is a standalone, Windows desktop tool. This tool allows you to inspect, edit, and add package content and create a new package disk without recapturing the application or modifying the original package.

Additionally, you can also use an option in the tool to generate a new package identifier for the edited package and use both packages in App Volumes Manager. When the edited package is imported to App Volumes Manager, this package replaces the original package. If the package has a new identifier then the imported package can be used in addition to the existing package.

While the existing package report functionality allows you to view the package content, the Package Editor tool gives you the ability to change the package content and create a package disk. You can import the new package to App Volumes Manager, replace the original with the newly edited package, and deliver this package to end users.
For information about the package report, see the About the App Volumes Application Package Report section in Package an App Volumes Application.

How to install the Package Editor tool

The Package Editor tool is installed using App Volumes Tools. The prerequisites and procedure to install Package Editor is similar to installing the App Volumes Application Capture Command-Line Program. For more information about installation, see the Install App Volumes Application Capture Command-Line Program section in the Omnissa App Volumes Install Guide at Omnissa Product Documentation.

Package Editor tool gets installed at C:\Program Files\Omnissa\AppVolumes\Agent\PackageEditor.

When to use the Package Editor tool

Here are some of the use cases that can help you decide when to use the tool:

• Correct package metadata such as name, description, author, version, and so on

• Add new shortcuts or import existing shortcuts for the package

• Remove a stale license file or fix a registry value

• Add a missing file or script in the package

• Scan the package for common vulnerabilities and exposures

• Export and share the package summary (in HTML format) with someone who has no access to the tool or App Volumes Manager

Workflows for using the Package Editor tool

When you edit the contents of a package that is already captured, the workflow you follow depends on whether the specific package version is delivered to production users. Editing a package that is already in production requires additional steps to ensure that the users continue to receive the specific package version. Choose the workflow that fits your situation. For more information about the workflows and certain best practices, see Package Editor Workflows.