Artikkeli
09/09/2016

Use Sysprep to Deploy Orchestrator

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator

You can deploy Orchestrator using Sysprep. This enables you to deploy any component in Orchestrator in a distributed environment in an automatic process.

For Orchestrator components you can create a Sysprep image by performing the following steps:

Prepare the Windows 2008 R2 image
Create the Orchestrator answer file for sysprep
Install Orchestrator using sysprep.

Prepare the Windows 2008 R2 image

Use the following steps to prepare the Windows 2008 R2 image.

To prepare the Windows 2008 R2 image

Install Windows Server 2008 R2.
Install .NET Framework 4 from https://go.microsoft.com/fwlink/?LinkId=246814. (This is only required for the web feature components of Orchestrator.)

Create the Orchestrator answer file for sysprep

Before you can use the Sysprep tool to install Orchestrator on Windows Server 2008 R2, install Orchestrator as part of the Sysprep process using an answer file.

See Sample Orchestrator.xml file for sample unattend.xml file. You can customize this sample file and import it into the Windows System Image Manager.

To create the answer file

Create the Orchestrator.xml unattend file using the sample provided.
Copy the file to %systemdrive%\windows\system32\sysprep.
Create the Orchestrator batch file that will install the Orchestrator components on this computer. An example of this file is available in Sample Orchestrator.xml file. This is referred to in the Orchestrator.xml file. See Install with the Orchestrator Command Line Install Tool for the available command line options that can be used to install Orchestrator.

Run the following command:

sysprep /generalize /oobe /shutdown /unattend:%systemdrive%\windows\system32\sysprep\Orchestrator.xml

Install Orchestrator using sysprep

You now have a Windows 2008 R2 Sysprep image that you can use to automatically deploy Orchestrator in the environment.

For information on creating a SQL Sysprep image for use with Orchestrator, refer to https://go.microsoft.com/fwlink/?LinkId=246815.

Sample Orchestrator.xml file

This is a sample Orchestrator.xml to be used for deploying Orchestrator with sysprep. Customize this using the Windows System Image Manager (available in the Windows Automated Installation Kit, at https://go.microsoft.com/fwlink/?LinkId=246813).

<?xml version="1.0" encoding="utf-8"?>  
<unattend xmlns="urn:schemas-microsoft-com:unattend">  
    <settings pass="oobeSystem">  
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="https://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  
            <AutoLogon>  
                <Password>  
                    <Value>password</Value>  
                    <PlainText>true</PlainText>  
                </Password>  
                <LogonCount>1</LogonCount>  
                <Enabled>true</Enabled>  
                <Username>Administrator</Username>  
            </AutoLogon>  
            <FirstLogonCommands>  
                <SynchronousCommand wcm:action="add">  
                    <CommandLine>cmd /c %systemdrive%\sco\install.bat</CommandLine>  
                    <Order>1</Order>  
                    <RequiresUserInput>false</RequiresUserInput>  
                </SynchronousCommand>  
            </FirstLogonCommands>  
        </component>  
    </settings>  
    <cpi:offlineImage cpi:source="wim:c:/windowsenterprise/extracted/sources/install.wim#Windows Server 2008 R2 SERVERENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />  
</unattend>

This is a sample install.bat file that is referenced in the Orchestrator.xml unattend file for the FirstLogonCommand. Create this batch file in the %systemdrive%\sco directory along with the Orchestrator setup files. This file can be customized by using the command line install tool. For more information, see Install with the Orchestrator Command Line Install Tool.

%systemdrive%\sco\setup\setup.exe /Silent /ServiceUserName:%computername%\administrator /ServicePassword:password /Components:All /DbServer:%computername%  /DbPort:1433 /DbNameNew:OrchestratorSysPrep /WebConsolePort:82 /WebServicePort:81 /OrchestratorRemote /UseMicrosoftUpdate:1 /SendCEIPReports:1 /EnableErrorReporting:always

Jaa