Nov 102010
 

If you look at the arguments of the setup.exe to do an install of BizTalk you can install everything by using the following switch: /ADDLOCAL ALL. However, you will notice that you can supply an xml to tell the setup what components to install:

image

But where is a sample configuration file? (I could not find it anywhere on MSDN)

You could use the following xml file to install all components, which is the tail of the configuration file that is created after the setup.exe completes.

<Configuration>
  <InstalledFeature>MsEDIAS2</InstalledFeature>
  <InstalledFeature>MsEDIAS2StatusReporting</InstalledFeature>
  <InstalledFeature>WCFAdapter</InstalledFeature>
  <InstalledFeature>InfoWorkerApps</InstalledFeature>
  <InstalledFeature>BAMPortal</InstalledFeature>
  <InstalledFeature>WcfAdapterAdminTools</InstalledFeature>
  <InstalledFeature>PAM</InstalledFeature>
  <InstalledFeature>Development</InstalledFeature>
  <InstalledFeature>MsEDISchemaExtension</InstalledFeature>
  <InstalledFeature>MsEDISDK</InstalledFeature>
  <InstalledFeature>MsEDIMigration</InstalledFeature>
  <InstalledFeature>Documentation</InstalledFeature>
  <InstalledFeature>SDK</InstalledFeature>
  <InstalledFeature>WMI</InstalledFeature>
  <InstalledFeature>BizTalk</InstalledFeature>
  <InstalledFeature>MOT</InstalledFeature>
  <InstalledFeature>Engine</InstalledFeature>
  <InstalledFeature>MSMQ</InstalledFeature>
  <InstalledFeature>Runtime</InstalledFeature>
  <InstalledFeature>RfidEventForwarderMessageTransform</InstalledFeature>
  <InstalledFeature>AdminAndMonitoring</InstalledFeature>
  <InstalledFeature>MonitoringAndTracking</InstalledFeature>
  <InstalledFeature>AdminTools</InstalledFeature>
  <InstalledFeature>BizTalkAdminSnapIn</InstalledFeature>
  <InstalledFeature>HealthActivityClient</InstalledFeature>
  <InstalledFeature>BAMTools</InstalledFeature>
  <InstalledFeature>Migration</InstalledFeature>
  <InstalledFeature>BizTalkExplorer</InstalledFeature>
  <InstalledFeature>BizTalkExtensions</InstalledFeature>
  <InstalledFeature>OrchestrationDesigner</InstalledFeature>
  <InstalledFeature>Designer</InstalledFeature>
  <InstalledFeature>PipelineDesigner</InstalledFeature>
  <InstalledFeature>XMLTools</InstalledFeature>
  <InstalledFeature>AdapterImportWizard</InstalledFeature>
  <InstalledFeature>VSTools</InstalledFeature>
  <InstalledFeature>WCFDevTools</InstalledFeature>
  <InstalledFeature>DeploymentWizard</InstalledFeature>
  <InstalledFeature>TrackingProfileEditor</InstalledFeature>
  <InstalledFeature>SSOAdmin</InstalledFeature>
  <InstalledFeature>AdditionalApps</InstalledFeature>
  <InstalledFeature>SSOServer</InstalledFeature>
  <InstalledFeature>RulesEngine</InstalledFeature>
  <InstalledFeature>OLAPNS</InstalledFeature>
  <InstalledFeature>FBAMCLIENT</InstalledFeature>
  <InstalledFeature>BAMEVENTAPI</InstalledFeature>
  <InstalledFeature>ProjectBuildComponent</InstalledFeature>
</Configuration>

And your batch script could look like this (notice you can’t use /quiet or /passive, but it can still be hands free):

"\\BizTalk Server 2010 Enterprise\BizTalk Server\setup.exe" /s "\\BizTalk Server 2010 Enterprise\BizTalk Server\CompleteSetup.xml"  /l c:\biztalksetupSSO.log /CompanyName Company /Username Developer /cabpath "\\BizTalk Server 2010 Enterprise\BizTalk Server\Bts2010Win2K8R2EN64.cab"

Option 2:

If you look deep in the log files you can see that on a full install has the following options:

MSI (s) (B8:0C) [01:30:32:802]: Command Line: ADDLOCAL=MsEDIAS2,MsEDIAS2StatusReporting,WCFAdapter,InfoWorkerApps,BAMPortal,WcfAdapterAdminTools,PAM,Development,MsEDISchemaExtension,MsEDISDK,MsEDIMigration,Documentation,SDK,WMI,BizTalk,MOT,Engine,MSMQ,Runtime,RfidEventForwarderMessageTransform,AdminAndMonitoring,MonitoringAndTracking,AdminTools,BizTalkAdminSnapIn,HealthActivityClient,BAMTools,Migration,BizTalkExplorer,BizTalkExtensions,OrchestrationDesigner,Designer,PipelineDesigner,XMLTools,AdapterImportWizard,VSTools,WCFDevTools,DeploymentWizard,TrackingProfileEditor,SSOAdmin,AdditionalApps,SSOServer,RulesEngine,OLAPNS,FBAMCLIENT,BAMEVENTAPI,ProjectBuildComponent COMPANYNAME=Company USERNAME=Developer FILESINUSEERROR= CEIP=0 CURRENTDIRECTORY=C:\Users\estott\AppData\Local\Temp\EBZ30319.tmp CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=5024 

I would like to tell you that I have figured out all of the combinations of what you want to install, but Trace Young beat me to it.

  • Matthew

    Very useful post! Thx Eric.

  • Kevin Patrick

    I work for Citrix Systems in Ft. Lauderdale, FL and I was racking my head on how to install the Biztalk rules engine for 2 days! I know it had to be something so stupid, but I was recieving WMI errors by only including
    <InstalledFeature>RulesEngine</InstalledFeature>
    in the xml install file. After reading this I added
    <InstalledFeature>WMI</InstalledFeature>
    <InstalledFeature>BizTalk</InstalledFeature>
    <InstalledFeature>RulesEngine</InstalledFeature>

    and it worked like a charm!

    The error I was recieving was “Error 5008.Registration of the BizTalk WMI provider failed. Return code -2147024894”

    Thanks!
    Kevin