Export (0) Print
Expand All

Silent Installation

The Microsoft Windows Installer (Msiexec.exe) is an executable program that interprets packages and installs products. Msiexec enables you to specify property values from the command line. This method gives you the ability to install Microsoft BizTalk Server 2002 silently (without constant interaction or prompts). A silent installation of BizTalk Server 2002 is ideal for test scenarios or as part of a large-scale enterprise deployment.

Perform a silent installation of BizTalk Server 2002

  1. On the Start menu, click Run.

  2. In the Open box, type cmd and click OK.

  3. Type the following syntax at the command prompt to install BizTalk Server 2002 silently:
    msiexec /I "\\server\folder\Microsoft BizTalk Server.msi"
    /qb /Lv* "C:\Temp\install.log" INSTALLLEVEL=200
    ALLUSERS=1
    DSNCONFIG="C:\Temp\BizTalkInstall.ini"
    

Ee251019.important(en-US,BTS.10).gif Important

  • You must add the ALLUSERS=1 parameter to complete the installation for all users. This parameter also ensures that the services are able to see the registry settings.

  • By default the silent installation process uses a local system account. If SQL Server is on a remote computer, this account must be given permissions to access the computer where SQL Server is installed. Failure to do so will cause the service to fail, and will generate errors when accessing the BizTalk Messaging Management database.

Ee251019.note(en-US,BTS.10).gif Notes

  • The following command-line options are used to run Msiexec in Step 3:
    • /I is the command line to install or configure a product.

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

    • /Lv* produces a log file.

    • 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 2002.

    • DSNCONFIG="C:\Temp\BizTalkInstall.ini" provides installation information to the setup wizard.

You can specify various options at the command line to set properties for a BizTalk Server 2002 installation. Unspecified properties take on the default values. The properties unique to BizTalk Server 2002 are listed in the following table.

Public propertyValueDescription
USERNAME

(Built-in installer property)

<name>

Default: {LogonUser}

The name of the user performing the installation. Customer Information dialog box; User name edit box.
COMPANYNAME

(Built-in installer property)

<organization>

Default: {LogonCompany}

The organization name for the user performing the installation. Customer Information dialog box; Organization edit box.
INSTALLLEVEL

(Built-in installer property)

<install level>

Default: 100

The feature installation level. For BizTalk Server 2002 setup, 100=Client and 200=Server setup type.
INSTALLDIR

(Built-in installer property)

<install path>

Default: "{ProgramFiles} \Microsoft BizTalk Server"

The destination folder for the installation.
BTS_GROUP_NAME

(Complete installation only)

<Group Name>

Default: "BizTalk Server Administrators"

The name of the BizTalk Server 2002 Windows NT® group. ConfigAdminGroup dialog box; Group name edit box.
BTS_GROUP_DESCRIPTION

(Complete installation only)

<Group Description>

Default: "Members can fully administer Microsoft BizTalk Server"

The description of the BizTalk Server 2002 Windows NT group. ConfigAdminGroup dialog box; Group description edit box.
BTS_USERNAME

(Complete installation only)

<username>

Default: ""

The logon DOMAIN\name for the BizTalk Server 2002 service. ConfigServiceLogon dialog box; User name edit box.
BTS_PASSWORD

(Complete installation only)

<password>

Default: ""

The logon password for the BizTalk Server 2002 service. ConfigServiceLogon dialog box; Password edit box.
BTS_SERVER

(Complete and Tools installations)

<servername>

Default: "localhost"

The name of the BizTalk Server to remotely administer. ConfigMgmtDesk dialog box; Server name edit box.
BTS_SDK_SERVER

(Complete and Tools installations)

<servername>

Default: ""localhost""

The name of the BizTalk Server to use for DCOM. ConfigSDK dialog box; Server name edit box.
DSNCONFIG

(Initialization file)

<pathname>

Default: ""

The path of the initialization file for the BTSsetupDB.exe and XLANGsetupDB.exe Database Setup Wizards to use.

Ee251019.note(en-US,BTS.10).gif Notes

  • The DSNCONFIG property is required to complete a silent installation of BizTalk Server 2002. The initialization path file listed on the command line is passed to the BTSsetupDB.exe and XLANGsetupDB.exe database setup wizards. Use one of the following command-line values:
    • DSNCONFIG="Full path to .ini file for BTSsetupDB.exe and XLANGsetupDB.exe"

      -Or-

    • BTSSETUPDB.INI="Full path to .ini file for BTSsetupDB.exe" and XLANGSETUPDB.INI="Full path to .ini file for XLANGsetupDB.exe"
  • The database setup wizard processes the contents of the initialization file using these rules:
    • All [sections] and keys= are optional; if a key is absent, the default value as shown in the sample initialization file is used.

    • If the GroupName exists in the specified BizTalk Messaging Management database, the [InterchangeDTA] and the [InterchangeSQ] sections are ignored because the group defines the values.

    • Specified databases are created if they do not already exist on the specified server.
  • The BizTalk Messaging Management database setup and the Orchestration Persistence database setup are mutually independent.

  • Depending on the features you install, setup configures either, neither, or both of the following:
    • BizTalk Messaging Management database. Configured only if the BizTalk Messaging Service and its associated components are installed.

    • Orchestration Persistence database. Configured only if BizTalk Orchestration Services is installed.
  • The following properties are used on the command line:
    • DSNCONFIG. Specifies the location of .ini file to be used by BTSsetupDB.exe and XLANGsetupDB.exe.

      -Or-

      BTSSETUPDB.INI. Specifies the location of .ini file to be used by BTSsetupDB.exe.

    • XLANGSETUPDB.INI. Specifies the location of .ini file to be used by XLANGsetupDB.exe.

