Menu
Quite often an exe uses /silent, /s, /q, or /quiet to do a silent install, but it may need a response file recorded first. Do a /?, which will usually give you an idea of what options there are. Also check documentation, as that will many times give you an idea of how to do a managed install. You may need to experiment. Use this command line to run the installation in record mode. In order to run an InstallScript MSI or InstallScript installation in silent mode, you must first run Setup.exe with the /r option to generate a response file, which stores information about the data entered and options selected by the user at run time.
Hello, I am fairly new to AutoIT and I have been trying to create a script for silent installs on a machine. There are two separate files I am trying to install one after another. Is there any reason why I am using the commands RunWait('C: ACMS cache JuniperEVPNClient17087 JuniperEVPNClient17087 JuniperSetupServiceInstaller.exe /S') RunWait('C: ACMS cache JuniperEVPNClient17087 JuniperEVPNClient17087 NCInst64.exe /S') I am not able to run the other command, no errors or anything. I am able to run that same command through the command prompt. If I put in RunWait('C: ACMS cache JuniperEVPNClient17087 JuniperEVPNClient17087 JuniperSetupServiceInstaller.exe /S') RunWait('C: ACMS cache JuniperEVPNClient17087 JuniperEVPNClient17087 JuniperSetupServiceInstaller.exe /S') I can install the same service twice but not a different one.
One reason I know it's not installing is because the NCInst64.exe is not prompting me for an admin password like it should. Thank you for your assistance. I apologize, I feel as though I did not word my question correctly. I am installing an application that has two install parts to it, first part is the JuniperSetupServiceInstaller.exe and the second part is NCInst64.exe When I use the RunWait command on JuniperSetupServiceInstaller.exe /S, it works perfectly fine, even without the @SWHide flag. In my code, I have RunWait(JuniperSetupServiceInstaller.exe /S') and follow by this line, I have RunWait(NCInst64.exe /S') Is there for any reason why the NCInst64.exe /S isn't even launching when I run this code?
If for some reason I try to run JuniperSetupServiceInstaller.exe twice, it will go through but not NCInst64.exe. Also, where is the correct place to place the @SWHide? Would it be RunWait('C:ACMScacheJuniperEVPNClient17087JuniperEVPNClient17087JuniperSetupServiceInstaller.exe /S', ', ', @SWHide) or RunWait('C:ACMScacheJuniperEVPNClient17087JuniperEVPNClient17087JuniperSetupServiceInstaller.exe /S', @SWHide) Thank you -ET.
. What Is Silent-Mode Installation? Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create prior to beginning the installation.
The installation program does not display any configuration options during the installation process. Silent-mode installation works on both Windows and UNIX systems. The instructions in this section are based on the assumption that you have already acquired the installation program either on DVD or from the BEA Web site.
Using Silent-Mode Installation: Main Steps The silent-mode installation process has two primary steps. Create a silent.xml file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For example, values for the BEA Home directory, the product directory, and the components to be installed are supplied in a silent.xml file. For a detailed procedure, see. For a sample silent.xml file, see. Start the silent-mode installation process using the values specified in the silent.xml file. For details on starting the installation in silent mode, see Important Considerations for Silent-Mode Installation When you are performing an installation in silent mode, keep in mind the following considerations.
Silent-mode installation requires the same amount of temporary disk space and uses the same temporary storage directories as a standard installation. The installation program does not alert you if there is not enough space in the temporary directory. A silent-mode installation takes the same amount of time as a standard installation. At the beginning of a silent-mode installation, an initial installation program window or message is displayed briefly, indicating that the installation has started. No messages are displayed to indicate that the installation is in progress or has completed successfully. Incorrect entries in the silent.xml file can cause installation failures.
To help you determine the cause of a failure, we recommend that you create a log file when you start the installation. The XML definition ( ) must be at the very beginning of the silent.xml file. There cannot be any spaces or line breaks before the XML definition. You cannot reinstall any BEA product on top of a previously installed version of the same product—in the same BEA Home directory or in the same file location. You can, however, add products and product components to an existing installation. For example, you can install WebLogic Server during one installation, and Workshop for WebLogic during a separate installation.Also to reinstall the same version of one of the products, you must first uninstall the previously installed instance of it or install the new instance in another location. Creating a silent.xml File for Silent-Mode Installation When you install your BEA software in silent mode, the installation program uses an XML file ( silent.xml) to determine which installation options should be implemented.
Therefore, before you can run the installation program in silent mode, you must first create a silent.xml file in which you specify the installation options that you want to have invoked. Note: Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation. To create a silent.xml file for use in the silent-mode installation process, follow these steps. In a supported browser, display the sample silent.xml file for silent-mode installation. Click to see the. This sample silent.xml file is also presented later in this chapter.
Save the sample XML file, with the name silent.xml, in the same directory that contains the installation program. Note: The XML definition ( ) must be at the very beginning of the silent.xml file. There cannot be any spaces or line breaks before the XML definition.
In the silent.xml file that you saved on your system, edit the values for the keywords shown in to reflect your configuration. Note: You must follow XML guidelines for characters when modifying values. That is, you cannot use characters reserved for use in XML, such as, , and.
If you do not include the COMPONENTPATHS data-value name in the silent.xml file, the complete WebLogic Server, Workshop for WebLogic, and WebLogic Portal products are installed. Note: The installation program performs dependency checking to ensure that all components that provide functionality on which other components depend for proper operation are installed. These dependencies are visible during graphical and console mode installations.
The same dependencies are enforced during silent installation: components on which other components depend are installed even if they are not explicitly referenced in a silent script. Sample silent.xml file for Silent-Mode Installation When you install your BEA software in silent mode, the installation program uses an XML file ( silent.xml) to determine which installation options should be implemented. For details about creating the silent.xml file, see. See for the sample file. Returning Exit Codes to the Console When run in silent mode, the installation program generates exit codes that indicate the success or failure of the installation. These exit codes are shown in the following table. Rem Execute the installer in silent mode @echo off platform win32.exe -mode=silent -silentxml=C: downloads silent.xml -log=C: logs productssilent.log @rem Return an exit code to indicate success or failure of installation set exitcode=%ERRORLEVEL% @echo.
@echo Exitcode=%exitcode% @echo. @echo Exit Code Key @echo - @echo 0=Installation completed successfully @echo -1=Installation failed due to a fatal error @echo -2=Installation failed due to an internal XML parsing error @echo. Using the Upgrade Installer in Silent Mode When you upgrade your installation in silent mode, you define the settings in an XML file that you create prior to beginning the upgrade installation. During the silent upgrade installation process, the installation program reads the settings for your configuration from the XML file. The installation program does not display any configuration options during the installation process.
Silent-mode upgrade installation works on both Windows and UNIX systems. The process for upgrading your installation in silent mode is similar to that used for silent-mode installation. For information about silent-mode installation, see. To complete an upgrade installation in silent mode on UNIX and Windows systems, perform the following steps. Create a silent-mode XML file as described in. Make backup copies of any files or applications that you have created in WLHOME. (As part of the upgrade procedure, the installation program automatically overwrites any files, including applications, that you have created in this directory.) For a description of the WLHOME directory, see.
Note: In some cases, changes are made in the config.xml file between service packs. You may want to make backup copies of the config.xml file in any user-created domains also, in case you later want to roll back or uninstall an upgrade installation.
Download the upgrade installer specific to your platform from the BEA Customer Support Web site at. Note: To download updates, you will need to log in using your eSupport username and password. If you do not have an eSupport account, you can register for one on the BEA Customer Support Web site. Shut down any servers that are running. Invoke the silent-mode upgrade installation process as described in the following table. Note: Incorrect entries in the silent.xml file can cause installation failures.
To help you determine the cause of a failure, we recommend that you create a log file when you start the installation. Open an MS-DOS command prompt window. Go to the directory in which you downloaded the installation program, and invoke the installation procedure by entering the following command: filename.exe -mode=silent -silentxml=pathtosilentxml Here filename.exe is the name of the upgrade installer you downloaded from the BEA Customer Support Web site, and pathtosilent.xml is the full pathname of the silent.xml template file.
Note: You can also include the -log=fullpathtologfile option in the command line to create a verbose installation log. For example: platformXXXupgradewin32.exe -mode=silent -silentxml=C: silent.xml -log=C: logs platforminstall.log In this example, XXX represents the version number of the software you are installing. For more information, see. Here is the name of the upgrade installation program you downloaded from the BEA Customer Support Web site, and pathtosilent.xml is the full pathname of the silent.xml template file.
Note: You can also include the -log=fullpathtologfile option in the command line to create a verbose installation log. For example: platformXXXupgradesolaris.bin -mode=silent -silentxml=/home/silent.xml -log=/home/logs/platforminstall.log. In this filename, XXX represents the version number of the software you are installing.
For more information on creating a log file, see. Where filename.jar is the name of the upgrade installation program you downloaded from the BEA Customer Support Web site, (for example filename, pjplatformXXXupgradegeneric.jar, in this, XXX represents the version number of the software you are installing), and pathtosilent.xml is the full path to the silent.xml template file.
Note: You can also include the -log=fullpathtologfile option in the command line to create a verbose installation log. For example: pjplatformXXXupgradegeneric.jar -mode=silent -silentxml=/home/silent.xml -log=/home/logs/platforminstall.log For more information, see. Creating a Silent-Mode Upgrade Installation XML File When you upgrade WebLogic Platform in silent mode, the installation program uses an XML file (silent.xml) to determine which BEA Home directory contains the installation to be upgraded. Therefore, before you can run the upgrade installation program in silent mode, you must first create a silent.xml file.
Note: If you created a silent.xml file when you initially installed WebLogic Platform, you should store it in a safe location or make a backup copy of it so that you do not accidentally overwrite it with the silent.xml file you are creating for your upgrade installation. Alternatively, you can name your upgrade file using a different file name, for example silentupgrade.xml. Note: Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.
Note: Do the following to create a silent.xml file for use in the silent-mode upgrade installation process. In a supported browser, display the XML template file for silent-mode upgrade installation. The sample template file, silentupgrade.xml, is available at. In the popup window that is displayed, choose FileSave As. Specify the file name silentupgrade.xml and save it in the directory containing the upgrade installation program that you downloaded from the BEA Customer Support Web site.
Note: The XML definition ( ) must be at the very beginning of the template file. There cannot be any spaces or line breaks before the XML definition. In the silentupgrade.xml file, replace the value for the BEAHOME keyword with the full pathname of the BEA Home directory associated with the particular installation of WebLogic Platform that you want to update and save the file.
Note: You must follow XML guidelines for characters when modifying values. That is, you cannot use characters reserved for use in XML, such as, , and. Sample Template File for Silent-Mode Upgrade Installation. We recommend that you run the QuickStart application to familiarize yourself with the software and execute the samples provided.
For additional information, see Note: QuickStart is not invoked automatically for console-mode or silent-mode installations. You can launch QuickStart from the Start Menu (Windows), or from the command line (Windows and UNIX). For instructions, see. For specific information about your software release, see the appropriate release notes.