I have had to do a few Registry detection methods loosely based on the following:Ĩ. Installshield Run Batch FileThis can be based on MSI (if there was an optional MSI with the application), or on Registry key. For the command line, enter install.cmd (or install.bat).ħ. Be sure to specify it as a Script installer when adding the application. Add the application using the SCCM Console. Installshield run batch file install#This install.bat can be run normally to perform a silent (unattended) install of the application.Ħ. Save the file as install.cmd (or install.bat) into your SCCM's application share folder. Setup.exe -s -f1'.setup.iss' -f2'%TEMP%Appinstall.log' Create an installation bat file with the following (general) contents: Copy this file to your application's source files folder on the SCCM share.ĥ. When the application setup finishes, the setup.iss file is generated and placed in the C:Windows folder of the computer it installed on. Install the application as you would normally for every user in Record mode. Hold Shift, then right-click a blank area of the folder, then click Open command window here. To do this, open an Explorer window, navigate to your SCCM server's file/application share, then to the folder of the application source files. Open a command prompt in the folder of the application's source files. This is done to generate a setup.iss file. Install the application in 'Record' mode. Most of the time, they will have a setup.exe and no MSI file, although there are sometimes MSI files alongside the setup executable - it's usually better to follow this tutorial than add the MSI file due to extra requirements needed by the application's setup.ģ. Copy the Installshield application source file(s) to your SCCM file share.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |