We need to deploy Symantec EV Outlook Add-in silently to our fleet of machines using SCCM 2012. The product comes with an MSI and a setup.exe. According to the doco the setup.exe is used for customer to allow UAC elevation in a locked down account (not a problem for us as SCCM would run the install elevated).

My question is around how to get Symantec EV Outlook Add-in installing from the MSI rather then the setup.exe. I've check in all the usual places in the MIS tables, Launch conditions, custom actions, property table ect and i can't see where its refering the setup.exe

If you try and launch the msi itself you get a message You cannot install the [ProductName] by launching this MSI file directly. You must launch setup.exe. For more information, contact your administrator.

I found that message inside the error table with an error code number of 25050.

I'm wondering if anybody else has had any luck getting the MSI working without the setup.exe, or alternately how to do a silent install from the setup.exe usual switches like setup.exe /s don't work and when i run the  setup.exe /? the only options it gives me are /A: Perform adminsitrative install /v verify signature.

I tried setup.exe /a but i can't see the files extract anywhereS
1 Comment   [ + ] Show comment


  • I did look for that entry also but could not find it in the properties, launch conditions or custom action tables. The setup.exe has been created using a bootstrap installer?
    • I have this working with the msi. You just need to upload the msi and set the Run Parmaters: /qn EULA_ACCEPT=YES /i

All Answers

This is not uncommon when dealing with installs that have been created with Installshield. Although I don't know for sure whether your Add-In is packaged with Installshield, chances are that setting the property ISSETUPDRIVEN=1 will remove the dependency on the setup.exe.
Some older installshield MSIs also installed a version of isscript.msi before installing the main MSI. The version needed would normally be extracted into the TEMP folder during the initial execution of setup.exe.  If this is the case in your install, you would install isscript.msi silently before the main MSI.  Note that there are many versions of isscript.msi and you will need the exact version your app was built with.  The property table of the MSI will normally give an indication of the version range required.
Answered 07/24/2014 by: EdT
Red Belt

  • I did look for that entry also but could not find it in the properties, launch conditions or custom action tables. The setup.exe has been created using a bootstrap installer? - See more at: http://www.itninja.com/question/symantec-ev-outlook-add-in-10-0-4-silent-install#sthash.3DugnWde.dpuf
    • The link above just brings me back to this thread. However, having a look in the app database where I am working at the moment, shows that the source for Symantec EV9 add in for Outlook is an MSI. If you can't get any further with the information posted by Dunnpy then I would suggest you revert to Symantec and ask for their further assistance.
      • That link in the OP's reply is an auto link that's generated by the copy/paste of something from this site.
It doesn't sound like a traditional Installshield setup that bootstraps the MSI.

Normally running with /? will give you other options, including /v to pass parameters to the MSI. As /v is giving you a signature verification option it's safe to assume that ISSETUPDRIVEN=1 isn't going to help.

If you can't find anything on Symantec fora or documentation about silent installation of the product - you'll have to do some further investigation.

Enable MSI logging in the registry (use the manual steps and full voicewarmup)  - http://support.microsoft.com/kb/223300 - the instructions are for XP, but the setting is the same in later versions of Windows.

Run setup and install the software.
Open your temp directory and you'll see at least one new file that starts wtih 'MSI' and has a .log extension.
This is the MSI installation log, you need to be examining it for property changes, hopefully named something meaningful that is telling the MSI that it was run from the setup.exe.

It's likely there'll be a 'commandline' entry that will show all parameters that were passed to the MSI when it was launched, and one of those will be required to run the MSI on its own, and one or more of them may be required in your MST for installation.

Hope that helps,

Answered 07/24/2014 by: dunnpy
Red Belt