EnglishFrançaisDeutschEspañolItaliano日本語한국어NederlandsPortuguês (Brasil)中文 (简体)中文 (繁體, 台灣)
Skip to main content

2026 年 8 月 5 日

Install App Volumes Agent

To package an App Volumes application or deliver the application to a Windows endpoint, the App Volumes agent must be installed on the endpoint (packaging computer and target desktops). During installation, options are available that allow you to choose how the agent needs to be managed and how applications can be delivered to the endpoint.

You can install the App Volumes agent in a managed mode where the agent connects to App Volumes Manager or install the agent as a standalone component. When installed in the managed mode, App Volumes Manager centrally manages the application lifecycle. Additionally, you can also determine whether to deliver an application to the local cache of a Windows endpoint or place the application on shared storage from where the Windows endpoint accesses the application. In a standalone mode, device management tools manage the application lifecycle.

For improved security, ensure that the Windows endpoint running the agent does not use weak ciphers when communicating using SSL/TLS protocol. To deactivate weak ciphers in SSL and TLS, see Deactivate Weak Ciphers in SSL/TLS in the Horizon 8 Installation and Upgrade documentation at Omnissa Product Documentation.

You can also install the agent silently using the Microsoft Windows Installer (MSI). See Install App Volumes Agent Silently for more information.

Install App Volumes in a non-persistent virtual desktop environment

Non-persistent machines are those that refresh regularly, and user data and settings are not persisted on the operating system disk. These machines are managed centrally by re-imaging the operating system with updates. In the non-persistent virtual desktop environment, any application installed by the end user is removed after the user logs out of the desktop or when the virtual machine is shut down.

To use App Volumes in such an environment, you can select the Non-persistent or multi-session machines option when installing the App Volumes agent.

In a non-persistent virtual desktop environment, to make user-specific data persistent and portable, you can use a Writable Volume. For more information about Writable Volumes, see the Omnissa App Volumes 4 Administration Guide at Omnissa Product Documentation.

Important: Writable Volumes can be used only on a non-persistent virtual desktop.

Deploy in Managed mode (connects to App Volumes Manager)

Prerequisites

  • Install App Volumes Manager.

    Ensure that you have the host IP address and port number handy. This information is required at the time of installing the agent.

  • Ensure that you install the agent on a Windows endpoint which is different from the endpoint where App Volumes Manager is installed.

  • Verify that your environment meets System Requirements.

  • Verify that your account has local administrator privileges on the target computer.

  • Do not install the agent on the same machine where the App Volumes Manager is installed.

  • You can install the latest Windows Update and keep the Windows Update activated.

    Note: For a non-persistent virtual desktop, install the latest Windows Update on the target computer and subsequently deactivate the Windows Update. When you have application packages or Writable Volumes and the Windows Update is not deactivated on the target computer, the system volume or the Writable Volumes might get corrupted.

  • To install the App Volumes agent on a non-persistent virtual desktop environment, a separate base image must be used.

  • If you intend to use this Windows endpoint as a packaging computer, create a clean snapshot or take a backup of this machine. Revert to this snapshot or the backup before packaging new application packages.

  • Ensure that you are aware of the deployment mode options (Managed mode and Standalone mode) in App Volumes. For more information about these options, see Choose Your App Volumes Deployment Model.

    • During installation, options are available which allow you to choose how a package can be accessed by a Windows endpoint. For more information about understanding package access modes, see Application Delivery Modes with App Volumes Manager.

    • If you choose to install App Volumes agent in the Local Copy package access mode, ensure that you use the Omnissa Apps Essentials License.