Sample initialization file with all [sections], keys=, and default values shown

The following is an example of the format of an .ini file needed to silently install BizTalk Server 2002. These command-line properties are required to perform a first-time installation of BizTalk Server 2002 using Microsoft Windows Installer.

Ee251019.note(en-US,BTS.10).gif Note

  • Store the following script file in a secure location, deleting Username, Password, and Database name values befor saving the file. Additionally, avoid printing the file or otherwise compromising the file security when storing or sending it. Avoid using the file without a value for the Username or Password, as doing so may cause blank usernames or passwords to be set.

Example SetupDB.ini

;----------------------------------------------------------------------
; SQL Server connection parameters for BizTalk Messaging Management database
; Required section used by BTSsetupDB.exe only.
; Specify new or existing database.
;
[InterchangeBTM]
Server=localhost
; Delete this Username before storing the script
Username=
; Delete this Password before storing the script
Password=
; Delete this Database name before storing the script
Database=InterchangeBTM

;----------------------------------------------------------------------
; Name for BizTalk Server Group
; Required section used by BTSsetupDB.exe only.
; Specify new or existing server group.
;
[Group]
GroupName=BizTalkGroup

;----------------------------------------------------------------------
; SQL Server connection parameters for BizTalk Tracking database
; Required section used by BTSsetupDB.exe only.
; Optional if existing server group specified.
;
[InterchangeDTA]
Server=localhost
; Delete this Username before storing the script
Username=
; Delete this Password before storing the script
Password=
; Delete this Database name before storing the script
Database=InterchangeDTA

;----------------------------------------------------------------------
; SQL Server connection parameters for BizTalk Shared Queue database
; Required section used by BTSsetupDB.exe only.
; Optional if existing server group specified.
;
[InterchangeSQ]
Server=localhost
; Delete this Username before storing the script
Username=
; Delete this Password before storing the script
Password=
; Delete this Database name before storing the script
Database=InterchangeSQ

;----------------------------------------------------------------------
; SQL Server connection parameters for Orchestration database
; Required section used by XLANGsetupDB.exe only.
; Specify new or existing Orchestration database.
;
[Orchestration]
Server=localhost
Database=XLANG

The following table describes the properties and values of the sample BizTalkDB.ini initialization file.

PropertyValueDescription
[InterchangeBTM]Server=BIZTALKLog on to this first SQL Server with default user name and password.
Database=BizTalkBTM

Create this BizTalk Messaging Management database if it does not already exist on the server.

[Group]GroupName=BizTalkServerGroupThe rest of the values are ignored if this group already exists.
[InterchangeDTA]Server=DTA-SERVERLog on to this second SQL Server with default user name and password.
Database=BizTalkDTA 

Create this Tracking database if it does not already exist on the server.

[InterchangeSQ]Server=SQ-SERVERLog on to this third SQL Server with default user name and password.
Database=BizTalkSQ 

Create this Shared Queue database if it does not already exist on the server.

[Orchestration]Server=localhostLog on to this fourth SQL Server with default user name and password.
Database=BizTalkXLANG

Create this Orchestration Persistence database if it does not already exist on the server.


Command-line options of Microsoft Windows Installer

Microsoft Windows Installer (Msiexec.exe) is the program that interprets packages and installs products. It also sets an error level on return that corresponds to the Microsoft® Win32® error codes. The following table describes command-line options for this program that you can use in addition to the properties and values listed previously.

OptionParametersMeaning
/IPackage|ProductCodeInstalls or configures a product.
/f[p|o|e|d|c|a|u|m|s|v] Package|ProductCodeRepairs a product. This option ignores any property values entered on the command line. The default argument list for this option is pecms. This option shares the same argument list as the REINSTALLMODE property.

p - Reinstall only if file is missing.

o - Reinstall if file is missing or if an older version is installed.

e - Reinstall if file is missing or an equal or older version is installed.

d - Reinstall if file is missing or a different version is installed.

c - Reinstall if file is missing or the stored checksum does not match the calculated value. Repairs only files that have msidbFileAttributesChecksum in the Attributes column of the File table.

a - Force all files to be reinstalled.

