Last updated: February, 2005
The Microsoft® BizTalk® Server 2004 Installation Guide provides guidelines for hardware and software requirements, and instructions for installing and removing BizTalk Server.
To ensure that you are reading the most up-to-date information, download the latest version of the BizTalk Server Installation Guide, at http://go.microsoft.com/fwlink/?linkid=22120.
International Do not install BizTalk Server 2004 on computers whose names contain characters outside of the following set: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only computer names that contain the characters in these sets are supported.
This section contains:
Prior to installing BizTalk Server 2004, you should review this document, as well as "Microsoft BizTalk Server 2004 Readme," which contains important, late breaking information about this release of BizTalk Server 2004, and is located in the root directory on the BizTalk Server 2004 installation CD.
For information about current issues since the initial release of BizTalk Server 2004, see Knowledge Base article 834624 located at http://go.microsoft.com/fwlink/?LinkId=22784.
Note the following permissions requirements for different types of installation:
| Type of installation | Permissions requirements |
|---|---|
| To install BizTalk Server using the Installation Wizard | You must:
|
| To install BizTalk Server using Terminal Services | You must be a local administrator on the computer on which you are installing BizTalk Server. |
| To install BizTalk Server on two or more computers, and you plan to use local user and group accounts (or domain user and group accounts): | You must use the same user account and group account names on both the local and the remote computers.
BizTalk Server supports local user and group accounts only in single computer configurations. BizTalk Server supports domain user and group accounts in both single and multiple computer configurations. |
It is highly recommended that you secure your deployment by installing the Enterprise Single Sign-On (SSO) master secret server as a stand-alone server. For more information about configuring SSO in a stand-alone environment, see "Configuring SSO in a Stand-Alone Environment" in BizTalk Server Help.
Note BizTalk Server automatically creates the SSO Administrators groups in SQL Server 2000 if you have specified group accounts and the user running the Configuration Wizard has administrator privileges on the remote computer. You create all group accounts during configuration, not during installation.
For more information about setting up the appropriate groups, see "Windows Group and User Accounts in BizTalk Server" in BizTalk Server Help.
For information about configuring SSO in a cluster environment, see "Clustering the Master Secret Server" in BizTalk Server Help.
The minimum hardware requirements for a complete installation of BizTalk Server include:
This section includes information about installing prerequisite software prior to installing Microsoft® BizTalk® Server 2004.
The following is required for all BizTalk Server installations:
-or-
This installation guide provides information for properly configuring Windows to support an installation of BizTalk Server.
Important You must install Windows Server 2003 on your computer in order to use Business Activity Services (BAS) with Windows SharePoint® Services. If you do not install these prerequisites, and you select a complete installation, you cannot configure BAS. You do not have to install Windows SharePoint Services unless you plan on using BAS.
BizTalk Server development tools are based on Microsoft® Visual Studio® .NET 2003. You need to install only the Visual C#® .NET portion of Visual Studio .NET 2003 on your computer before you install BizTalk Server development tools.
You must install Microsoft SQL Server™ 2000 with Service Pack 3a on your computer or have it accessible remotely.
This section contains:
The following installation requirements provide information for properly configuring Windows with SQL Server 2000, Visual Studio .NET, Windows SharePoint Services, and BizTalk Server.
Important You must install either Windows Server 2003 or Windows Small Business Server 2003, Premium Edition, if you plan to include Business Activity Services (BAS) with your installation of BizTalk Server. BAS depends on Windows SharePoint Services that you can only install on Windows Server 2003 or Windows Small Business Server 2003, Premium Edition.
You can also use Windows 2000 Server for a complete installation of BizTalk Server, however, during the installation process, BizTalk Server will not install BAS. For more information on BAS, see "Business Activity Services" in the BizTalk Server Help.
You can use Windows XP Professional in development environments.
Additional Windows requirements include Microsoft Internet Information Services (IIS) and ASP.NET.
After installing Windows, you must be logged on as an administrator, or add a Windows user account to the Administrators group in order to install additional software.
This section contains:
Active Directory®, which is an essential component of the Windows 2000 and Windows Server 2003 architecture, presents organizations with a directory service designed for distributed computing environments. Active Directory allows organizations to centrally manage and share information on network resources and users while acting as the central authority for network security. In addition to providing comprehensive directory services to a Windows environment, Active Directory is designed to be a consolidation point for isolating, migrating, centrally managing, and reducing the number of directories that companies require.
The following items should be considered when integrating with Active Directory:
If Windows Server 2003 is not installed on your computer, go to the Microsoft Windows Web site (http://go.microsoft.com/fwlink/?LinkId=17552) for more information about purchasing and installing Windows Server 2003.
You must install Internet Information Services (IIS) on the server if you are using the Simple Object Access Protocol (SOAP) adapter or the Hypertext Transfer Protocol (HTTP) adapter. By default, Windows Server 2003 does not install IIS after you install Windows Server 2003. You must manually install it.
If Windows Small Business Server 2003, Premium Edition, is not installed on your computer, go to the Microsoft Windows Web site at http://go.microsoft.com/fwlink/?LinkId=17552 for more information about purchasing and installing Windows Small Business Server 2003.
To support Windows Small Business Server 2003, Premium Edition, customers, BizTalk Server includes a pre-defined, custom setup script for the Small Business Server platform to create a secure configuration. This script, SetupforSBSPremium.vbs, is located in the root installation folder of BizTalk Server Partner Edition.
The script runs a silent BizTalk Server installation and then automatically launches the Configuration Wizard with the pre-defined configuration for Windows Small Business Server 2003. This script also creates the appropriate user accounts for configuring BizTalk Server. These user accounts have secure, auto-generated passwords. Although these passwords are not documented, local administrators can change them if needed.
After you have installed all the software prerequisites, you can run the Windows Small Business Server 2003 custom setup script by double-clicking SetupforSBSPremium.vbs located in the root installation folder of BizTalk Server Partner Edition.
If you have not installed Windows 2000 Server or Windows XP Professional on your computer, go to the Microsoft Windows Web site for more information about purchasing and installing Windows at http://go.microsoft.com/fwlink/?LinkId=17552.
If you have Windows 2000 Server or Windows XP Professional installed on your computer, ensure that you meet the following requirements:
Note BizTalk Server does not support Windows NT4.0 domains.
In addition to the software listed in the Software Prerequisites, install the following software:
Note Reapply Service Packs even after silent installations have completed; otherwise error messages appear.
Note Apply this hotfix if you are using certificates for any type of encryption. This hotfix only applies to Windows 2000 Server and Windows XP.
You must install and enable Internet Information Services (IIS) and ASP.NET for Windows Server 2003 and Windows XP before you can publish BizTalk orchestrations and schemas as Web services.
If you did not select IIS on the Windows Server 2003 (or Windows XP) Components page during setup of Windows Server 2003 (or Windows XP), use the following procedure to install it.
Important The version of IIS included with Windows XP allows only a maximum of 10 simultaneous TCP connections. It is not as versatile or as powerful as the version shipped with Windows Server 2003, Enterprise Edition, or Windows 2000 Server.
Note Microsoft Windows 2000 Server installs IIS by default.
To install Internet Information Services 6.0 on Windows Server 2003
Note The Configure Your Server Wizard enables ASP.NET by default, which is needed for the SOAP adapter.
Caution The IIS 6.0 configuration does not allow ISAPI extensions by default. You must explicitly configure this before using BizTalk Server HTTP receive handlers.
Note If you have upgraded your operating system from Windows 2000 Server to Windows Server 2003, the default IIS setting is IIS 5.0 in isolation mode. You must turn off IIS 5.0 isolation mode. For more information about configuring servers for applications in IIS 6.0, see Microsoft Knowledge Base Article 814868 located at http://support.microsoft.com/default.aspx?scid=814868.
To install Internet Information Services 5.1 on Windows XP
Note There may be several other IIS components selected by default. These components are optional. If you will be installing Visual Studio .Net onto this computer, then you must install the Microsoft® FrontPage® Server Extensions.
For more information about installing and enabling ASP.NET on Windows Server 2003, Windows 2000 Server, and Windows XP, go to http://go.microsoft.com/fwlink/?LinkId=21100.
When you configure BizTalk Server, the configuration process creates several BizTalk Server databases. To properly configure BizTalk Server databases, you must install Microsoft SQL Server 2000 with Service Pack 3a (SP3a), or have remote access to an installation of SQL Server SP3a.
Important Although the download page for SP3a states that you do not need to apply the patch if you have already applied SP3, it is a requirement for BizTalk Server 2004.
During BizTalk Server configuration, BizTalk Server prompts you for the SQL Server 2000 computer and database information necessary to configure BizTalk Server databases. BizTalk Server supports local user and group accounts only in single computer configurations. BizTalk Server supports domain user and group accounts in both single and multiple computer configurations.
Note You must specify domain groups and user accounts when you install BizTalk Server 2004 in a multiple computer environment. For more information, see Knowledge base article 872924 at http://support.microsoft.com/?id=872924
.SQL Server Administrative privileges are required to run the Configuration Wizard and configure the necessary databases. If you plan to use a remote SQL Server, you must establish these privileges on the remote computer before you run the Configuration Wizard.
For more information about configuring BizTalk Server using a remote SQL Server, see "BizTalk Server Database Creation and Configuration" in BizTalk Server Help.
To install SQL Server 2000, insert the Microsoft SQL Server compact disc into the CD-ROM drive and follow the on-screen instructions for any SQL Server 2000 installation prerequisites (if any). The Setup Wizard walks you through the steps necessary to install SQL Server.
Observe the following requirements:
Microsoft BizTalk Server supports collations commonly associated with BizTalk Server language versions. BizTalk Server is available in English, French, German, Italian, Japanese, Korean, Simplified Chinese, Spanish and Traditional Chinese.
The exact list of supported collations is:
If you install SQL Server 2000 on a computer with system locale corresponding to one of these languages, the appropriate collation is set during the default installation of SQL Server 2000. In all other instances, the collation must be set during a custom install of SQL Server 2000 to one of the collations previously listed. Ensure that the collation selected is not case-sensitive or binary. If the SQL Server 2000 computer has a binary or case-sensitive collation, the BizTalk Service may fail to install.
Caution When using the SQL Server 2000 shared memory network library with BizTalk Server, you may experience degradation in performance under certain stress conditions, if clients are accessing SQL Server 2000 from the same computer. To resolve this issue, disable the shared memory network library in the SQL Client Network Utility. To disable the shared memory network library, open the SQL Server 2000 Client Network Utility and clear the Enable shared memory protocol check box.
After you install SQL Server 2000, you must install SQL Server 2000 Service Pack 3a (SP3a). For more information about SQL Server 2000 SP3a, go to http://go.microsoft.com/fwlink/?LinkId=22839.SQL Server Analysis Services is optional. It is required only if you want to use Health and Activity Tracking (HAT) or Business Activity Monitoring (BAM). If you install SQL Server Analysis Services, you must also install Service Pack 3a (SP3a) for Analysis Services.
Important In a distributed environment, install the SQL Server Analysis Services Decision Support Objects (DSO) COM object on the BizTalk Server Runtime computer, otherwise, the Configuration Wizard may fail during Business Activity Monitoring (BAM) configuration of Microsoft Online Analytical Processing (OLAP) objects.
BizTalk Server development tools are based on Visual Studio .NET 2003. Therefore, you must have the Microsoft Visual C#® .NET portion of Visual Studio® .NET 2003 installed on your computer before installing BizTalk Server development tools.
For installation instructions for Visual Studio .NET 2003, go to the Visual Studio .NET Web site on MSDN http://go.microsoft.com/fwlink/?LinkId=17557.
Important You must install the FrontPage Server Extensions prior to installing Visual Studio .NET.
To install Visual Studio .NET
Important To work with the BizTalk Server development tools, you must select Visual C# as one of the options. You may choose other languages, but only Visual C# is required.
Important You must also install the Visual Studio product documentation for BizTalk Server User Interface (F1) Help to work in the Visual Studio environment. If you do not install the Visual Studio product documentation, and you attempt to use F1 Help for BizTalk Server, Help for Visual Studio does not install as indicated by an error message.
Microsoft® Windows SharePoint® Services is required software for a complete or custom installation of BizTalk Server, which includes Business Activity Services (BAS). You can only install Windows SharePoint Services on Windows Server 2003. If you do not install Windows SharePoint Services, BAS does not install with BizTalk Server.
Note Windows 2000 Server, unlike Windows Server 2003 and Windows XP, does not include the standard logon services — Network Service, Local Service, and Local System — for use with SQL Server 2000. Use the Trading Partner Manager (TPM) database on a SQL Server 2000 computer with Windows Server 2003 or Windows XP. When configuring Windows SharePoint Services, do not use standard logon services like Network Service; rather, use a valid service account.
You must uninstall Microsoft FrontPage Web Server extensions if you have installed them.
To uninstall Microsoft FrontPage Web Server extensions
Refer to the "Windows SharePoint Services Administrator's Guide" at http://go.microsoft.com/fwlink/?LinkId=18110 for further information about installing Windows SharePoint Services.
Important Windows Server 2003 must be running as a Web server running Internet Information Services 6.0 in IIS 6.0 worker process mode. You must enable ASP.NET on the server before installing Windows SharePoint Services.
Important When installing Windows SharePoint Services, choose Server Farm as your database option because your environment will be using SQL Server 2000 rather than Microsoft SQL Server 2000 Desktop Engine (MSDE 2000).
Important If the SharePoint Configuration database, Content database, and BizTalk Server exist on different computers, and if you use Windows authentication to access those databases, you must have db_owner permissions on these databases when running BizTalk Server configuration. After BizTalk Server configuration is complete, these permissions should be removed from the SharePoint Configuration and Content databases.
When the Windows SharePoint Services installation is complete, the SharePoint Central Administration page opens.
You can now configure an administration site and apply Windows SharePoint Services to a virtual server using SharePoint Central Administration.
After you install Windows SharePoint Services, you must extend the server by configuring an administration site and applying Windows SharePoint Services to a virtual server. You must extend a virtual server with Windows SharePoint Services before you can create a Windows SharePoint Services Web site.
To configure Windows SharePoint Services
By default, Windows SharePoint Services includes the root of the IIS default Web site as a managed path. To create a virtual directory on a Windows SharePoint Services-extended virtual server for your own use (for example, for a BizTalk Server receive location or for a Web service application), you must exclude the URL for your virtual directory from the Windows SharePoint Services managed paths. Alternatively, if you have not configured a top-level Windows SharePoint Services site on the root of the IIS Web site, you may remove the root as a managed path.
To configure Managed Paths in Windows SharePoint Services
For information about how to configure managed paths from the command line, see the topic "Managing Paths" in Microsoft Windows SharePoint Services Administrator's Guide at http://go.microsoft.com/fwlink/?LinkId=18110.
BizTalk Server 2004 requires the following versions of the Microsoft® XML Parser (MSXML) installed in this order:
In addition to the software listed up to this point, the following software should be installed:
Note You must install Knowledge Base Article 838166 on the computer(s) on which you install SQL Server 2000 and it must be applied after SQL Server 2000 Service Pack 3a.
If you plan on configuring Business Activity Services (BAS), the minimum software requirement includes:
To perform a successful installation of Microsoft® BizTalk® Server 2004, ensure you meet the prerequisite hardware, software, and security requirements mentioned earlier in this document.
This section contains:
A complete installation of BizTalk Server requires Windows Server™ 2003, Windows® 2000 Server or Windows XP in combination with Microsoft® SQL Server™, Visual Studio® .NET, Windows SharePoint® Services, and various Windows Components.
Caution Close all other programs before installing BizTalk Server.
Caution During the installation process, IISAdmin (along with its dependent services) stops and restarts. The computer may also shut down and restart.
To perform a complete installation of BizTalk Server
If the BizTalk Server Setup page does not appear, double-click setup.exe located in the root of the installation CD.
Note If you are installing Windows Small Business Server 2003, Premium Edition, double-click SetupforSBSPremium.vbs instead of setup.exe.
Important During the installation process the Windows Management service is stopped and restarted.
International The installation path must not contain characters outside of the following sets: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only installation paths that contain the characters in this set are supported.
Note If you do not install all the prerequisite software, BizTalk Server does not install some components.
The Configuration Wizard appears.
Important Review the configuration documentation before configuring BizTalk Server. For information about configuring BizTalk Server, see "BizTalk Server Configuration" in the Deployment section of the BizTalk Server Help.
Important It is highly recommended that you review the BizTalk Server 2004 Readme SP1 before installation. To ensure you are reading the most up-to-date information, download the latest version of BizTalk Server 2004 Readme SP1, from http://go.microsoft.com/fwlink/?linkid=39416.
For a list of the fixes in BizTalk Server 2004, Service Pack 1, see http://go.microsoft.com/fwlink/?linkid=39415.
The following section details how to perform a custom installation on 4 separate computers.
To set up a distributed BizTalk Server (multiple computer) environment
Note If you plan to develop a Human Workflow Services (HWS) Web Service fact retriever for custom installations on each HWS Web Service and Administration Tools-only computer, install and store the fact retriever in the Global Assembly Cache (GAC). For information about HWS fact retrievers, see "Installing, Editing and Removing Fact Retrievers" in the Operations section of the BizTalk Server Help."
Caution During the installation process, IISAdmin along with its dependent services stops and restarts. ENTSSO, RuleEngineUpdateService, and EDI Subsystem NT services will also be stopped and restarted if SSO, Rule Engine, and EDI are installed.
The following table indicates the dependencies that you must install or update before installing BizTalk Server based on the features you select.
| Feature | Windows SharePoint Services | MDAC 2.8 | .NET Framework 1.1 | VS .NET 2003 | MSXML 4.0 SP2 | IE6 SP1 | SQL Client Tools | SQLXML 3 SP2 | OWC10 |
|---|---|---|---|---|---|---|---|---|---|
| Documents | X | ||||||||
| Development | X | X | X | X | |||||
SDK |
X | X | X | X | |||||
| Runtime Components | |||||||||
Engine |
X | X | X | X | X* | X | |||
| HWS Runtime Components |
X | X | X | X | |||||
| Base EDI Adapter |
X | X | X | X | |||||
Rule Engine |
X | X | X | X | |||||
Enterprise Single Sign-On |
X | X | |||||||
| Admin and Monitoring | |||||||||
Admin Tools |
X | X | X | X | X* | X | |||
| HWS Admin |
X | X | X | X | |||||
Enterprise Single Sign-On Admin |
X | X | |||||||
| Information Worker Application/Portal | |||||||||
BAS |
X | X | X | X | X | ||||
Human Workflow Web Service |
X | X | X | X |
Note *If you use Business Activity Monitoring (BAM) on the client computer, ensure that you install SQL Server Client Tools.
In the custom installation Summary page, you have the option of selecting either Enterprise Single Sign-On Services (SSO), or the Engine, or both from the Runtime components.
In the custom installation Summary page, you have the option of selecting the SSO Administration feature.
Note If you have BizTalk Server Runtime, Development, or Administration features installed, you must first remove those features before you are able to uninstall the SSO Runtime or Administration components.
Important When performing a custom installation that only includes the Development option, two computers are required. You must perform a complete installation and configuration on the first computer, create a new BizTalk Group, and then, on a separate computer, perform a custom installation for Development only. During the Development-only installation, join the existing BizTalk group and specify the SQL Server where you created your group.
There are four HWS components:
To install HWS using multiple computer systems, you can install the Runtime components, Administration Tools and Web Service component of HWS on separate stand-alone computers. The Development\SDK is not required.
To install HWS Runtime components, use the Create option in the Configuration Wizard that creates the databases, BizTalkHWSDb and BizTalkMgmtDb. BizTalk Server does not support adding HWS Runtime components using the Join option if there is no existing database BizTalkHWSDb.
To configure HWS using multiple computer systems, you must configure the HWS Runtime components first.
Important You must install HWS Runtime components on a computer running Internet Information Services (IIS). Without IIS installed, HWS can only run HWS actions and cannot act as an HTTP receive location.
In order for the HWS Web service to work on a computer running a Windows Server 2003 domain controller, the following permissions are required:
In order for HWS Web service to work on a computer running a Windows 2000 Server domain controller, the following permissions are required.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\Hws\WebService\Identity\ASPNET_SETREG
If you install Windows 2000 Server Service Pack 4:
For more information about default permissions and user rights for IIS 6.0, see "Knowledge Base Article 812614: INFO: Default Permissions and User Rights for IIS 6.0" available at http://go.microsoft.com/fwlink/?LinkId=24982.
To install Business Activity Services (BAS) without Active Directory or with BAS Microsoft Message Queue Server (MSMQ) signing turned off, the DisableBasMsmqSigning switch in the HKLM\Software\Microsoft\BizTalk Server\3.0\TPM registry path must have a value of 1. You should set this switch after installing BizTalk Server but before running the Configuration Wizard.
If you have already installed BizTalk Server and need to disable BAS MSMQ signing, complete the following steps.
To disable BAS MSMQ Signing
If you have already installed BizTalk Server with BAS MSMQ disabled and need to enable BAS MSMQ signing, complete the following steps.
To enable BAS MSMQ Signing
To perform a custom installation of BizTalk Server on multiple computers
If the BizTalk Server Setup page does not appear, double-click setup.exe located in the root of the installation CD.
International The installation path must not contain characters outside of the following sets: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only installation paths that contain the characters in these sets are supported.
In a distributed environment (multiple computers), ensure all installations are complete on each computer before selecting the Configuration Wizard.
Under Runtime Components, select only Enterprise SSO.
Select only Enterprise Single Sign-On and clear all other components
Under Runtime Components, clear Enterprise Single Sign-On
Under Administration and Monitoring, clear all components
Under Runtime Components, select only Administration and Monitoring
After you have considered and selected all the options for each computer, click Install.
Important In a distributed environment (otherwise known as a multiple computer configuration), do not run the BizTalk Configuration Wizard until you install all the BizTalk Server software on the various computers. To complete the BizTalk Server configuration, you must install Microsoft SQL Server™ 2000 with Service Pack 3a on your computer or have it accessible remotely.
The Configuration Wizard appears.
Important Review the configuration documentation before you configure BizTalk Server. For information about configuring BizTalk Server, see "BizTalk Server Configuration" in the Deployment section of the BizTalk Server Documentation.
Important It is highly recommended that you review the BizTalk Server 2004 Readme SP1 before installation. To ensure you are reading the most up-to-date information, download the latest version of BizTalk Server 2004 Readme SP1, from http://go.microsoft.com/fwlink/?linkid=39416.
For a list of the fixes in BizTalk Server 2004, Service Pack 1, see http://go.microsoft.com/fwlink/?linkid=39415.
A silent installation is ideal for test scenarios or as part of a large-scale enterprise deployment. BizTalk Server provides command line parameters that you can use with setup.exe to perform a silent installation.
You can configure your BizTalk Server installation in silent mode in conjunction with setup.exe or as a separate procedure, only after using the Installation Wizard and Configuration Wizard to complete an initial installation and configuration. The initial configuration produces an XML file that is required for a silent configuration.
For more information about running the Configuration Wizard in silent mode, see "Silent Configuration" in BizTalk Server Help. To use the documentation after you install BizTalk Server, on the Start menu, point to Programs, point to BizTalk Server, and click BizTalk Server Documentation.
There are two different modes of silent installation. Both have their own required parameters and are mutually exclusive:
Note The following procedure will not configure BizTalk Server. For more information about running the Configuration Wizard in silent mode, see "Silent Configuration" in the BizTalk Server Help. To use the documentation after you install BizTalk Server, on the Start menu, point to Programs, point to BizTalk Server, and click BizTalk Server Documentation.
To perform a complete silent installation of BizTalk Server
Setup.exe /addlocal all /INSTALLDIR "c:\Program Files\Microsoft BizTalk Server" /l "c:\temp\BTSsetup.log" /InstallPlatform /AutologonPassword <password>
You must use the following command line options in conjunction with setup.exe:
Important Enterprise SSO Services and administration features are required. If you do not use /InstallPlatform to install Enterprise SSO Services and administration features, you must run the SSO.msi before you run setup.exe. The SSO Services is required for certain BizTalk Server features, including the Runtime Engine. For the silent installation scenario, you must install the SSO.msi beforehand using setup.exe.
The following parameters are optional:
International The installation path must not contain characters outside of the following set: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only installation paths that contain the characters in this set are supported.
Note In order to display additional options for command line installation, type setup.exe /? at the command prompt.
Note There should be no line break in the actual command line syntax.
Note Microsoft Windows Installer (MSI) command line options are not case-sensitive.
Note For more information about the MSI command line options, see Microsoft Windows Help.
To perform a custom installation of BizTalk Server from the command line, use setup.exe along with the configuration snapshot (XML file) generated during the initial configuration.
Important These command line parameters do not work unless you have already installed and configured BizTalk Server and saved the configuration XML file.
Note The following procedure will not configure BizTalk Server. For more information about running the Configuration Wizard in silent mode, see "Silent Configuration" in tBizTalk Server Help. To use the documentation after you install BizTalk Server, on the Start menu, point to Programs, point to BizTalk Server, and then click BizTalk Server Documentation.
To perform a custom silent installation of BizTalk Server
Setup.exe /s "c:\Config.xml" /INSTALLDIR "c:\Program Files\Microsoft BizTalk Server" /l "c:\temp\BTSsetup.log" /InstallPlatform /AutologonPassword <password>
Step 6 uses the following command line parameters:
Note In order to display additional options for command line installation, type setup.exe /? at the command prompt.
Note There should be no line break in the actual command line syntax.
Note Windows Installer (WMI) command line options are not case-sensitive.
Note For more information about the WMI command line options, see Microsoft Windows Help.
For more information about configuring BizTalk Server in silent mode, see "Silent Configuration" in BizTalk Server Help. To use the documentation after you install BizTalk Server, on the Start menu, point to Programs, point to BizTalk Server, and then click BizTalk Server Documentation.
When you install BizTalk Server, it adds to or changes the following files in folders other than the typical installation folders.
Caution If you uninstall BizTalk Server, BizTalk Server does not remove many of these files from your system automatically. You must remove them manually.
After installing BizTalk Server, it installs or updates the following files in the System folder (system32) to the latest version:
Use the Microsoft Windows Add/Remove Programs utility to remove Microsoft BizTalk Server.
Observe the following:
To remove BizTalk Server
Note Uninstalling BizTalk Server does not uninstall Enterprise Single Sign-On (SSO). Use Add/Remove Programs to uninstall it manually. You cannot uninstall SSO if you have a dependent BizTalk Server feature installed on the same computer.
Note After uninstalling BizTalk Server, SSO does not function even though it appears in Add/Remove Programs.
To remove Enterprise SSO Services
Note If you have BizTalk Server Runtime, Development, or Administration features installed, you are not able to uninstall the SSO Runtime or Administration components until all dependencies are removed.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows Server, BizTalk, FrontPage, InfoPath, SharePoint, Visual C#, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.