Secunia CSI7
Create Profile
Our Commitment
Open Discussions
My Threads
Create Thread

Forum Thread: Guide on how to create .msi file?

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:

This thread has been marked as locked.
thoang Guide on how to create .msi file?
Member 28th Jan, 2014 23:52
Ranking: 0
Posts: 3
User Since: 27th Jan, 2014
System Score: N/A
Location: US
Hello everyone,
please help me create a custom package or update package with msi file. I'm not sure how to use the parameter and all I get is just the popup of Windows Installer msiexec.exe.
I would appreciate if someone can walk me through step by step.

This user no longer exists RE: Guide on how to create .msi file?
Secunia Official 29th Jan, 2014 10:31

The below thread was opened few days ago by one of our community users where we were asked how to create a custom package for Microsoft MSXML software.

Please consider that the steps pointed within this case would be identical for any other package that has Product entry listed inside the Secunia Package System menu (where you could right-click on that product and select create Update package).

If you wish to create a completely new deployment in scenario where your product is not listed within the Secunia Package System interface, then you have to perform some more actions to configure your package. Below is one simple way of doing that configuration:

1. Copy with Ctrl+C the everything under line 3 'var silentParams' (including) of an existing JScript template from any product that appeared in Blue color in the SPS interface (right-click > Create Update Package)(these packages include a fully configured generalized SPS Jscript template).

2. After copying the Jscript go back to the main SPS Interface and click on the top button 'New Custom Package', then navigate to step 2 of the wizard. Paste the script you copied at point #1 above into the current JScript window (make sure you paste from under line 2 to match the same script configuration as you would have in a pre-configured package).

3. Use the Add Local File button to include your installer

4. Add your silent parameters in between the quotes of line #3 'var silentParams'

You are now ready to publish your package. Please note that this package must mandatory be labeled as 'AlwaysInstallable' and that package would deploy to the entire amount of machines you approved it to. F.e. Approving this package to 'All Computers' group would result in installing this Custom Package to each and every machine in the domain.

I hope you'll find my information helpful.

Please note that all steps must be followed correctly and that it's a must to test each Custom Package you configured before deploying that domain wide. Secunia CSC does not provide official support for Custom Packages and it preserves the right to decline support should that not be feasible for our support team. You should consider my information here as provided on 'good will' and as it's my sole experience with the software. Use it on your own risk.

Kind regards / Stay Secure
Rosen Danailov / Security+
Secunia Customer Support
thoang RE: Guide on how to create .msi file?
Member 30th Jan, 2014 20:04
Score: 0
Posts: 3
User Since: 27th Jan 2014
System Score: N/A
Location: US
would you mind giving me an example script? Say a whole script of a working software like 7-zip or Google Chrome that has .msi file?
Was this reply relevant?
This user no longer exists RE: Guide on how to create .msi file?
Secunia Official 24th Feb, 2014 09:13

Any script which is found inside a blue product entry inside the Secunia Package System is an active working script.

The scripts provided in CSI are not meant to serve a single product, like 7-Zip for example, these are generic scripts that work for each package as long as you copy/paste them into a new package configuration. Whether your package is .MSI or .EXE it doesn't matter, the script includes mechanisms to handle the installation correctly for each given format.

After you copied/pasted the script as mentioned above, you have to add your installer and then add the correct silent parameter to the script, and so your package is ready to deploy.

Please make sure you followed the steps exactly as I pointed them for you above to achieve the simplest configuration of a new custom package without complicating your task too much.

Kind regards / Stay Secure
Rosen Danailov / Security+
Solution Specialist
wwfit RE: Guide on how to create .msi file?
Member 25th Feb, 2014 10:08
Last edited on 25th Feb, 2014 10:08 Hi,

this works fine with msi and exe, as I tried often.

But now I have to deploy a *.MSU file (Microsoft Standalone update Package).

I tried to redesign the script, because instead of msiexec this has to use wusa.exe in front of the installing file.

Could you provide me and the rest of the community a sample how to solve this?

Best regards
Was this reply relevant?
This user no longer exists RE: Guide on how to create .msi file?
Secunia Official 2nd May, 2014 11:54

Unfortunately, Secunia had not yet implemented support for installation of .MSU packages in the scripts we provide in the Secunia Package System and we do not have an official workaround we can propose to you at the current moment.

Customers that wish to deploy .MSU packages would have to implement the script in SPS on their own by adding a function in the script that would be able to handle and execute .MSU installers added to their packages.

Kind regards / Stay Secure
Rosen Danailov / Security+
Secunia Customer Support

This thread has been marked as locked.

 Products Solutions Customers Partner Resources Company
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
Technology Partners
 About us

© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer