Vmware horizon client msi how to#

S uppress all reboot attempts by the installer - if a reboot is required it can be instigated by the user, or the deployment toolset. You might also want to add the following to the Property table: If there are other public properties (those in CAPITALS) you which to define from the information on the link above then set them in the Property table - if they are not present already, add then as a new row with the desired value. Setting these Level values in your MST you can define which Features are installed in your package. If it is equal to the INSTALLLEVEL value then it will install. Now check the Feature table and work out which features, using the ADDLOCAL names you have.Ĭheck the 'Level' value for each Feature row - if that value is less than the INSTALLLEVEL value you noted in the Property table (or less than 1, if it isn't defined) then the feature WON'T install. If there isn't one, there is a default value of 1 for the property, even though it isn't defined. If you want to go down the MSI/MST route then you can create a transform to contain these settings.Įach one of the ADDLOCAL items refers to a Feature inside the MSI, you can chose which Features are installed by changing the Level value in the Feature Table.įirst check the Property table - is there an INSTALLLEVEL property? What is its value? You could use the ADDLOCAL options on the command line with your MSI file, along with the other properties you want to configure - which is the easiest option if you don't really have much knowledge of modifying MSI installers.

Vmware horizon client msi how to#

My first reply would give someone with a working knowledge of MSI packaging how to proceed - it's sometimes difficult to know what level to pitch an answer - so sorry about that! The information is there from the vendor, it's a matter of knowing how to apply it :) I dont want to EXE-Install the View Agents. choose what to install/enable and what to not install/disable during installiation: Has anyone already figured out where the important settings are located an how they are called ?

In this case VMware seems to leave their customers with the struggle to figure out important parameters in Orca them selves. I remember Adobe provides a special MST Editor (Customization Wizard) so that its easier for us folks to navigate through the settings and set preferred configuration. I created an AIP (Administrative Installation Point) from the EXE via '/a' and can deploy the View Agent (6.0.2) via MSI but I would like to configure the Installation components like: (USB Passthrough, SingleSignOn, etc) via an MST file.