The third way to create an Installation Setup
Initialization file is manually. You can start with a blank file and create the
file line by line (if you're feeling very industrious), or you can use one of the
previous two methods to create a file that you can then edit.
Editing an .ISS file can be accomplished by opening the file from Notepad:
Click to Enlarge
Review the following link to
learn about the different sections of the Installation Setup Initialization file
(this is important for the exam):
Once you have created your custom Installation Setup Initialization file you
need a way to initiate the installation. You can initiate the installation by
entering the appropriate commands at the command prompt or by creating a batch
file to start the installation.
Beginning an unattended installation from the command prompt is not a big deal
if you only have a few systems, located locally, that you need to install SQL
Server on. Imagine if you needed to install the client tools on hundreds of
workstations. To simplify that daunting task we can use a batch file and SMS
(Systems Management Server -
install SQL Server 2000 without having to visit every computer. You can also use
a batch file if the task of installing SQL server will be done by someone who
has very little knowledge of the network or SQL Server. For more information on
batch files look at the examples provided with SQL Server.
No matter which way you choose to start the Unattended Installation, both methods
run setupsql.exe located in the \x86\setup directory of your SQL Server CD (ex:
D:\x86\setup\setupsql.exe). You can then use command-line parameters to specify
how setup should run.
The table below shows you the command line parameters available with
setup in silent mode with no user interface
Specifies an Installation Setup Initialization file ex: -f1 setup.iss
Returns control back to the command line only after setup has completed. You
use this parameter in a batch file in conjunction with the "start /wait"
After you have selected the system you would like to
install SQL Server on, click Next.
Performing an installation of SQL Server 2000 on a remote system is a lot like
performing a local installation of SQL Server. SQL Server Setup accomplishes a
Remote Installation by creating a setup.iss file from the information you
provide, copying the setup file and other files to the \admin$, directory and
then starting a service on the remote server to begin an Unattended Installation
on the remote system.
Due to the fact a Remote Installation is just an Unattended Installation that is
started on a remote system for you, Unattended Installations have the same
restrictions Remote Installations have. This means you can't use a Remote
Installation to setup Failover Clustering, Remove SQL Server, or Change the
Optional Components that are already installed.
To begin a Remote Installation of SQL Server 2000, run the SQL Server Setup as
you normally would. When you are prompted to select the computer you would like
to install SQL Server on, select "Remote Computer" and then enter the name of
the system you would like SQL Server (or the client tools) to be installed on.
You can also click the Browse button to see a list of available systems.
Not a lot of options on the next screen:
Select "Create a new instance of SQL Server, or
install Client Tools" and click Next
The next Setup screen is unique to the Remote Installation. This screen prompts
for the account and path information that will be used to install the SQL
Server. The account you choose should have Administrative privileges on the
remote system. An important thing to note is the account you enter on this
screen is only used during the installation and has nothing to do with the
Services or Logon accounts of SQL Server.
The Target Path you enter should be given in the Universal Naming Convention
form. In this example I am installing the files on the "C" drive of SQL2. The
Setup Source Files textbox specifies the location of the SQL Setup files. In
this example the files are located on the server named CDSRV and are located in
the SQL_ENT share.
Enter the appropriate information and click Next.
From this point on the Remote Installation will prompt you for the Installation
Type, Service Accounts, Authentication mode, Collation, etc. (just like a basic
installation). Once Setup has all the information it needs, it will then begin an
Unattended Installation on the remote system automatically.
Page 3: Types of Clusters
See All Articles by Columnist Michael Aubert