Bulk Deployment - Lens Desktop
Poly Lens Desktop provides administrators with flexibility over their deployments across their fleet of managed assets. Using industry standard tooling, administrators can customize their installation and automate the deployment to their end users.
In addition to automating the deployment of the application, IT admins can create unique client tokens within a Poly Lens cloud Account that when deployed together with Lens Desktop to personal devices, Poly Lens will automatically associate all users to the Poly Lens cloud Account associated with the token without needing the personal device user to login. This method identifies current logged in user, allowing immediate management of all supported USB and Bluetooth peripherals.
Poly Lens Desktop – Windows Environments
Customers who wish to pre-stage the installation of Poly Lens Desktop on managed endpoints can use third-party tools like Microsoft Endpoint Configuration Manager (MECM), previously known as System Center Configuration Manager (SCCM). Poly Lens Desktop is distributed as a common .MSI installer file type to support various third-party deployment tool frameworks.
While HP provides support for customers using Poly Lens Desktop, HP does not directly support these third-party tools. The information below is meant to provide guidance of an example deployment and as reference only.
MSIEXEC Command Line Options
Package Options
Poly Lens Desktop supports the following package specific options (Public Properties) to customize the installation behavior.
| Parameter | Supported Value/Behavior |
|---|---|
| TENANTTOKEN | <client token> - The client token that is used to associate the Poly Lens Desktop application with a Poly Lens cloud Account. This token is generated in the Poly Lens cloud Account and is unique to each Account. Note: This property is required for Loginless deployments. |
| ACCEPTEULA | 0 - The EULA will be accepted on behalf of the end user by the administrator. 1 (Default behavior) - The end user must accept the EULA before Poly Lens Desktop will launch. Note: Regardless of selection, the Poly Lens EULA link is available on the bottom of the client Settings page. The EULA can be found at: Poly Lens EULA. |
| NODATA | 0 (Default behavior) - Poly Lens Desktop connects with Poly Lens cloud and operates under normal behavior. Full functionality is provided in app to the user and in the cloud for the IT administrator. 1 - The app instance does not communicate with the cloud any telemetry data and only connects to download latest generally available releases of connected devices and application updates. IT administrators will have no visibility to the app instance nor of the peripherals connected to the machine. Utilization and telemetry is not provided to the cloud and the application is not connected to a cloud account for Lens policy adherence. |
| NOUSERINFO | 0 (Default behavior) - Poly Lens Desktop connects with Poly Lens cloud and operates under normal behavior. Full functionality is provided in app to the user and the cloud for the IT administrator. 1 - Information regarding the machine and connected peripherals is provided to the Poly Lens cloud, however, no user information is provided. Telemetry regarding devices connected and call state activity is provided without any and user context information. Installation will be connected to a Poly Lens cloud Account if used in conjunction with a tenant token. |
Note: All other Public Properties for the MSI package are considered unsupported and subject to change. Usage of these properties may lead to a non-functional deployment.
Installation Options
HP supports the following MSI switches controlling the behavior of the Poly Lens Desktop Installer.
| Switch Parameter | Behavior |
|---|---|
| /i | Specifies a Normal installation. |
| /x | This parameter is used to uninstall an application that was distributed as an MSI. Note: There are 2 ways to use this parameter and only 1 of them is supported in the 2.x versions of Lens Desktop. /x <path_to_package> With this option the path_to_package refers to the MSI file itself that was used during install. This was supported in 1.x Lens Desktop but does not work in 2.x Lens Desktop. This is because the Lens Desktop 2.x MSI installer is actually a wrapper of 2 other installers of the Lens Desktop and Lens Control Service installers. If you try to use this option with .MSI file, you will receive a message such as: “Windows Installer - This action is only valid for products that are currently installed.” /x <package code> This version works for both 1.x and 2.x versions of Lens Desktop. However, with 2.x version you will need to work out what are the 2 package codes for the Lens Desktop and Lens Control Service packages installed on user’s PC. The package codes vary from one release to the next of Lens Desktop 2.x, however the upgrade code is consistent. For this reason, the recommended workaround for using msiexec /x package code> with Lens Desktop 2.x, is to use the 2 upgrade codes to query the user’s PC, to discover the 2 package codes, then invoke msiexec /x <package code> twice to uninstall the 2 packages. There are a couple of ways to look up package code from upgrade code and an example powershell script can be shared if required. The upgrade codes for our 2 products are: Lens Desktop upgrade code: 8CADC38F-F0FB-43AF-9AB1-187665C977AE Lens Control Service upgrade code: F2DF66E0-0805-11EB-ADC1-0242AC120002 |
Display Options
Additionally, Poly supports the following MSI switches controlling what a user sees during the Installation Process.
| Switch Parameter | Behavior |
|---|---|
| /quiet | Installation (orUninstallation) occurs without any User Interaction. |
| /passive | Specifies Unattended Mode, showing only a progress bar during installation. The user is unable to cancel the installation process. |
| qn | Specifies no UI during the installation process. This is the same as specifying (/quiet). |
| qn+ | Installation will occur without any user interaction showing only a confirmation dialogue of success. |
Restart Options
Poly supports the following MSI switches controlling the restart behavior of the Windows PC. This is sometimes necessary with certain deployments; however, a restart is generally not required for Poly.
Poly Lens Desktop Installations
| Switch Parameter | Behavior |
|---|---|
| /norestart | Does not allow or prompt the device to restart once Poly Lens Desktop is installed. |
| /promptrestart | If a restart was necessary, the user will be prompted once Poly Lens Desktop Installation is completed. |
| /forcerestart | The device will restart once Poly Lens Desktop is installed. |
Additional Parameter Supports
msiexec supports additional parameters (such as logging) which are compatible with the Poly Lens Desktop. For additional details on these options please refer to the official Microsoft documentation available at msiexec|Microsoft Docs.
Windows Registry Keys
Deployment of the MSI with the TENANTTOKEN option will create the following registry keys within Microsoft Windows deployments.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Poly\Poly Lens Desktop\Tenant Token