Unattended Options

For situations in which you will be configuring several BizTalk servers either in the same or different server groups, you probably will want to avoid manually performing the installation on each server. Instead, use the silent installation features to help ensure that the servers have identical settings. For example, let's say that we have three servers that are going to be part of the same Server group and share SQL that is installed on a fourth server, such as BIZTALK, BIZTALK2, BIZTALK3, and SQLServer!.. For this example, we'll pretend that we have copied the entire CD up to a network share called BTFILES on a server called IMAGESERVER.We have also created an INI file called SQLSettings.ini to contain our SQL Server configuration, and all these servers are a member of a domain called BTDOMAIN.

Here is an example command line that will provide for a completely silent installation (this is one line, let it wrap; we broke it down to make it easier to read):

msiexec /I "\\IMAGESERVER\BTFILES\Microsoft BizTalk Server.msi" /qb /Lv*"C:\Temp\install.log" INSTALLLEVEL=2 00




PIDKEY="your 25-character product key (without dashes)" DSNCONFIG="\\IMAGESERVER\BTFILES\SQLSettings.ini"

The preceding command line is documented here:

■ ALLUSERS=1 controls the setting that allows the Registry changes made during the installation to be seen by all users. It is required.

■ BTS_USERNAME= is the domain name and username of the service account you want to configure BizTalk Server to use.Without this, it defaults to the Local system account and is not recommended. You can also use a Local account; in that case, you could supply .\BizTalkService to avoid having to change the file for each server you want to use this file with. However, you would still have to create this user account before the installation.

■ BTS_PASSWORD= is the password for the user specified on the BTS_USERNAME parameter

■ /I is the command line to install the product rather than uninstall.

■ /qb is the command line to present a basic user interface (progress bar only).

■ /Lv* produces a log file based on the location and filename that you specify.

■ INSTALLLEVEL=200 installs the server. If you do not specify the INSTALLLEVEL, the value defaults to 100, which is the Tools installation of BizTalk Server 2000.

■ PIDKEY="your 25-character product key (without dashes)"

is the product key. For example, PIDKEY= AB6CDEFGH7IJK8LMN45LLTT34.


provides DSN installation information to the Setup wizard.

Table 2.3 lists some other possible command-line options, their default values, and their descriptions.

Table 2.3 Other Command-Line Options


Default Value



Logged on User Name

The username information from the initial manual installation screen.


Logged on Company

The organization information from the initial manual installation screen.


"\Program Files\ Microsoft BizTalk Server"

The installation root directory.




The name of the Windows NT group that the installa tion will create.



"Member can fully administer Microsoft BizTalk Server"

The description for the Windows NT group.



The name of the BizTalk server.



Table 2.3 Continued

Parameter Default Value Description

BTS_SDK_SERVER "localhost" The name of the server for DCOM access (Ilnterchange).


.ini can be broken down into two files. This file path supplies the location of the .ini file containing the information for the Messaging Service Database Configuration Wizard, BTSsetupDB.exe.

XLANGSETUPDB.INI "" Supplies the file path to the .ini containing the information for the XLANG Database wizard, XLANGsetupDB.exe.

DSN Configuration File

This simple text file contains information about your SQL server, database names, and server group information. There are five basic sections within this text file, which are shown next. If the BizTalk Server group already exists, the rest of the settings are ignored. If the databases already exist, they will be left alone. This makes this script able to be used on the first and subsequent installations. If any of these values are not supplied, it uses a default value in each case. Server defaults to localhost and the other defaults have not been changed from the example file shown here:


; SQL Server connection parameters for BizTalk Messaging Management database

; Required section used by BTSsetupDB.exe .

; Specify new or existing database.






; Name for BizTalk Server Group ; Required section used by BTSsetupDB.exe ; Specify new or existing server group.



; SQL Server connection parameters for BizTalk Tracking database ; Required section used by BTSsetupDB.exe .

; Optional if existing server group specified.

[InterchangeDTA] Server=SQLSERVER1 Username=sa Password=


[InterchangeSQ] Server=SQLSERVER1 Username=sa Password=


; SQL Server connection parameters for Orchestration database

; Required section used by XLANGsetupDB.exe .

; Specify new or existing Orchestration database.




Was this article helpful?

0 0

Post a comment