Procedure

  1. Download the Omnissa App Volumes ISO.

    1. Go to the Customer Connect page.
    2. Click Downloads.
    3. In the Products A-Z listing, search for App Volumes and click Download Product.
    4. In the Download App Volumes page, navigate to the desired edition, and click GO TO DOWNLOADS.
    5. In the Download Product page, download the files.

  2. Mount the ISO and navigate to the Installaion folder.

  3. Run the setup.msi installer in an elevated command prompt.

    The same installer is used to install App Volumes Manager and the agent.

    Optional: To obfuscate PII data or control logging entries in the App Volumes agent log files, you can use svservice parameters. These parameters can be provided only as commandline options at the time of install. You can install the App Volumes agent using the msiexec command as follows:

    msiexec /i "path_of_App_Volumes_Agent.msi" EnablePIILogging=0 LogLevel=1

    For more information about these parameters, see Obfuscate PII Data in App Volumes.

  4. Read and accept the End User License Agreement and click Next.

  5. In the Management Mode window, select (Managed) Connects to App Volumes Manager and click Next.

  6. In the Package Access Mode window, select how application packages are accessed on this device.

    Package Access Mode OptionsProcedure
    Shared Storage

    In this mode, packages remain on central storage. The Windows endpoint always requires a network connection to access the packages.
    1. In the Server Configuration window, enter the App Volumes Manager IP address and App Volumes Manager port number.
      Note: The default port number for App Volumes Manager is 443. If you have configured App Volumes Manager to listen on an HTTP port, enter 80 for the port number.

    2. (Optional) If you do not want the agent to validate the App Volumes Manager certificate, check the Disable Certificate Validation with App Volumes Manager box.
      Certificate validation is enabled by default.

    3. If you want to use App Volumes in an environment that retains user data and settings on the operating system disk, in the Machine Type window, clear the Non-persistent or multi-session machines check box.

    4. In the Ready to Install App Volumes Agent window, click Install.
    Local Copy

    In this mode, packages are cached locally on a Windows endpoint. The endpoint can access the downloaded packages any time even when offline.
    1. In the Server Configuration window, enter the App Volumes Manager IP address and App Volumes Manager port number.
      Note: The default port number for App Volumes Manager is 443. Enter 80 for the port number if you have configured App Volumes Manager to listen on an HTTP port.

    2. (Optional) If you do not want the agent to validate the App Volumes Manager certificate, check the Disable Certificate Validation with App Volumes Manager box.
      Certificate validation is enabled by default.

    3. In the Ready to Install App Volumes Agent window, click Install.

  7. After the installation is complete, to exit the wizard, click Finish.

  8. To complete the agent installation, restart the Windows endpoint.

What to do next

  • Configure SSL certificates for the agent. You can also deactivate SSL communication and certificate validation between App Volumes Manager and agent.
    For more information, see the Omnissa App Volumes Administration Guide on Omnissa Product Documentation.

  • If you have selected the Local Copy package access mode during installation, ensure the following:

    • Configure the Omnissa Apps Essentials License key.
      For more information about the configuration, see the Configure License in App Volumes Manager section in the App Volumes Administration Guide, version 2512 and later, at Omnissa Product Documentation.

    • Turn on the Generate MSI when creating VHD package setting in App Volumes Manager.
      For more information about this setting, see App Volumes Manager Configuration Settings Page section in the Omnissa App Volumes Administration Guide.

Deploy in Standalone mode (Device Management Tools are used)

Prerequisites

Procedure

  1. Download the Omnissa App Volumes ISO.

    1. Go to the Customer Connect page.
    2. Click Downloads.
    3. In the Products A-Z listing, search for App Volumes and click Download Product.
    4. In the Download App Volumes page, navigate to the desired edition, and click GO TO DOWNLOADS.
    5. In the Download Product page, download the files.

  2. Mount the ISO and navigate to the Installaion folder.

  3. Run the setup.msi installer in an elevated command prompt.

    The same installer is used to install both App Volumes Manager and the agent.

    Optional: To obfuscate PII data or control logging entries in the App Volumes agent log files, you can use svservice parameters. These parameters can be provided only as command-line options at the time of install. You can install the App Volumes agent using the msiexec command as follows:

    msiexec /i "path_of_App_Volumes_Agent.msi" EnablePIILogging=0 LogLevel=1

    For more information about these parameters, see Obfuscate PII Data in App Volumes.

  4. Read and accept the End User License Agreement and click Next.

  5. Select Install App Volumes Agent and click Next.

  6. Select Standalone Agent Configuration.

  7. Select the desired option for the license configuration.

  8. Review the Operational Data Collection information.

    Note: Omnissa may collect operational data. This means that Omnissa may monitor and collect configuration, performance, usage, and consumption data relating to customers and their users’ use of the software to facilitate the delivery and operation of the products and services (collectively, referred to operational data) as described in the Omnissa Privacy Notice. You can deactivate the collection of operational data by contacting Omnissa support.

  9. Follow the on-screen instructions.

  10. To exit the wizard after the installation is complete, click Finish.

  11. To complete the agent installation, restart the Windows endpoint.

What to do next

  1. On a clean Windows endpoint, Install App Volumes Application Capture Command-Line Program.

  2. Capture an App Volumes application package into the .msi format using the App Volumes Application Capture Command-Line Program on the Windows endpoint.

    For more information about using the Capture Command-Line program, see Using the App Volumes Application Capture Command-Line Program chapter in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.

If you have selected trial mode at the time of install, at a later time, you can upgrade to a production license by adding a license key using the svservice command with administrator privileges as follows:

svservice.exe setlicensekey license_key

where license_key is 35 characters long in this format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Note: The production license gets updated only on the Windows endpoint where the svservice command is run. Hence, this update must be performed on every Windows endpoint which has the App Volumes agent installed.

When upgrading to later versions of App Volumes, using a production license is mandatory in the following scenarios :

  • Trial mode has expired in the source version of the upgrade.

  • Production license has expired in the source version of the upgrade and the target version of the upgrade is not an App Volumes patch release.

此页面对您有帮助吗?

对本主题提供反馈

本主题对您有帮助吗?

请勿填写任何个人信息或机密信息。

正在生成链接…