2 Replies Latest reply on Jan 10, 2011 11:02 AM by DanDinolfo

    Self Extracting Zip then run installer - HowTo


      I am currently deploying Office 2010 via UNC admin share and settting the deployment method to "run at source"

      This works perfect, but I have some apps that need to be copied to the target machine and installed locally on the workstation.

      I read some other posts that suggest for multiple files to create a SFX and deploy.

      Just wondering what steps others are using to deploy via this method.

        • 1. Re: Self Extracting Zip then run installer - HowTo
          phoffmann SupportEmployee

          Very simple. You use a batch-file as your main package, in fact.


          The quick and dirty is this:


          1 - The batch is the main file.

          2 - The Office-zip is an additional file.


          3 - The batch's purpose is to run the command-line to extract the compressed files, and then run the install / command-line switches.


          The details here will vary based on what tool you use.


          4 - that's it, pretty much .




          I would recommend that you maybe look up "Understanding Batch File Distribution" for more information on using batch files, and grab some of the later BKM's on installing office, perhaps, to give you a clearer idea.


          I hope this is clearer now? It's really not as complicated as it may seem at first - the devil is in the detail though of getting it right .


          - Paul Hoffmann

          LANDesk EMEA Technical Lead

          • 2. Re: Self Extracting Zip then run installer - HowTo

            I create my self extracting files using 7 zip.  I find it very convenient.  I've attached all of the files needed in a zip file.  Just save the contents somewhere on your hard disk and then follow my instructions below.  You can get to the creators website at "http://7zsfx.solta.ru/en/"  I tweaked my setup to prompt for elevation on execute.  I'd have to fumble around to figure out how to do that again if anyone is interested.


            1. Place the files you would like to be part of your install inside the "Bin" folder.
            2. Modify the config.txt file to point to the file you want to run after extraction.  For example, if you wanted the SFX to run "install.bat" upon execution, change the config.txt file to say RunProgram="install.bat"
            3. If you want to run a vbscript as part of the install, change it to say RunProgram="wscript.exe install.vbs"
            4. Next, click on "Create.cmd".  This will create the base program.
            5. After the DOS box closes, you should see, "Program_name.exe" appear.  Rename this to an appropriate name.
            6. You're done!  When you run this file, it will extract the contents to a temporary folder, run the executable, and then delete the temporary folder when completed.


            The command line that you run cannot include spaces in names since you are unable to use quotation marks in this field.  A work around would be to point to "install.bat" and then have your complex commands inside that.  You can escape your quotes with a back slash '\'  Example:  \"%programfiles%\\Firefox\"
            One of the nice parts about using this system is that it really is very simple.  Once you have the hang of it, you can make/change installs very quickly and efficiently.  Especially since once your initial settings are tweaked for an install, you can make revisions by just clicking "create.cmd" and then renaming the "Program_name.exe" to the appropriate name.




            Configurable Settings
                (edit the file names below in notepad to change settings)


                    2 = Silent extraction.
                    1 = Progress bar during extraction, but can't cancel extraction/install.
                    0 = Progress bar during extraction with cancel button during extraction/install.
            Enter the command you want to run as part of the SFX.
            You can use a special command to hide the output of batch files.  Set the program to RunProgram="hidcon:install.bat" and the batch file will not be visible as it runs.  This is critical for making silent installs when using batch files.


            Compression level.  9 is highest compression.  0 is no compression.  Using 0 is a good option for large installs that are already mostly compressed.  For example, Lotus Notes only goes down by a few percent with 9 compression, but the install takes several minutes longer to uncompress.  Using 0 is recommended for things like that.