The application can be uninstalled using the silent install parameters again: Be aware, however, that some MSI routines ignore both parameters falling back to their default destination path. Since MSI routines tend to ignore the INSTALLDIR parameter in favor of the TARGETDIR parameter, I recommend to pass both using the same value. This example installs the application into C:\tools\myApp and appends a verbose installation protocol to C:\logs\myApp.log. Msiexec /package installer.msi /qn /LV "C:\logs\myApp.log" TARGETDIR="C:\tools\myApp" INSTALLDIR="C:\tools\myApp" MSI should be called with the following silent install parameters: A setup file based on this installer is always extended with. This installer can be identified quite easily. Usually only few software products are bundled using this installer. Microsoft’s preferred installation technology is the so called Windows Installer, formerly known as Microsoft Installer. In the following I will describe the different installers, how to identify them, and which parameters are necessary for an automated installation. All of them need their own specific parameters for a silent installation. However, this varies largely depending on the underlying installation technology.ĭuring my automation project for Windows environments I got in touch with six different installers. This means that the information, which is usually gathered via the graphical assistant, has to be passed via the command line. Unfortunately the graphical assistant cannot be used for automated silent software installations, as there is no user interaction involved. This always works quite the same way regardless of the software vendor. windows/setup.exe, it installs fine displaying the default -ident.Most Windows applications can be installed very easily using the graphical installation assistant by clicking Next-Next-Finish. The installs are downloaded directly from 3ds support site using my login details as provided, so they are "official packages". I have also tried to remove the "-ident" function completely, as I assumed tis would default to the long name, and still no luck. I’ve set the "-ident" parameter in the stardb.exe command to R24 and have also tried the long name "-6R2014" but still I get "UnofficialPkgVersion". My problem is the "UnofficialPkgVersion" part as the "-ident" switch does not seem to be working. I have used the same since V5R18 but now since the upgrade from R20 to V5R24 I get it to install yes, but the shortcuts to desktop and start menu are called "CATIA UnofficialPkgVersion" and "ENOVIA DMU Navigator UnofficialPkgVersion" respectively. So, I have a silent install batch file I use for installing my Catia V5. Sometimes I need multiple Catia's installed and they often happen to be installed in different locations and at different SP
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |