Faronics Deploy fails to install a custom application even after verification.

Problem

Customers see a custom application that installs correctly during the installation process fail to install properly on subsequent machines. 

Issue

Some 3rd party applications append a token ID or unique identifier to the name of the application during the installation process of their software. Faronics Deploy uses an exact match for the name of the product as shown in the Control Panel's Add/Remove Programs list to determine if a given product is installed. The addition of a unique identifier for each install of the product results in the initial install attempt to be successful when the application is set up, but causes subsequent installs to fail on other devices. 

This behavior can be confirmed by looking at the name for the product in the list of installed applications in the control panel, if you see what appears to be a random value added to the end of the product name that is different on two machines this indicates that your product exhibits this behavior. 

Workaround

At this time Faronics suggests using the custom script functionality to download and install an application that appends a unique identifier to the application name. The Custom Script functionality does not rely on a exact match of the products name to determine a successful install and instead relies on the return values that the script provides to the operating system to determine success. 

Known Impacted Products

At this time Faronics is aware of the following products that exhibit this behavior;
  • Beyond Trust Remove Support Jump Client 
  • Elpha Secure Client