StarQuest Technical Documents

Deploying a Silent Installation of StarSQL using Microsoft Systems Management Server (SMS)

Last Update: 26 June 2008
Product: StarSQL
Version: 5.x
Article ID: SQV00SQ046


A silent installation uses the settings specified in a response file instead of prompting for user input. This reduces the installation time and ensures that StarSQL is installed the same way on every computer. Once a silent installation package has been created, StarSQL can easily be deployed to a large number of desktops using Microsoft Systems Management Server (SMS). This document describes how to create a silent installation package of StarSQL and provides a sample SMS package definition file (PDF). 


  1. Create a silent installation package of StarSQL using the instructions in the technical document Creating a Custom StarSQL v5.x Installable Image, which also describes how you can import StarSQL ODBC data sources and license information during the silent installation.
  2. After you have created and tested the silent installation package, create an SMS package definition file using the following sample as a guideline.


[Package Definition]
Publisher=StarQuest Ventures, Inc.
Comment=StarSQL Installation

Comment=Silent Installation of StarSQL
CommandLine=setup /s /f1%RESPONSEFILE% /f2%LOGFILE% /v"ADDLOCAL=Core,SQ_SPECIFIC,AS400,TCPIP,TrcStart,PDF,StarSQL_Help"
SupportedClients=Win 9x, Win NT(i386)

NOTE: The CommandLine parameter value in the above PDF is only a sample. Replace it with the setup command that installs the features you want to install on each computer. The technical document Creating a Custom StarSQL v5.x Installable Image describes the setup command options and syntax.

Refer to the Microsoft Systems Management Server documentation for information on additional SMS options.


The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.