Professional Documents
Culture Documents
Installing and Configuring BizTalk Server 2006 R2 On Windows Server 2003
Installing and Configuring BizTalk Server 2006 R2 On Windows Server 2003
Copyright
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the companies, organizations, products, domain
names, e-mail addresses, logos, people, places, and events depicted in examples herein are
fictitious. 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.
2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, BizTalk, Excel,
SharePoint, Visio, Visual C#, and Visual Studio are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
Contents
Installing and Configuring BizTalk Server 2006 R2 on Windows Server 2003................................7
What's New and Changed in This Document..............................................................................7
Known Issues in the Installation of BizTalk Server 2006 R2 on Windows Server 2003...............8
BizTalk Server 2006 R2 Installation Guide Contains Incorrect Links to Redistributable CAB
Files................................................................................................................................... 8
BizTalk Server Installation Creates SQL Server Objects on the Primary Filegroup...............8
"Error when downloading BtsRedist.cab" when Downloading Simplified Chinese (CN)
CAB File............................................................................................................................ 9
Setup Fails When Attempting to Install SQLXML 3.0 SP3....................................................9
About the Installation Process..................................................................................................... 9
Overview.................................................................................................................................. 9
Hardware Requirements......................................................................................................... 11
Software Requirements.......................................................................................................... 13
BizTalk Server 2006 R2 Features and Components..............................................................17
BizTalk Server 2006 R2 Feature Dependency Matrix.........................................................20
Deploying BizTalk Server 2006 R2 on Windows Server 2003...................................................21
Considerations for 64-Bit Windows Server 2003 Editions...................................................21
Windows Groups and Accounts.......................................................................................... 22
Localized Versions and Cross-Language Support..............................................................22
Using SQL Server with BizTalk Server 2006 R2.....................................................................22
Supported SQL Server Topologies for Windows Server 2003 Editions............................23
Using SQL Server Named Instances...............................................................................23
Supported SQL Server Collations....................................................................................23
List of Databases Used in BizTalk Server 2006...............................................................23
Considerations for Installing Windows SharePoint Services...............................................24
Considerations for Installing Commerce Server 2007 on the Same Computer...................25
Considerations for Installing BizTalk Server on Domain Controllers...................................26
Performing an Administration Tools-Only Installation.............................................................26
Performing a Complete Installation............................................................................................27
Task 1: Install the Operating System......................................................................................27
Step 1: Install Windows Server 2003..................................................................................27
Step 2: Install Windows Server 2003 Service Pack 2.........................................................28
Step 3: Apply Windows Server 2003 Updates....................................................................28
Task 2: Install Software Prerequisites....................................................................................29
Step 1: Install Internet Information Services 6.0.................................................................29
Step 2: Install Office Excel and Office InfoPath...................................................................30
Step 3: Install Visual Studio 2005.......................................................................................31
Step 4: Install SQL Server 2005 or SQL Server 2000.........................................................32
Step 5: Install Windows SharePoint Services.....................................................................35
Copyright................................................................................................................................... 75
Overview
The basic installation process for BizTalk Server 2006 R2 is the same as for most Windowsbased applications. The BizTalk Server Setup program calls Windows Installer to install BizTalk
Server 2006 R2 and the related components. Setup coordinates the installation process from
beginning to end, terminating when the last component is installed. If you do not have a
component, Setup is able to install prerequisites from the Web or from a previously downloaded
CAB file.
The following table provides a brief overview of the steps needed to install BizTalk Server,
assuming that you are beginning with a new computer that does not have an operating system
installed.
Step/Task
Notes
Step/Task
Notes
given time.
For information about installing BizTalk RFID, see Installing and Configuring BizTalk RFID at
http://go.microsoft.com/fwlink/?linkid=81041.
For the download locations of the CAB files, see Redistributable Cab Files.
Hardware Requirements
The following table shows the minimum hardware requirements for a BizTalk Server 2006 R2
installation. Achieving acceptable performance in a production environment will generally dictate
greater hardware requirements for your servers. The minimum computer configuration is suitable
for development and testing purposes.
Component
Minimum Requirement
Component
Minimum Requirement
Hard disk
Component
Minimum Requirement
Display
Other
Software Requirements
BizTalk Server relies on a broad base of prerequisite software to provide the services necessary
for a BizTalk Server application to function. The following table is a complete list of the
prerequisite software you may be required install on the server that will run BizTalk Server 2006
R2. Not all of these prerequisites will be required for every installation. Exactly what software
must be installed depends on which BizTalk Server features you decide to implement. For more
information, see the BizTalk Server 2006 R2 Feature Dependency Matrix.
Product
Description
Operating system. BizTalk Server supports 64bit Windows on x64-based systems; Itaniumbased systems are not supported.
Product
Description
features:
HTTP adapter
SOAP adapter
Product
Description
Product
Description
ADOMD.NET 8.0
ADOMD.NET 9.0
16
Description
Documentation
Server Runtime
Windows Communication
Framework (WCF) Adapter Runtime
Component
Description
Additional Software
Component
Description
http://go.microsoft.com/fwlink/?LinkId=67694
(32-bit) or http://go.microsoft.com/fwlink/?
linkid=88352 (64-bit), "Microsoft
Management Console 3.0 for Windows
Server 2003."
BAM Client
19
Note
.NET Framework 1.1 is required when you install SQL Server Notification Services 2.0
with Service Pack 1 and for Windows SharePoint Services 2.0 with Service Pack 2.
Note
.NET Framework 3.0 is required only if you install the WCF adapter or WCF Admin Tools,
or if you install Windows SharePoint Services 3.0.
Note
You only need to install IBM WebSphere MQ 5.3 with CSD 10 or IBM WebSphere MQ 6.0
for MQSeries Agent. If you install the MQSeries Agent you must also install the .NET
20
Framework 2.0, however, this requirement is not enforced by the SQL Server setup
program.
High availability cannot be assured; fault tolerance is limited to data protection and disaster
recovery. For more information about disaster recovery and backup procedures for BizTalk
Server, see "Backing Up and Restoring BizTalk Server" at http://go.microsoft.com/fwlink/?
linkid=105772.
Security is complicated by the concentration of services and data on one computer. For more
information about security in BizTalk Server, see "Planning for Security" at
http://go.microsoft.com/fwlink/?linkid=110436.
The system may be difficult to scale. For more information about scaling BizTalk Server
solutions, see "Scaling Your Solutions" at http://go.microsoft.com/fwlink/?linkid=110437.
Running host instances in native 64-bit mode is only supported on BizTalk Server 2006 R2
Enterprise Edition, Developer Edition, Branch Edition, and Evaluation Edition.
BizTalk Server cannot be run on Itanium-based Windows editions; however, BizTalk Server
can make use of SQL Server databases hosted on an Itanium-based system.
There is no unique installation application for the 64-bit platform. During installation the Setup
Wizard (setup.exe) will determine which platform (32-bit or 64-bit) it is running on, and then
install the appropriate version of the BizTalk Server executables. The Setup Wizard itself is a
32-bit application.
There are separate setup programs for 32-bit and 64-bit Enterprise Single Sign-On (SSO).
The Setup Wizard will automatically invoke the correct SSO installation package; however, if
it becomes necessary to install SSO directly from its installation package you must be sure to
choose the correct setup version. The SSO subfolder contains the 32-bit installation package.
The SSO64 folder contains the 64-bit installation package.
If you have installed BizTalk Server 2006 R2 on the 64-bit edition of SQL Server 2005, the
default server name will not be populated in the custom configuration manager unless the
SQL Server Browser service is started before running configuration. For more information,
see "SQL Server Browser Service" in SQL Server 2005 Books Online at
http://go.microsoft.com/fwlink/?linkid=110458.
You can configure host instances to run in either 32-bit or 64-bit mode by using the 32-bitonly check box option in the Host Properties dialog box in the BizTalk Server Administration
console. By default, host instances are created to run in 32-bit mode.
Business Activity Services (BAS) requires the 32-bit editions of Microsoft Internet Explorer 6
or Windows Internet Explorer 7.
If you are installing the BAM portal, you must configure ASP.NET 2.0 to run in 32-bit mode.
For more information about running BizTalk Server on 64-bit Windows Server 2003 editions, see
"BizTalk Server 64-Bit Support" in the Performance and Capacity Planning section of BizTalk
Server 2006 R2 Help.
32-bit Windows Server 2003 with 32-bit SQL Server 2005 or 32-bit SQL Server 2000
64-bit Windows Server x64 Editions with 32-bit SQL Server 2005 or 32-bit SQL Server 2000
64-bit Windows Server x64 Editions with 64-bit SQL Server 2005 or 64-bit SQL Server 2000
Itanium-based systems are not supported for single-server installations. BizTalk Server will
not run on Itanium-based systems. (Itanium-based systems can be used in a multiple server
configuration, with SQL Server installed on the Itanium system.)
Local installations of SQL Server 2000 and SQL Server 2005 at the same time are not
supported.
The SQL Server Express editions are not recommended for production use because the SQL
Server Agent Service is not included with the Express editions.
If you do not intend to install any of these features, you do not need to install WSS.
23
BizTalk Server 2006 R2 supports Windows SharePoint Services 2.0 SP2 and Windows
SharePoint Services 3.0, or Windows SharePoint Services 2.0 and Microsoft Office SharePoint
Server 2007 (MOSS). Not all BizTalk Server features are compatible with all versions of Windows
SharePoint Services.
Windows SharePoint Services support in BizTalk Server 2006 R2 is summarized in the following
table:
Windows SharePoint Services
WSS adapter
BAS
32-bit only
32-bit only
Not supported
version
Windows SharePoint
Services 2.0 SP2
Support for 64-bit systems is
provided by WOW64. IIS and
ASP.NET must run in 32-bit
mode.
Windows SharePoint
Services 3.0 or Microsoft Office
SharePoint Server 2007
WSS 3.0 and MOSS require IIS
and ASP.NET to run in 64-bit
mode on 64-bit Windows
editions.
If you plan a side-by-side installation of WSS 2.0 and WSS 3.0, we recommend (but dont
require) that you install WSS 3.0 before WSS 2.0. If WSS 3.0 is installed after WSS 2.0, the
WSS 3.0 Setup Wizard automatically attempts to upgrade the existing WSS 2.0 installation.
Installing WSS 3.0 first will avoid this problem, although you can manually choose not to
perform an upgrade when the WSS 3.0 Setup Wizard runs.
The Windows SharePoint Services (both WSS 2.0 and WSS 3.0) installation type must be
Server Farm. This is true even if you are performing a single-server installation of BizTalk
Server 2006 R2. The Server Farm type of installation allows you to configure WSS to use the
databases you specify.
WSS 3.0 requires Microsoft .NET Framework 3.0. The .NET Framework must be installed
prior to installing Windows SharePoint Services 3.0.
On 64-bit Windows, both IIS and ASP.NET must be configured to run in 64-bit mode before
installing WSS 3.0.
24
On 64-bit Windows, both IIS and ASP.NET must be configured to run in 32-bit mode before
installing WSS 2.0.
Although side-by-side installation of WSS 2.0 and WSS 3.0 is supported on 64-bit Windows,
side-by-side execution is not supported. WSS 2.0 requires IIS and ASP.NET to run in 32-bit
mode on 64-bit Windows, however, WSS 3.0 requires IIS and ASP.NET to run in 64-bit mode.
IIS can only run in one mode, 32-bit or 64-bit, at any given time on 64-bit Windows. This
prevents side-by-side execution of WSS 2.0 and WSS 3.0.
In general this is not a serious constraint, but there are exceptions. For example, if you want
to run BAM or BAS in conjunction with the Windows SharePoint Services adapter, you will
have to configure the adapter to use WSS 2.0.
Side-by-side installation and side-by-side execution of WSS 2.0 and WSS 3.0 is supported on
Windows 32-bit x86 editions. This means that it is possible to configure the WSS adapter
Web service to use WSS 3.0, and simultaneously host the BAS Web site using WSS 2.0. This
configuration is only possible on Windows 32-bit x86 editions.
The Windows SharePoint Services adapter supports Windows SharePoint Services 2.0 SP2
(32-bit only), Windows SharePoint Services 3.0 (32-bit on x86 systems; 64-bit on x64
systems with 64-bit Windows installed), or Microsoft Office SharePoint Server 2007. The
WSS adapter can be configured to use only one version of WSS or MOSS at a given time.
BAS does not support WSS 3.0 or MOSS. BAS requires WSS 2.0 SP2.
For more information about the versions of Windows SharePoint Services that are supported for
use with BizTalk Server 2006 R2, see the BizTalk Server online Help topic Windows SharePoint
Services Support in BizTalk Server 2006 R2.
25
SQL Server Agent must be running on all computers that are hosting BizTalk Server
MessageBox databases. This is required if you want to track message bodies in the BizTalk
Server Messaging engine. The SQL Server Agent also runs maintenance jobs that are critical
to the proper function of your BizTalk Server system.
To use HAT, you must have the read permissions to access the SQL Server, Analysis Server,
and the IIS virtual directory. For information about how to use the BizTalk Server
Administration console and HAT, see "Monitoring BizTalk Server" at
http://go.microsoft.com/fwlink/?linkid=110457.
When you run the BizTalk Server Configuration Wizard, you must create an Analysis Server
database.
To create an Administration Tools-only installation
1. During the installation of BizTalk Server, select Administration Tools in the component
selection screen without selecting any other components and complete the Installation
Wizard.
2. After the installation is complete, launch the custom configuration manager and join an
existing SSO system and BizTalk Group.
a known state, you should start with a fresh installation of Windows Server 2003. Additional
software, if any, should be kept to a minimum.
Ensure that your server has all necessary security and software updates installed by visiting
the Microsoft Update site before installing software prerequisites, and periodically check for
additional updates as installation progresses. In general, you should install all high-priority
updates, and optional updates, as appropriate.
Real-time antivirus scanning software should be disabled during BizTalk Server installation.
Antivirus software may block certain configuration changes that are necessary for the proper
operation of your BizTalk Server.
After installing Windows Server 2003, you must log on as an administrator in order to install
additional software.
Installation of BizTalk Server 2006 R2 into a domain is only supported on an Active Directory
domain environment that is running in Windows 2000 native mode or later. You cannot install
into a mixed-mode domain (i.e., one that supports NT 4.0 clients).
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.
Windows Firewall is on by default only during new installations of Windows Server 2003.
Windows Firewall provides network protection while users update their system with the latest
updates using the new Post-Setup Security Updates feature. As soon as the updates are
finished, the firewall is turned off unless it was explicitly enabled. If a server running Windows
Server 2003 is updated or upgraded to Service Pack 1 or Service Pack 2 the firewall is off by
default and the Post Setup Security Updates feature is not used. For more information about
using Windows Firewall with Windows Server 2003, see "Windows Server 2003 Windows
Firewall (WF)" at http://go.microsoft.com/fwlink/?linkid=67902.
27
includes Service Pack 1, or if you are using Windows Server 2003 R2. Even so, we recommend
that you install Service Pack 2 to obtain the latest software updates and security improvements.
To learn more about Windows Server 2003 Service Pack 2, see "Windows Server 2003 Service
Pack 2 Technical Library" http://go.microsoft.com/fwlink/?LinkId=86804.
The Windows Server 2003 Service Pack 2 and installation procedure is available for download at
the following locations:
Windows Server 2003 Service Pack 2 can also be obtained from Microsoft Update.
28
Microsoft Office Excel 2007 and Office InfoPath 2007, or Office Excel 2003 and
InfoPath 2003 with Office 2003 Service Pack 2. Office Excel is required for BAM. Office
InfoPath is required for BAS.
SQL Server 2005 with Service Pack 2 or SQL Server 2000 with Service Pack 4 (SQL
Server 2005 is recommended)
If SQL Server 2000 is installed, then the following services are necessary
HTTP adapter
SOAP adapter
29
Analysis Services
Notification Services
32
Integration Services
Note
Using BizTalk Tracking database with SQL Server 2005 Analysis Services is not
supported.
Note
The Reporting Services component is optional.
Note
SQL Server Management Tools is required to configure BAM. Management Tools
are installed by default if the Workstation components, Books Online and
development tools option is selected, however, if you perform as advanced
setup you will need to ensure that Management Tools is installed. Management
Tools is located under the Client Components section in the SQL Server Setup
Wizard Feature Selection page.
33
SQL Server 2005 Service Pack 2 is required for BizTalk Server 2006 R2. In this procedure you
will update your SQL Server 2005 installation by applying SQL Server 2005 Service Pack 2.
Note
You do not need to perform this step if you installed a version of SQL Server 2005 that
includes Service Pack 2.
To install SQL Server 2005 Service Pack 2
1. Browse to http://go.microsoft.com/fwlink/?linkid=86436 to download the appropriate
service pack for your computer. For Windows x64 editions, download and save
SQLServer2005SP2-KB921896-x64-ENU.exe to your local hard drive. For 32-bit
Windows editions, download and save SQLServer2005SP2-KB921896-x86-ENU.exe to
your local hard drive.
2. Locate the file you just downloaded and double-click it to run Setup. The Microsoft SQL
Server 2005 Service Pack 2 Setup screen will appear. Click Next.
3. Review the license terms, select I accept the agreement, then click Next.
4. On the Feature Selection screen, click Next.
5. On the Authentication screen, verify that the authentication method is set to Windows
Authentication, and then click Next.
6. On the Error and Usage Reporting Settings screen, you can leave the defaults or
choose to send error and feature usage data, and then click Next.
7. The Running Processes screen will appear. Running processes that have locked files
that need to be updated will be displayed here. Listed processes, if any, should be shut
down using the Services management tool. When there are no running processes
remaining in the list, click Next.
8. The Ready to Install screen will appear. Click Install.
34
In the following procedures, you will install WSS 3.0 before installing WSS 2.0 SP2. If WSS 3.0 is
installed after WSS 2.0, the WSS 3.0 Setup Wizard will automatically attempt to upgrade the
existing WSS 2.0 installation. Installing WSS 3.0 first will avoid this problem.
Configure ASP.NET 2.0 to Run In 64-Bit Mode On 64-Bit Windows Editions
The following procedure only applies to the 64-bit Windows editions. You must configure IIS and
ASP.NET 2.0 to run in 64-bit mode before installing WSS 3.0. You do not have to perform this
step if you do not plan to install WSS 3.0.
To configure ASP.NET 2.0 for 64-bit mode
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 64-bit mode:
cscript %Systemdrive%\inetpub\adminscripts\adsutil.vbs SET
W3SVC/AppPools/Enable32bitAppOnWin64 0
3. Type the following command to install the version of ASP.NET 2.0 (64-bit) and to install
the script maps at the IIS root and under:
%Systemroot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i -enable
Note
Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the
Web service extension list in Internet Information Services Manager.
Install Windows SharePoint Services 3.0
In the following procedure you install Windows SharePoint Services 3.0.
To install Windows SharePoint Services 3.0
1. Windows SharePoint Services 3.0 requires Microsoft .NET Framework 3.0, which must
be installed before beginning installation of Windows SharePoint Services 3.0. The .NET
Framework is available for download at http://go.microsoft.com/fwlink/?linkid=75053.
Note
The default .NET Framework 3.0 download requires that the installation computer
is connected to the Internet during the setup process. This requirement may be
avoided by downloading and installing the full redistributable package for .NET
Framework 3.0. The full redistributable package for 32-bit systems is available at
http://go.microsoft.com/fwlink/?linkid=70848. The full redistributable package for
64-bit (x64) systems is available at http://go.microsoft.com/fwlink/?linkid=70849.
2. Browse to http://go.microsoft.com/fwlink/?linkid=77800 (32-bit x86) or
http://go.microsoft.com/fwlink/?linkid=95019 (64-bit x64). Download the installation
package to a location on your hard disk.
35
3. Locate the package you just downloaded (SharePoint.exe), and then double-click the
package to start the setup.
4. On the End User License Agreement screen, select I accept the terms in the License
Agreement. On this screen and several others that follow, the setup wizard will
automatically move to the next screen when you have made your selection.
5. Under Type of installation, choose the Advanced button.
Note
If Windows SharePoint Services 2.0 is already installed, the Windows SharePoint
Services 3.0 setup will display an Upgrade earlier versions tab. If you would
like to perform a side-by-side installation of Windows SharePoint Services 3.0
with Windows SharePoint Services 2.0, chose the option for No, do not run
upgrade at this time, then continue with the setup procedure as documented
below.
Important
Do not upgrade a Windows SharePoint Services 2.0 installation until you have
reviewed Considerations for Installing Windows SharePoint Services. Some
BizTalk Server features are not compatible with Windows SharePoint Services
3.0 or Microsoft Office SharePoint Server 2007.
6. On the Server Type tab, select Web Front End, then click Install Now.
7. When installation is completed, clear the check box for Run the SharePoint products
and technologies Configuration Wizard, and then click Close. You will not configure
anything at this time.
Configure ASP.NET 2.0 to Run In 32-Bit Mode On 64-Bit Windows Editions
The following procedure only applies to the 64-bit Windows editions. You must configure IIS and
ASP.NET 2.0 to run in 32-bit mode before installing WSS 2.0 SP2.
To Configure ASP.NET 2.0 for 32-bit mode
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 32-bit mode:
cscript %Systemdrive%\inetpub\adminscripts\adsutil.vbs SET
W3SVC/AppPools/Enable32bitAppOnWin64 1
3. Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install
the script maps at the IIS root and under:
%Systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i -enable
Note
Make sure that the status of ASP.NET version 2.0.50727 (32-bit) is set to
36
37
under.
The account you specify must be in the format of DomainName\UserName
orServerName\UserName if you are using a local account. If when you attempt to save
the configuration settings you receive System Error 1057 while trying to query SPTimer
it is a cryptic indication that you did not correctly format the account as described above.
If you encounter Error 18456, see http://go.microsoft.com/fwlink/?LinkId=61924 for
instructions to resolve the error.
Note
When using binary collation with SQL Server, the domain or server name you
specify in the SharePoint Admin Application Pool account must be in uppercase
letters.
6. In the Password field, type the account password, and then confirm the password.
7. Under Security Configuration, select NTLM, and then click OK.
Note
Kerberos authentication is not supported with Business Activity Services.
8. The Application Pool Changed page loads and tells you that you must restart IIS.
9. Click Start, click Run, type IISRESET, and then click OK.
10. On the Application Pool Changed page, click OK. The Configuration Database page
loads.
11. Under Configuration Database, in the Database server field, type the name of your
SQL Server.
12. In the SQL Server database name field, type WSSDB.
13. Leave the rest of the default values, and then click OK. This creates the configuration
database and you are redirected to the Central Administration Homepage.
Ensure that you have installed all BizTalk Server software prerequisites necessary for the
type of installation you want to perform.
Your computer name should not exceed 15 characters for the BizTalk Server configuration to
work properly.
Avoid changing the computer name after configuration. If the computer name is changed, the
BizTalk Server configuration will not work. Recovery entails restoring the computer name or
removing and reinstalling BizTalk Server.
The account you are logged on as must be part of the local administrators group and have
DBA rights on SQL Server. After configuration is complete, you can lower the privileges to
DBO.
Both BizTalk Server 2006 R2 Setup and Windows Installer generate log files during the
installation process. By default, Setup creates log files in the %Temp% folder. The log files consist
of one .htm summary file that is generated each time Setup is executed, one detailed .log file
generated by MSI, and one .log file for configuration.
BizTalk Server 2006 R2 writes event messages to the Windows application log. The Windows
application log collects information about events that are generated by the applications running
41
on the local system. You can use the Event Viewer to view the log file and to filter the messages it
contains.
If the application event log runs out of space during BizTalk Server setup, the installation will fail.
To avoid this problem you should ensure that the application log has sufficient space available
before running setup. The amount of space required in the application log varies depending on
the BizTalk Server features installed during setup. You can clear the log events before running
setup, or change the event log properties to provide more space or to allow the event logging
system to overwrite old event log entries.
For more information about the Windows application log or Event Viewer, see the Windows
product documentation.
If you plan to use a redistributable CAB file, we recommend that you download
the CAB file to a network share. During the installation, the BizTalk Server 2006
R2 installation disk needs to remain in the CD drive from which you are installing
BizTalk Server.
4. On the Summary page, verify that the components that you select to install are correct.
5. Click Install to start the installation process.
Note
During the installation of the BizTalk Server Web services, the Visual Studio 2005
Choose your default environment settings dialog box may appear. To close
this dialog box and continue the installation of BizTalk Server 2006 R2, click Exit
Visual Studio.
6. On the Installation Completed page, verify that the Launch BizTalk Server
Configuration check box is selected, and then click Finish. This starts the Configuration
Wizard.
You should create the service account under which the BizTalk Server service in-process host
will run before starting configuration. You will be prompted to enter the account name and
password during configuration. For more information, see the section.
The account you are logged on as must be part of the local administrators group and have
System Administrator rights on SQL Server.
During Basic Configuration, the user who is running the configuration tool will be the BAS site
owner.
Configuration fails if the event log is full. You need to make sure that the event log is not full
during the configuration.
Configuration is selected.
2. Under Database, ensure that you enter the name of the computer where SQL Server is
installed. SQL Server must be installed on the local computer for basic configuration.
3. Under Service Credential, in the User name text box, type the user name for the
account that the BizTalk services will run under.
Note
In a Basic Configuration, all BizTalk services will run under this account. The
configuration process grants this account the necessary security permissions on
the server and objects in SQL Server.
4. Under Service Credential, in the Password text box, type the password for the account
you specified, and then click Configure.
Note
You may receive a warning if you enter a user name with administrative
credentials on this computer. Click OK to continue.
5. On the Summary page, review the configuration about to be performed and make sure
all features are validated, and then click Configure.
6. On the Completion page, click Finish.
Note
If you have an anti-spyware software package installed, you may see a security level
warning during the configuration of the BAS site.
Post-Installation Requirements
After you install BizTalk Server 2006 R2, you must follow these post-installation steps in the order
listed:
If you installed the Windows SharePoint Services adapter, you must add the BizTalk Service
account to the SharePoint Enabled Hosts Windows group on that server.
If you installed Human Workflow Services, you will need to add the HWS Web Service user to
the IIS_WPG and STS_WPG Windows groups.
Ensure that TCP/IP and named pipes are enabled in the Microsoft SQL Server 2000 Client
Network Utility or the SQL Server 2005 Configuration Manager.
Download and install BizTalk Server 2006 Best Practices Analyzer from
http://go.microsoft.com/fwlink/?LinkId=83317. The BizTalk Server 2006 Best Practices
Analyzer examines a BizTalk Server 2006 R2 deployment and generates a list of best
practices issues it discovers. The Best Practices Analyzer performs configuration-level
verification, by reading and reporting only, and uses the gathered data to determine whether
best practices are being followed.
2. To start the silent installation, at the command prompt, type setup.exe /<command
name> <options>, and then press ENTER.
The following table shows the Windows Server 2003 command-line options that you use to install
BizTalk Server 2006 R2.
Command name
Option
Description
/HELP, or /?, or /H
/QUIET
Performs an installation
without a user interface. You
cannot cancel the installation.
Note
All messages are
entered into the setup
log file.
Note
The Quiet flag cannot
be specified for an
upgrade.
/CABPATH
/S
/PASSIVE
Performs a passive
installation. The setup program
only displays the progress bar.
/NORESTART
/FORCERESTART
Command name
Option
Description
/X or /UNINSTALL
/L
<Logfile> [i][w][e][a][r][u][c][m]
[p][v][*]
/IGNOREDEPENDENCIES
/COMPANYNAME
<Company name>
/USERNAME
<User name>
/PRODUCT
/ADDLOCAL ALL
/REMOVE ALL
47
Command name
Option
/REPAIR ALL
Description
Do not remove BizTalk Server prerequisites before you remove BizTalk Server. They must be
present for the process to complete successfully.
If assemblies stored in the global assembly cache (GAC) are in use when you uninstall
BizTalk Server, you cannot remove them completely. To ensure that you remove all
assemblies, stop all host instances from running and stop Internet Information Services (IIS)
before you uninstall BizTalk Server.
The BizTalk Server uninstall process does not remove the maps and schemas that have been
created in Visual Studio 2005 or the BizTalk Server databases.
Uninstalling BizTalk Server does not uninstall Enterprise Single Sign-On (SSO). Use
Add/Remove Programs to uninstall SSO manually. You cannot uninstall SSO if you have a
dependent BizTalk Server feature installed on the same computer.
If you have other applications using SSO, you must reconfigure SSO. If SSO is configured on
the master secret server, you will need to back up the master secret before uninstalling
BizTalk Server 2006 R2 and then restore it after SSO has been reconfigured.
If you choose to delete the Windows groups created during an installation and configuration
of BizTalk Server, you must revoke the rights from the SQL Server database by deleting it
from SQL Server Security. If you do not do this, the next configuration of BizTalk Server 2006
R2 will fail.
2. In the Add/Remove Programs dialog box, click Microsoft BizTalk Server 2006, and
then click Change/Remove.
3. On the Program Maintenance screen, select Remove, and then click Next.
4. On the Summary screen, review the components to be uninstalled, and then click
Uninstall.
5. On the Uninstall Completed screen, click Finish.
In the following procedure you uninstall the Microsoft Enterprise Single Sign-On Services.
To uninstall Enterprise SSO services
1. Click Start, point to Control Panel, and then click Add/Remove Programs.
2. In the Add/Remove Programs dialog box, click Microsoft Enterprise Single Sign-On,
and then click Change/Remove.
3. On the Program Maintenance screen, select Remove, and then click Next.
4. On the Summary screen, review the components to be uninstalled, and then click
Uninstall.
5. On the Uninstall Completed screen, click Finish.
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.
To remove BAM Alerts Notification Services instance on SQL Server 2000 Notification
Services
1. Click Start, point to All Programs, point to Microsoft SQL Server Notification
Services 2.0 SP1, and then click Notification Services Command Prompt.
2. Type the following command to disable the instance: nscontrol disable -name
BAMAlerts.
3. Type the following command to stop the instance: net stop NS$BAMAlerts.
4. Type the following command to unregister the instance: nscontrol unregister -name
BAMAlerts.
Note
The BAM Notification name is generated as NS$<Prefix for Alerts Database
Name> where <Prefix for Alerts Database Name> is what you specified on the
BAM Alerts configuration page. The default name is BAMAlerts.
CleanupBTFExpiredEntriesJob_BizTalkMgmtDb
MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb
MessageBox_Parts_Cleanup_BizTalkMsgBoxDb
MessageBox_UpdateStats_BizTalkMsgBoxDb
Operations_OperateOnInstances_OnMaster_BizTalkMsgBoxDb
PurgeSubscriptionsJob_BizTalkMsgBoxDb
Rules_Database_Cleanup_BizTalkRuleEngineDb
TrackedMessages_Copy_BizTalkMsgBoxDb
Note
50
If you deployed BAM, you may also need to remove the job named bam_<Cube
Name>_<View Name>.
To remove SQL Server agent jobs on SQL Server 2000
1. Click Start, point to All Programs, point to Microsoft SQL Server, point to Enterprise
Manager, and then click Enterprise Manager.
2. In Enterprise Manager, expand SQL Server Group, expand (local), expand
Management and expand SQL Server Agent. Click Jobs.
3. Remove the following jobs:
CleanupBTFExpiredEntriesJob_BizTalkMgmtDb
MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb
MessageBox_Parts_Cleanup_BizTalkMsgBoxDb
MessageBox_UpdateStats_BizTalkMsgBoxDb
Operations_OperateOnInstances_OnMaster_BizTalkMsgBoxDb
PurgeSubscriptionsJob_BizTalkMsgBoxDb
Rules_Database_Cleanup_BizTalkRuleEngineDb
TrackedMessages_Copy_BizTalkMsgBoxDb
Note
If you deployed BAM, you may also need to remove the job named bam_<Cube
Name>_<View Name>.
BAM_AN_<Cube Name>
BAM_DM_<View Name>
BAM_AN_<Cube Name>
BAM_DM_<View Name>
BAMAlertsApplication
BAMAlertsNSMain
BAMArchive
BAMPrimaryImport
BAMStarSchema
BizTalkDTADb
BizTalkEDIDb
BizTalkHwsDb
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
SSODB
Note
If you configured the server using Custom configuration and modified the
database names, you will need to remove those databases.
52
BAMAlertsApplication
BAMAlertsNSMain
BAMArchive
BAMPrimaryImport
BAMStarSchema
BizTalkDTADb
BizTalkEDIDb
BizTalkHWSDb
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
SSODB
Note
If you configured the server using Custom configuration and modified the
database names, you will need to remove those databases.
BizTalkAnalysisDB
53
BAMAnalysis
Technical Appendices
This section covers technical reference information for BizTalk Server 2006 R2.
BizTalk Server 2006 R2 supports only <NetBIOS domain name>\<user> name formats for
service accounts and Windows groups.
In general, Domain Local Groups are not recommended because their use requires that all of
the servers, including SQL Servers, in the BizTalk Server infrastructure must belong to the
same domain. This consideration does not apply to small networks where all of the servers
and user accounts reside in a single domain. For more information about Active Directory
groups, see "Group Scope" in the Windows Server 2003 product Help at
http://go.microsoft.com/fwlink/?linkid=93663.
If Domain Local Groups are used, the logon account used to configure BizTalk Server must
also be a member of the domain where the Domain Local Groups exist.
The user running the BizTalk Server configuration must belong to the following user groups:
SQL System Administrators group on the SQL server. The user does not need to be a
member of the Administrators group for the computer on which SQL Server is installed.
The domain group used for the BizTalk Server Administrators group.
Group Description
Membership
SSO
Administrator of the Enterprise Single
Administrator Sign-On (SSO) service.
Contains
service
Group
Group Description
Membership
accounts for
Enterprise
Single SignOn service.
Contains
users/groups
that need to
be able to
configure and
administer
BizTalk
Server and
SSO service.
SSO
securityadmin SQL
Server Role for the
SQL Server where
SSO is located
Contains
accounts
used to run
BizTalk
Configuration
Manager
when
configuring
SSO master
secret server.
SSO Affiliate Administrators of certain SSO affiliate
Administrator applications.
s
Can create/delete SSO affiliate
applications, administer user mappings,
and set credentials for affiliate application
users.
Contains no
service
accounts.
BizTalk
Server
Administrator
s
Contains
BAS
Management
Web Service
Account.
BTS_ADMIN_USERS
SQL Server Database
Role in the following
databases:
Contains
users/groups
BizTalkMsgBoxDb
Contains
account used
for BizTalk
Server
Administrator
s.
BizTalkMgmtDb
BizTalkRuleEngineDb
55
Group
Group Description
Membership
that need to
be able to
configure and
administer
BizTalk
Server.
BizTalkDTADb
BAMPrimaryImport
db_owner SQL Server
Database Role for the
following databases:
BAMStarSchema
BAMPrimaryImport
BAMArchive
BAMAlertsApplication
BAMAlertsNSMain
NSAdmin SQL Server
Database Role in the
following databases:
BAMAlertsApplication
BAMAlertsNSMain
HWS_ADMIN_USER
SQL Server Database
Role in the following
databases:
BizTalkDTADb
BizTalkHwsDb
BizTalkMgmtDb
OLAP Administrators
on the computer
hosting the
BAMAnalysis OLAP
database.
BizTalk
Server
Operators
Contains
user/groups
that will
monitor
solutions.
BTS_OPERATORS
SQL Server Database
Role in the following
databases:
Contains no
service
accounts.
BizTalkEDIDb
BizTalkDTADb
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
56
Group
Group Description
Membership
BizTalk
Application
Users
BizTalk
The default name of the first Isolated
Isolated Host BizTalk Host Group created by
Users
Configuration Manager. Isolated BizTalk
hosts not running on BizTalk Server, such
as HTTP and SOAP.
Use one BizTalk Isolated Host Group for
each Isolated Host in your environment.
Contains
service
accounts for
the BizTalk
In-Process
host instance
in the host
that the
BizTalk Host
Group is
designated
for.
BTS_HOST_USERS
SQL Server Database
Role in the following
databases:
Contains
service
accounts for
the BizTalk
Isolated host
instance in
the host that
the Isolated
BizTalk Host
Group is
designated
for.
BTS_HOST_USERS
SQL Server Database
Role in the following
databases:
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
BizTalkDTADb
BAMPrimaryImport
BAM_EVENT_WRITE
R SQL Server
Database Role in the
BAMPrimaryImport
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
BizTalkDTADb
BAMPrimaryImport
Contains
HWS
Runtime
Account.
EDI
Subsystem
Users
Contains
service
accounts for
BizTalk Base
EDI service.
BAM Portal
Users
Everyone
group is used
for this role
by default.
EDI_ADMIN_USERS
SQL Server Database
Role in the
BizTalkEDIDb
57
Group
Group Description
Membership
Contains no
service
accounts.
BizTalk BAS
Web
Services
Group
Contains
BAS
Management
Web Service
Account,
BAS
Publishing
Web Service
Account,
and BAS
Application
Pool
Account.
BizTalk BAS
Users
Contains no
service
accounts.
BizTalk BAS
Managers
Contains no
service
accounts.
Contains
BAS Site
Owner.
BizTalk
SharePoint
Adapter
Enabled
Hosts
Contains
service
accounts for
the BizTalk
host instance
to be able to
call
SharePoint
Adapter.
58
Group
Group Description
Membership
BAS
Enabled
Hosts
The default
BizTalk
Application
Users group
is used for
this role by
default.
User Description
Group Affiliation
Enterpris
e Single
Sign-On
Service
Service account
used to run
Enterprise Single
Sign-On Service,
which accesses
the SSO
database.
SSO Administrators
BizTalk
Host
Instance
Account
Service account
used to run
BizTalk In-Process
host instance
(BTNTSVC).
BizTalk
Isolated
Host
Instance
Account
Service account
used to run
BizTalk Isolated
host instance
(HTTP/SOAP).
Rule
Engine
Update
Service
Service account
used to run Rule
Engine Update
Service, which
receives
notifications to
deployment/undep
IIS_WPG
RE_HOST_USERS
SQL Server
Database Role in the
BizTalkRuleEngineD
b
59
User
User Description
Group Affiliation
loyment policies
from the Rule
engine database.
BizTalk
Base
EDI
service
Service account
used to run
BizTalk Base EDI
service, which
processes EDI
documentations.
HWS
Runtime
Account
Service account
used to run HWS
Messaging
components.
HWS
Web
Service
Account
Application pool
account used to
run HWS Web
Service.
IIS_WPG
IIS_WPG
STS_WPG
STS_WPG
HWS_WS_USER
SQL Server
Database Role in the
following databases:
BizTalkMgmtDb
BizTalkDTADb
BizTalkHwsDb
BAM
Notificati
on
Services
User
Service account
SQLServer2005NotificationServicesUser$
used to run BAM
<ComputerName>
Notification
No group affiliation for SQL Server 2000.
Services, which
accesses the BAM
databases.
NSRunService SQL
Server Database
Role in the following
databases:
BAMAlertsApplicatio
n
BAMAlertsNSMain
BAM_ManagementN
SReader SQL
Server role for the
BAMPrimaryImport
BAM
Manage
ment
Web
Service
User
NSSubscriberAdmin
SQL Server
Database Role in the
following databases:
BAMAlertsApplicatio
n
60
User
User Description
Group Affiliation
Portal calls
BAMManagement
Service with the
user credentials
logged on the
BAM Portal to
manage alerts, get
BAM definition
XML and BAM
views.
BAMAlertsNSMain
BAM_Management
WS SQL Server role
for the
BAMPrimaryImport
BAM
Applicati
on Pool
Account
Application pool
account for
BAMAppPool,
which hosts BAM
Portal Web site.
IIS_WPG
BAS
Manage
ment
Web
Service
Account
BAS
User
User Description
Group Affiliation
Publishin
g Web
Service
Account
by the TPM
Publishing Web
Service
(TPPubWS) to
access the BizTalk
Management
database
TPPubWS
performs the tasks
for BizTalk BAS
Users, BizTalk
BAS Managers,
and BizTalk BAS
Administrators.
STS_WPG
BAS
Applicati
on Pool
Account
Application pool
account for BAS
web services
(TpmWSSAppPoo
l) which hosts
TPMgmtWs and
TPPubWs.
IIS_WPG
STS_WPG
62
Volume
Growth
Description
SSO Database
SSODB
Low
Low
BizTalk
Management
Database
BizTalkMgmtDb
Low
Low
BizTalk
MessageBox
Database
BizTalkMsgBoxDb
High
Medium
High
High
Rule Engine
Database
Low
Low
This database is a
repository for policies, which
are sets of related rules and
BizTalkRuleEngineDb
63
Volume
Growth
Description
vocabularies. Vocabularies
are collections of userfriendly, domain-specific
names for data references
in rules.
BizTalk Base
EDI Database
BizTalkEDIDb
Low
Low
HWS
Administration
Database
BizTalkHWSDb
Low
Low
BAM Primary
Import
Database
BAMPrimaryImport
Medium
Medium
BAM Archive
Database
BAMArchive
Medium
Medium
BAM Star
Schema
Database
BAMStarSchema
Medium
Medium
BAM
Notification
Services
Application
database
BAMAlertsApplication
Medium
Medium
Volume
Growth
Description
BAMAlertsNSMain
Medium
Medium
Trading Partner
Management
Database
BizTalkMgmtDb
Low
Low
Volume
Growth
Description
BizTalk Tracking
Analysis
Database
BizTalkAnalysisDB
Medium
Medium
This database
stores both
business and
health monitoring
online analytical
processing
(OLAP) cubes.
BAM Analysis
Database
BAMAnalysis
Medium
Medium
This database
contains Business
Activity
Monitoring (BAM)
OLAP cubes for
both online and
offline analysis.
Note
Using the BizTalk Tracking Analysis database with SQL Server 2005 Analysis Services is
not supported.
65
Default database
Volume
Growth
Description
name
Windows
SharePoint
Services
configuration
database
User-defined
Low
Low
This database
contains all of the
global settings for
the server.
Windows
SharePoint
Services content
database
User-defined
Medium
Medium
This database
contains all of the
site content, such
as list items and
documents.
10. On the Installation Definition screen, ensure that Server and Client Tools are
selected, and then click Next.
On the Instance Name screen, ensure that Default is selected, and then click Next.
11. On the Setup Type screen, ensure that Typical is selected, and then click Next.
12. On the Services Accounts screen, ensure that Use the same account for each
service. Auto start SQL Server Service is selected, enter a local account or domain
account and password, and then click Next.
13. On the Authentication Mode screen, select Windows Authentication, and then click
Next.
14. On the Start Copying Files screen, click Next.
15. On the Choose Licensing Mode screen, under Licensing Mode, select the type of
licensing you have, and then click Continue.
16. On the Setup Complete screen, click Finish.
Step 5: Install SQL Server Notification Services 2.0 with Service Pack 1
Note
This is required only if you want to use Business Activity Monitoring (BAM) Alerts.
69
Note
You are required to install SQLXML 3.0 with Service Pack 3 before you install SQL Server
Notification Services 2.0 with Service Pack 1.
Note
You do not need to complete this step if you installed SQL Server 2005.
In the following procedure you start the SQL Server services. The SQL Server services must be
running before you install SQL Server Notification Services 2.0 with Service Pack 1.
To start SQL Server Services
1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click
Service Manager.
2. Under Services, select SQL Server, and then click Start/Continue.
3. Under Services, select SQL Server Agent, and then click Start/Continue.
4. Close SQL Server Service Manager.
In the following procedure you install SQL Server Notification Services 2.0 with Service Pack 1.
Microsoft SQL Server Notification Services 2.0 with Service Pack 1 provides organizations with a
platform to build scalable notification applications that generate messages customized to meet
their users' specific information requirements. SQL Server Notification Services is optional for a
BizTalk Server 2006 R2 installation. It is required only if you want to use Business Activity
Monitoring (BAM) Alerts.
To install SQL Server Notification Services 2.0 with Service Pack 1
1. Browse to http://go.microsoft.com/fwlink/?LinkId=62108.
2. On the Notification Services 2.0 Service Pack 1 download page, under Enterprise
Edition, select your download language, and then click Go.
Note
Optionally, you can install Standard Edition.
3. Download and save MSSQLNS20SP1.Ent.exe to a location on your hard disk.
4. Double-click MSSQLNS20SP1.Ent.exe.
5. On the Welcome screen, click Next.
6. On the License Agreement screen, select I accept the terms in the license
agreement, and then click Next.
7. On the Customer information screen, type your user name and organization, select
Anyone who uses this computer (all users), and then click Next.
8. On the Custom Setup screen, ensure that all features are selected to be installed, and
then click Next.
Note
At a minimum you must install Engine Components, Client Components, and
70
English
Japanese
German
French
Spanish
Italian
Korean
Simplified Chinese
Traditional Chinese
Cross-Language Support
BizTalk Server 2006 R2 provides the following cross-language support:
Localized versions of BizTalk Server 2006 R2 are supported on localized operating systems
that are the same language as the localized BizTalk Server version.
71
Installing the English-language version of Visual Studio 2005 is supported on all localized
versions of BizTalk Server. You can install a localized version of Visual Studio 2005 if it is the
same language as the localized BizTalk Server version.
Localized versions of BizTalk Server 2006 R2 are also supported on English-language versions of
supported operating systems through the use of Windows Multilingual User Interface Pack (MUI)
settings. You must verify certain operating system settings before installing a localized version of
BizTalk Server 2006 R2 on a server that is running an English-language operating system with a
non-English MUI setting. You must verify that the following operating system settings match the
language of the localized BizTalk Server to be installed:
The 64-bit editions of Windows Server 2003 are only available in English or Japanese language
versions. Support for localized versions of BizTalk Server on the English language version of 64Bit Windows is provided using MUI, as described above.
ADOMD.NET 8.0
ADOMD.Net-KB893091-v8.00.0991-x86.EXE
ADOMD.NET 9.0
72
Link
CN
http://go.microsoft.com/fwlink/?LinkId=81466
DE
http://go.microsoft.com/fwlink/?LinkId=81467
EN
http://go.microsoft.com/fwlink/?LinkId=81468
ES
http://go.microsoft.com/fwlink/?LinkId=81469
FR
http://go.microsoft.com/fwlink/?LinkId=81470
IT
http://go.microsoft.com/fwlink/?LinkId=81471
JA
http://go.microsoft.com/fwlink/?LinkId=81472
KO
http://go.microsoft.com/fwlink/?LinkId=81473
TW
http://go.microsoft.com/fwlink/?LinkId=81474
Link
CN
http://go.microsoft.com/fwlink/?LinkId=81457
DE
http://go.microsoft.com/fwlink/?LinkId=81458
EN
http://go.microsoft.com/fwlink/?LinkId=81459
ES
http://go.microsoft.com/fwlink/?LinkId=81460
FR
http://go.microsoft.com/fwlink/?LinkId=81461
IT
http://go.microsoft.com/fwlink/?LinkId=81462
JA
http://go.microsoft.com/fwlink/?LinkId=81463
KO
http://go.microsoft.com/fwlink/?LinkId=81464
TW
http://go.microsoft.com/fwlink/?LinkId=81465
73
Copyright
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the companies, organizations, products, domain
names, e-mail addresses, logos, people, places, and events depicted in examples herein are
fictitious. 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.
2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, BizTalk, Excel,
InfoPath, Internet Explorer, SharePoint, Visio, Visual C#, and Visual Studio are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
74