How to Use the Omnissa App Volumes Package Editor Tool

In addition to using the Package Editor tool for editing the package contents and creating a new package disk, you can also use the tool to inspect the package contents, scan the package for vulnerabilities and generate a report, and export the package summary in HTML format.

Important: Before you perform any of these tasks, ensure that you have a good understanding of the tool. For more information, see Use the Package Editor.

Inspect the contents of an App Volumes package

You can use the Package Editor tool to inspect the package details such as name, description, version, application icon, Volume ID, App ID, and so on. You can also view the capture information about the environment in which the package is captured. Additionally, you can also see the file system and registry hive of the captured package and scan the package for vulnerabilities.

When you open the package, the capture information displayed belongs to the original package. Later, you can edit some of the package properties and package contents.

Procedure

1. Start the Package Editor tool.

2. Click Open Application Package.

3. Browse and select the .vhd package that you want to inspect.
   The selected package opens in the tool.

4. Review the package content in the following sections:

   Section	Description
   Overview	Package details such as name, description, version, application icon, app product ID, capture environment, fonts, environment variables, Windows Services, on-Demand properties such as shortcuts and File Type Associations. This section also provides an Audit Trail, which is a change log for each package edit after a package is finalized.
   Filesystem	The virtual file system contained in the package.
   Registry	The registry hive captured in the package.
   Vulnerability Scan	Known vulnerabilities affecting the binaries in the package. See Scan a package for vulnerabilities.

Edit the contents of an App Volumes package

You can edit or add some package contents and properties, but not all of them. In the tool, you can locate Edit and Add buttons in some sections. To discard the changes and keep the original information, you can use the Revert functionality wherever applicable. Additionally, you can delete some package properties by using the Delete button.

Prerequisites

Ensure that you have disk space for the new VHD and additional package edits.

Procedure

1. Start the Package Editor tool.

2. Click Open Application Package.

3. Browse and select the .vhd package that you want to edit.
   The selected package opens in the tool.

4. Before changing any of the package contents, you can select a few advanced options such as display hidden files, short file names, preview, and so on that can be applied to multiple sections.

   1. At the top of the toolbar, click Options, and select or clear the required option check boxes.

5. To change some of the package details, add fonts, environment variables, and shortcuts, and so on, navigate to Overview > Package summary tab.

   Note: One of the package properties that can be edited in the Package Details section is the App Product ID. If your package already has an App Product ID then clicking on Generate will overwrite the existing value of this package property. When the edited package is imported into App Volumes Manager, this package gets associated with a new application inventory item instead of the existing application.

   For more information about the behavior of imported application packages, see Import an Application to App Volumes.

6. To make changes to the file system, such as adding a file or folder, deleting an unwanted file, or setting the Short File Name (SFN), navigate to the Filesystem tab.

   1. Search for the required file or folder, right-click on the object, and perform the required action.

7. To make changes to the registry hive of the captured package, navigate to the Registry tab.

   1. Search for a key or value name, right-click on the object, and perform the required action.

Scan an App Volumes package for vulnerabilities

To detect common vulnerabilities and exposures (CVE) in the selected package, you can scan the binaries and library files in the package against CVE providers such as NVD, OSV, and OSS Index. After the scan runs, the tool generates a report that you can export in HTML and CSV formats.

Procedure

1. Start the Package Editor tool.

2. Click Open Application Package.

3. Browse and select the .vhd package that you want to inspect.
   The selected package opens in the tool.

4. Navigate to the Vulnerability Scan section.

5. Optional: To configure a CVE provider, click Configure CVE Providers.

   1. Click the Provider drop-down and select a provider.

   2. Configure the remaining details such as the NVD API key, minimum CVSS score, and so on.
      Some of these fields are optional.

   3. Click Save.

6. Click Scan Now.
   When the scan completes, the tool lists the vulnerabilities and exposures in the package.
   Note: The vulnerability scan covers only the binaries and library files from the original package. The scan does not include the files and folders that you add or remove while editing the package.

7. Review the list of vulnerabilities and exposures using the related information such as CVE ID, Severity, EPSS score, and so on.

8. Optional: To export the vulnerability report in HTML, CSV, or both formats, click Export Report.

   In the Export vulnerability report window, click Export and save the exported files in the required destination.

Export a read-only App Volumes package summary

You can export a read-only HTML summary of the package so that a reviewer can examine the package contents without installing the Package Editor tool. The exported file is a static inventory, which does not include the vulnerability scan results or the staged edits that have not been written to a package disk.

Procedure

1. Start the Package Editor tool.

2. Click Open Application Package.

3. Browse and select the .vhd package.
   The selected package opens in the tool.

4. Click Options > Export package snapshot (HTML).

5. In the Save Package Snapshot window, select the destination where you want to save the HTML file and provide a file name.

6. Click Save.

   The package summary is saved in HTML format.

Create a new App Volumes package disk

After editing the package contents, you must finalize the changes and create a package that contains these changes. Until you finalize, all changes remain staged. The tool does not modify the original package.

Prerequisites

Ensure that you have disk space for the new VHD and additional package edits.

Procedure

1. Start the Package Editor tool.

2. Click Open Application Package.

3. Browse and select the .vhd package that you want to finalize.
   The selected package opens in the tool.

4. Click Finalize.

5. In the Create new package disk page, review the list of staged changes in the Staged changes table.

6. Optional: To revert any change, use the Revert button.

7. In the Destination section, browse and specify a destination path for the new package disk (.vhd).

8. Enter a file name for the new package disk.

9. Create a new package disk

   Option	Procedure
   You want to replace the original package with the edited package	Select the I have reviewed the staged changes... checkbox. Clear (do not select) the Generate new... checkbox. Click Create New Package Disk. A new package disk with the same package identifier (App ID in the JSON file) as the original package is created. When imported to App Volumes Manager, this package replaces the original package.
   You want to use the edited package as a new package in addition to the original package for the same application	Select the I have reviewed the staged changes... checkbox. Select the Generate new... checkbox. Click Create New Package Disk. A new package disk is created and a new package identifier (App ID) is generated for this package. When imported to App Volumes Manager, this package gets associated with the application in addition to the original package.

Results

The tool generates the new .vhd and the corresponding .json files at the specified path. You can navigate to the Overview > Package summary > Audit Trail section and review the change log. This change log records every change saved into the package. All changes are grouped per session. To view the changes per session in the Audit Trail section, click the drop-down, and select the required sessions. All changes corresponding to the selected sessions are displayed.

Package Editor logs are present at C:\Program Files\Omnissa\AppVolumes\Agent\PackageEditor\Logs.

What to do next

After you create a new package disk, import the edited package into App Volumes Manager. Perform the next steps based on the chosen workflow. For more information, see Package Editor Workflows.