Sysprep BizTalk Server

964 Words2 Pages

Overview
The System Preparation (Sysprep) tool prepares an installation of Windows for duplication, also called imaging, and enables you to capture a customized Windows image that can be reused throughout an organization.

This can be particularly beneficial when provisioning machines for a team of BizTalk developers. Installing and configuring BizTalk Server machines from scratch increases the lead time on a project. The other main advantage is the guarantee that each developer is working off a consistent configuration reducing the chances of "it works on my machine" incidents.

However, Sysprepping a BizTalk Server image is not as straightforward as Sysprepping a base Operating System image; mainly due to BizTalk Servers reliance on SQL Server.

BizTalk Server ships with some sample Sysprep scripts, but as with most samples these just serve as a foundation and require some customizations and additions. The documentation that accompanies the sample scripts is misleading in places and contains some gaps that can cause confusion.

In this article I will cover the steps required to Sysprep a fully configured BizTalk Server virtual machine.

Golden Image
The "golden image" is an isolated virtual machine configured with:

Windows Server 2008 R2 Standard Edition • SQL Server 2008 R2 Enterprise Edition • BizTalk Server 2010 Enterprise Edition ○ Enterprise SSO ○ BizTalk Runtime ○ Business Rules Engine ○ BAM Tools § BAM Alerts ○ BAM Portal • BizTalk Server 2010 ESB Toolkit ○ Exception Management ○ ESB Core Components • Visual Studio 2010 Premium Edition

Steps
Install and configure the software listed above using local accounts and groups.

Prerequisites
There are a number of modifications that should be made post-configuration and pre-sysprep that will reduce the changes required during Sysprep as well as the complexity of the scripts.

These are:

More about Sysprep BizTalk Server

Open Document