Skip to main content

STAF silent install with options on user login and quick menu

By
STAF is a software test automation framework, see this link for more information. When installing the software remotely without manual intervention, silent install is must have feature. The package was actually created using InstallShield Multiplatform. In fact silent installation is documented in the STAF User's Guide. But unfortunately it does not mention all the options, just the most frequently used ones. What I am going to do here is to document how to get those options and a sample command to install STAF with "Start STAF on user login" and "Place Icons on the Quick Start Menu" not included during installation. To get the command line options, you need to read the InstallShield .uip file that defines all those options. For STAF this can be found from this link. To get the command line option for "Start STAF on user login" and "Place Icons on the Quick Start Menu" was not really that challenging because the developers were using variables that pretty much describes them. Example, stafOptions.startSTAFOnLogin was used for "Start STAF on user login" and stafOptions.iconsOnQuickStartMenu was used for "Place Icons on the Quick Start Menu." With the information at hand, command should now look like below: 
d:\>STAF323-setup-win32 -is:log D:\ismplog.txt -silent -W license.selection="Accept" -W setupTypes.selectedSetupTypeId="Full" -W stafOptions.updateEnvironmentVariables="System" -W stafOptions.defaultIPvVersion="IPv4 only" -W stafOptions.startSTAFOnLogin="false" -W stafOptions.iconsOnQuickStartMenu="false"
This assumes that STAF323-setup-win32.exe is in the system path or on D:\. ~ts
Labels:

Comments

Post a Comment

Popular posts from this blog

The following add-ins could not be started MonoDevelop.GnomePlatform

By
Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.
21 comments
Read more

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

By
Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re
11 comments
Read more