Skip to main content

Search

Pinnacle Series Technical Configuration

Articles about technical configuration of the Pinnacle Series platform

EP background

Installing Pinnacle Series User Tools in a Virtual Environment

Applies To:

Technical Admins.

 

Common Causes/Issues:

  • Your organization has enabled a complete and personalized desktop experience for users with a fully secured and compliant centralized source.
  • You would like to learn how the Pinnacle Series user tools' MSI file can be used in a virtual desktop environment.

Solution Overview:

  • MSI files can be used with Microsoft Endpoint Configuration Manager, Group Policy, or third-party distribution software, to deploy Pinnacle Series to your organization.

  • Windows Installer, commonly known as MSI from the file extension of its packages, is a Microsoft technology introduced with Office 2000 intended to create more coherency in the area of application deployment and management on Windows.

  • MSI files on a physical system:

    • When Pinnacle Series installs MSI files on a physical system, the default MSI installation directory is here:

            mceclip0.png

  • MSI package for individual users:

    • When Pinnacle Series installs the MSI package for individual users in a virtual environment, the default MSI installation directory is %AppData%\<inventory_name> (Pinnacle Series User Tools).

  • You can override the default installation directory by using an INSTALLDIR property in the msiexec command. This will require you to edit the Pinnacle MSI file so we strongly recommend that you reach out to our technical support team to verify the file before deploying.

    • From the command line, type the msiexec /i <database>.msi
      INSTALLDIR=C:\<my_directory>\<my_package> command.

  • What is a VDI or Virtual Desktop Infrastructure? 

 

Tactical Rundown:

Install or update the Pinnacle Series user tools on VDI.

  • You can deploy the Pinnacle Series user tools for VDI using a per-machine installation or per-user installation using the MSI package. Deciding on which approach to use depends on whether you use a persistent or non-persistent setup and the associated functionality needs of your organization.

  • For a dedicated persistent setup, both per-machine and per-user installation will work. However, for a non-persistent setup, Pinnacle Series user tools require a per-machine installation in order to work efficiently.

  • With per-machine installation, automatic updates are disabled. This means that to update the Pinnacle Series user tools, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates are enabled.

  • For most VDI deployments, we recommend you deploy Pinnacle Series user tools using per-machine installation.

Install the MSI to the VDI VM by running one of the following commands:

  • Per-user installation (default).

    msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSERS=1


    This process is the default installation, which installs Pinnacle Series User Tools to the %AppData% user folder.

  • Per-machine installation.

reg add "HKLM\SOFTWARE\Eagle Point Pinnacle Series\Pinnacle Series User Tools" /v IsWVDEnvironment /t REG_DWORD /d 1 /f
    • This process adds a required registry key to the machine that lets the Pinnacle Series installer know it is a VDI instance. Without it, the installer will error out, stating: "Installation has failed. Cannot install for all users when a VDI environment is not detected".

msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1
  • This process installs Teams to the %ProgramFiles(x86)% folder on a 64-bit operating system and to the %ProgramFiles% folder on a 32-bit operating system.

 

Related Article(s):

Deploying Pinnacle Series User Tools

 

Still Need Help? 

Log a support ticket