u - Rewrite all required user-specific registry entries.

m - Rewrite all required computer-specific registry entries.

s - Overwrite all existing shortcuts.

v - Run from source and recache the local package.

/aPackageAdministrative installation option. Installs a product on the network.
/xPackage|ProductCodeUninstalls a product.
/j[u|m]Package

or

[u|m]Package /t Transform List

or

[u|m]Package /g LanguageID

Advertises a product. This option ignores any property values entered on the command line.

u - Advertise to the current user.

m - Advertise to all users of the computer.

t - Apply transform to advertised package.

g - Language ID.

/L[i|w|e|a|r|u|c|m|o|p|v|+|!]LogfileSpecifies the path to a log file; the flags indicate which information to log.

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Startup of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

+ - Append to existing file

! - Flush each line to the log

"*" - Wildcard; log all information except the v option. To include the v option, specify "/l*v".

/mfilenameGenerates a Systems Management Server (SMS) status .mif file. Must be used with the install (-i), remove (-x), administrative installation (-a), or reinstall (-f) option. The Ismif32.dll is installed as part of SMS and must be on the path.

The fields of the status .mif file are filled with the following information:

  • Manufacturer - Author

  • Product - Revision number

  • Version - Subject

  • Locale - Template

  • Serial Number - Not set

  • Installation - Set by Ismif32.dll to "DateTime"

  • InstallStatus - "Success" or "Failed"

  • Description - Error messages in the following order: 1) Error messages generated by installer; 2) Resource from Msi.dll if installation could not commence or user exits; 3) System error message file; 4) Formatted message: "Installer error %i", where %i is the error returned from Msi.dll.
/pPatchPackageApplies a patch. To apply a patch to an installed administrative image, you must combine options as follows:

/p <PatchPackage> /a <Package>

/qn|b|r|fSets the user interface (UI) level.

q, qn - No UI.

qb - Basic UI.

qr - Reduced UI with a modal dialog box displayed at the end of the installation.

qf - Full UI with a modal dialog box displayed at the end.

qn+ - No UI except for a modal dialog box displayed at the end.

qb+ - Basic UI with a modal dialog box displayed at the end. The modal dialog box is not displayed if the user cancels the installation.

qb- - Basic UI with no modal dialog boxes. /qb+- is not a supported UI level.

/?

or

/h

 Displays copyright information for the Windows Installer.
/ymoduleCalls the system API DllRegisterServer to self-register modules passed in on the command line. For example, msiexec /y my_file.dll.

This option is used only for registry information that cannot be added using the registry tables of the .msi file.

/zmoduleCalls the system API DllUnRegisterServer to unregister modules passed in on the command line. For example, msiexec /z my_file.dll.

This option is used only for registry information that cannot be removed using the registry tables of the .msi file.


Ee251019.note(en-US,BTS.10).gif Note

  • In the preceding table:
    • The options /i, /x, /f[p|o|e|d|c|a|u|m|s|v], /j[u|m], /a, /p, /y, and /z should not be used together. The one exception to this rule is that patching an administrative installation requires using both /p and /a.

    • The options /t and /g should be used only with /j.

    • The options /l and /q can be used with /i, /x, /f[p|o|e|d|c|a|u|m|s|v], /j[u|m], /a, and /p.

Syntax rules for properties and values

Only public properties can be modified using the command line. All property names on the command line are interpreted as uppercase, but the value retains case sensitivity. If you type MyProperty at a command line, the installer overrides the value of MYPROPERTY and not the value of MyProperty in the Property table. To install a product with PROPERTY set to VALUE, use the following syntax on the command line. You can put the property anywhere except between an option and its argument.

Correct syntax:

msiexec /i A:\Example.msi PROPERTY=VALUE 

Incorrect syntax:

msiexec /i PROPERTY=VALUE A:\Example.msi 

Property values that are literal strings must be enclosed in quotation marks. Include any white spaces in the string between these marks.

msiexec /i A:\Example.msi PROPERTY="Embedded White Space"

To clear a public property using the command line, set its value to an empty string.

msiexec /i A:\Example.msi PROPERTY="" 

For sections of text set apart by literal quotation marks, enclose the section with a second pair of quotation marks.

msiexec /i A:\Example.msi PROPERTY="Embedded ""Quotes"" White Space"

The following is an example of a complicated command line.

msiexec /i testdb.msi INSTALLLEVEL=3 /l* msi.log COMPANYNAME="Acme ""Widgets"" and ""Gizmos."""

The following example illustrates advertisement options. Switches are not case sensitive.

msiexec /JM msisample.msi /T transform.mst /G langid /LIME logfile.txt

For more information about Microsoft Windows Installer, go to the Microsoft® MSDN® Web site (msdn.microsoft.com/downloads/).


Did you find this information useful? Please send your suggestions and comments about the documentation to BizTalk Server Documentation Feedback@microsoft.com



Show:
© 2015 Microsoft