Leveraging Microsoft® System Center Configuration … Integration.pdfLeveraging Microsoft® System Center Configuration Manager 2007 for Dell Factory Customization 10 Configuring

Leveraging Microsoft® System Center Configuration Manager 2007 for Dell™ Factory Customization

A Dell Technical White Paper

Dell Services Product Development Greg Ramsey and Warren Byle Edited by Reagan Evans and Ross Hobbie March 2010

Leveraging Microsoft® System Center Configuration Manager 2007 for Dell Factory Customization

2

THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL

ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR

IMPLIED WARRANTIES OF ANY KIND.

© 2010 Dell Inc. All rights reserved. Reproduction of this document in any manner whatsoever without

the express written permission of Dell, Inc. is strictly forbidden. For more information, contact Dell.

Dell, the DELL logo, Latitude, and OpenManage are trademarks of Dell Inc. Microsoft, Windows, and

Windows Vista are either trademarks or registered trademarks of Microsoft Corporation in the United

States and/or other countries. Other trademarks and trade names may be used in this document to

refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any

proprietary interest in trademarks and trade names other than its own.


3

Executive Summary This whitepaper provides an overview on how to leverage Dell Hardware Customization with the

operating system deployment capabilities of Microsoft System Center Configuration Manager 2007™ to

deploy a customized system image (OS, applications, settings) on new Dell client systems.


4

Table of Contents Executive Summary ....................................................................................................................................... 3

Table of Contents .......................................................................................................................................... 4

Introduction .................................................................................................................................................. 5

Benefits of Dell Hardware Customization ..................................................................................................... 6

Dell Hardware Customization Process Overview .......................................................................................... 7

Prerequisite Activities ................................................................................................................................... 8

1. Create a stand‐alone media build ..................................................................................................... 8

2. Apply the Stand‐Alone Media Build to an offline PC and validate the build process ....................... 9

Configuring your Stand‐Alone Media Build for Dell Custom Factory Integration ...................................... 10

1. Using conditional statements to enhance your existing task sequence ......................................... 10

2. Modify the “Partition Disk” Step so that it does not run in the Dell factory. ................................. 11

3. Add Required “Apply Driver Package” Steps to support models ordered from Dell Factory. ........ 12

4. Create and configure a new Group – “Dell CFI Integration.” .......................................................... 12

5. Create the Media Build .iso ............................................................................................................. 14

6. Test the Stand‐Alone Media Build to Simulate Dell Configuration Services Integration ................ 15

Advanced Scenarios .................................................................................................................................... 16

Create a Custom Computer Name .......................................................................................................... 16

Summary ..................................................................................................................................................... 17

References .................................................................................................................................................. 17

Related Reading .......................................................................................................................................... 17


5

Introduction Today’s enterprise information technology (IT) departments typically manage a heterogeneous mix of

decentralized client hardware and various software applications. Large scale enterprise administration

requires centralized systems management processes that utilize consistent management methods for

diverse network clients. Some typical IT administrator activities involve deploying standardized OS builds

on client hardware, and gathering application software, hardware, and operating systems (OS)

information across the network from a central management console.

Dell offers several ways to assist IT administrators with rapid development and deployment of a

customized build on Dell client systems. To further simplify the initial operating system deployment

(OSD) and configuration activities, administrators can leverage their customized build process for Dell

client systems within the Dell factory. This white paper provides an overview of using the operating

systems deployment capabilities of Microsoft System Center Configuration Manager 2007™ (ConfigMgr)

to deploy a customized OS build on new Dell client systems.

The intended audience for this paper is IT and network administrators or managers who use ConfigMgr

to perform OSD activities within their organization. In order to successfully follow the guidelines

presented in this white paper, administrators need to understand creating and deploying customized

builds on Dell client systems and have experience in creating and validating a stand‐alone media build

from a ConfigMgr OSD task sequence.


6

Benefits of Dell Hardware Customization The timeline diagram below details the benefits of using Dell Hardware Customization with your

existing ConfigMgr OSD task sequence; the time and effort normally required to launch and complete

your OSD build can be moved from the local site and into the Dell factory, freeing up time and resources

for other tasks. Dell refers to this process as Custom Factory Integration (CFI).


7

Dell Hardware Configuration Process Overview The diagram below outlines the basics steps in ConfigMgr OSD task sequence integration with the Dell

factory.


8

Prerequisite Activities The ConfigMgr task sequence must support the following scenarios before configuration for use with

CFI.

1. Create a stand‐alone media build Creating a stand‐alone media build should be a simple process. Review the Microsoft document

How to Create a Stand-alone Media for detailed information. As a review, there are a few key items

to note:

A. Use the Task Sequence Step “Apply Driver Package” instead of “Auto Apply Drivers”

Auto Apply drivers is not supported in a stand‐alone media scenario, as the system does

not have access to your ConfigMgr site. A Dell OS deployment best practice is to use the

OSD CAB files, and WMI queries to ensure that the proper drivers are applied to the

proper model. Review the walk‐through on Dell TechCenter to learn how to use the OSD

CABs and Apply Driver Packages. Also review the information on Microsoft‘s TechCenter

for the Apply Driver Package step.

B. ‘Install Software Updates’ is not supported with Stand‐alone Media

The Install Software Updates Task Sequence step is not supported in a stand‐alone

media scenario, as the system does not have access to your ConfigMgr site. Install all

security updates into your base .wim using ConfigMgr’s Build and Capture Process.

C. Dell Best Practices

In addition to ConfigMgr requirements for a stand‐alone media build, Dell also has

requirements (and reminders) for successful integration into the factory integration

(CFI) process.

1. Do not run custom actions to configure the local disk. Running diskpart or

similar tools to manage the disk and partitions will disrupt the CFI process; work

with your CFI project engineer to have CFI create the needed disk/partition

configuration.

2. Systems will not join your domain while in the Dell Factory. As your systems

will not have domain access in Dell factories, the “Apply Network Settings” task

sequence step will not successfully join your domain. Follow the steps later in

this document for how to modify your task sequence to join your domain (if

required) later in the task sequence.


9

3. Move task sequence steps that require network connectivity to the end of the

overall task sequence process. For the custom factory integration to be

successful, there must be a point in your task sequence where offline build tasks

complete and your system “hands off” control back to CFI. In the factory, this

allows the hardware to be shut down, boxed, and shipped directly to the user (if

desired). At that point, your user will power up the system and the task

sequence can resume with on‐network tasks. These tasks can leverage your

enterprise LAN/WAN connectivity (if desired) to complete additional steps, such

as join the domain, activate Windows™, and other domain/network‐specific

actions.

4. Enable Continue on Error. For build process consistency, you may want to

enable the “Continue On Error” checkbox on each task sequence step. Some

application installations may return an unexpected error code during the build

process that may cause the entire process to fail.

2. Apply the Stand‐Alone Media Build to an offline PC and validate the build process

It is very important to validate your task sequence prior to adding the steps for Dell CFI. Use the

information in the previous section to modify your standard task sequence and create a stand‐

alone media build. After successfully completing the stand‐alone media build, validate that the

steps you modified are working properly, such as “Apply Driver Package” and other custom

steps. For more detail on this process, refer to the section: Test the Stand‐Alone Media Build to

Simulate Dell CFI.


10

Configuring your Stand‐Alone Media Build for Dell Custom

Factory Integration

For successful factory integration, you will need to modify your standard task sequence so that it will

perform properly in the Dell factories. This section walks you through the basic process to modify the

task sequence to work properly with the Dell CFI process. For more information, visit the ConfigMgr

section on Dell TechCenter.

1. Using conditional statements to enhance your existing task sequence Figure 1 displays the standard task sequence created when you use the “Install an existing image

package” option in the “New Task Sequence Wizard;” you should modify your existing task

sequence to simplify your deployment process. Using multiple task sequences to deploy the

same OS should be avoided as it increases the deployment solution complexity.

Figure 1 ‐ Standard Task Sequence


11

In Figure 1, the highlighted sections are the ones that run based on conditional statements.

Read more information on conditional statements in Microsoft TechNet’s coverage of the Task

Sequence Options Tab. If you select the task sequence group “Capture Files and Settings”, and

click the Options tab, that step will only run if the task sequence variable _SMSTSInWinPE

equals “false”. This variable is automatically configured at the start of the task sequence. Bare

metal and media builds set this variable to false so that it will only run if the task sequence was

launched from Windows. Take a few minutes to review the other conditional statements to

become more familiar with the flexibility of the task sequencer.

NOTE: The following groups/steps do not execute during a stand‐alone media build process:

Capture Files and Settings

Restart in Windows PE – not needed, as you start in WinPE

Apply Device Drivers – not needed as it uses the “Auto Apply Drivers” process

Install Updates – not needed as it uses the “Install Software Updates” step

2. Modify the “Partition Disk” Step so that it does not run in the Dell factory.

The only task sequence step we need to modify is the “Partition Disk” step. We need to ensure

that this step does not run during the CFI process in the factory. Modify the conditional

statements for “Partition Disk” step to appear as shown in Figure 2.

Figure 2 – Modifying the “Partition Disk” Step

The modifications in Figure 2 allow this step to run only if neither of these conditions is true:


12

The task sequence is launched from Windows (Mandatory Assignment or Run

Advertised Programs).

A custom variable (inserted during media creation) CFI is equal to True. So if

CFI=True, this step will not run.

3. Add Required “Apply Driver Package” Steps to support models ordered from Dell Factory.

As mentioned previously, the “Auto Apply Drivers” step is not supported when using a stand‐

alone media build; review the walk‐through on Dell TechCenter for complete details. To

properly apply drivers, create an “Apply Driver Package” step, select a valid driver package, and

then add the conditional statement as shown in Figure 3.

Figure 3 – Apply Driver Package and Conditional Statement

Repeat this step for each model that you will support using Dell CFI Integration.

4. Create and configure a new Group – “Dell CFI Integration.” The “Dell CFI Integration” group consists of three primary sections:

A. Handing the process back to CFI that signals CFI to exit the process on the next system

restart.

B. System restart step – occurs in Dell factory.

C. Post‐Delivery configuration – a group of all task sequence steps that occur once the

system is installed, connects to the network, and powers up.

Figure 4 shows how to create the conditional statement in the “Dell CFI Integration” task

sequence group. This is the last conditional statement required for CFI integration.


13

Figure 4 – The Dell CFI Integration Group

A. Create the step “Handoff to CFI”

Next, create a “Run Command Line” task sequence step called “Handoff to CFI,” and

configure it as show in Figure 5.

Figure 5 – The “Handoff to CFI” Task Sequence Step

Specify the information exactly as shown in Figure 5. The CFI integration team will

provide CFI_Launch.bat at the factory. Verify that D:\ is entered in the “Start in:” text

box, unless instructed differently by the CFI team.

B. Create the Restart Computer Step

This is the last step required for CFI, and is the last step that will occur in the Dell

factory. All additional steps execute upon first boot in your facility.


14

C. Create the Post‐Delivery Configuration Group

Include all steps in this group that you need to complete your build process. Figure 6

displays the Post‐Delivery Configuration group, which includes the following:

“Join Domain” step that runs while the system is connected to the customer

network.

“Install Custom Business Application‐On Network” step, to simulate installing

applications that may require network resources (query a database, AD Site

information, etc).

“Activate Windows” step to trigger activation of Windows to an internal KMS

Server; your environment may or may not require this, but is a good example of a

step required to run on –network.

“CFI Cleanup” step that removes unneeded files from the disk. Configure this step

exactly as shown in Figure 6. The CFI integration team will provide CFI_cleanup.bat

at the factory. Verify that c:\dell\CFI\ is entered into the “Start in:” text box, unless

instructed differently by the CFI team.

Figure 6 – CFI Cleanup Step

5. Create the Media Build .iso Use the standard ConfigMgr Process to create the stand‐alone media build.


15

A. Right‐Click on your task sequence, and select Create Task Sequence Media.

B. Select Stand‐alone Media.

C. Select CD/DVD Set, and enter the File Name for the media.

D. Clear the Protect Media with a password checkbox.

E. On the Variables tab, create a new variable, with a name of CFI, and a value of True.

Figure 7 – Setting CFI=True Task Sequence Variable for Stand‐Alone Media

F. Complete the Wizard to create the media build file(s).

6. Test the Stand‐Alone Media Build to Simulate Dell CFI Although you cannot replicate the entire Hardware Customization process, you should perform

a simulation of the process to identify potential failures. If your process is similar to our

example, with post‐delivery configuration that requires network access such as join domain, do

your best to simulate the system being off and on the network. The following steps represent a

brief test simulation walk‐through:

A. Create the stand‐alone media DVD(s).

B. Disconnect the test system from the network.

C. Prepare your disk/partitions manually, if required.

D. Boot the test system using the media DVD.

E. Click Next to start the build process.

F. Watch the build for the Restart Computer step to occur at the beginning of the Dell CFI

integration group, and during the restart, connect the system back to the network; this

represents the point where the system will be delivered to your facility.


16

G. Allow the task sequence process to complete.

H. Log into the system, and verify all configuration and application installation settings to

confirm a successful deployment.

Advanced Scenarios

Create a Custom Computer Name

You may require a custom computer name for your systems. If your custom computer name depends on

hardware information, you can to customize it during the task sequence. Here's an example of how to

set the computer name equal to the service tag during the OSD Process.

1. Create a vbscript named "SetComputerName.vbs", and insert the following information into the script:

SET env = CreateObject("Microsoft.SMS.TSEnvironment")

' Connect to WMI

Set objWMIService=GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" _

& strComputer & "\root\cimv2")

' Find the Service Tag, which will make up the last part of the computer name

Set colservicetag=objWMIService.ExecQuery("Select * from Win32_Bios")

For Each objservicetag in colservicetag

strName = objservicetag.serialnumber

Next

' Set the variable

env("OSDCOMPUTERNAME") = strName

2. Save the script. 3. Create a new ConfigMgr package, and send to distribution points (DPs). 4. Edit your task sequence. 5. Immediately following the "Partition Disk" step, insert a new task for "Run Command Line". 6. Select the package that contains the vbscript. For the command line, enter :


17

Cscript //nologo SetComputerName.vbs

7. Click OK to save the task sequence. 8. Re‐create the stand‐alone media.

For more information, review About Task Sequence Variables in the Microsoft TechCenter.

Summary The Dell Hardware Customization integration process simplifies IT for ConfigMgr administrators by

enabling a single‐source provisioning solution for all deployment scenarios, including direct from the

Dell factory. This reduces operating expenses by reduction or elimination of time and resources

previously required for the deployment of new Dell systems.

References Additional Dell documentation can be found on DellTechCenter.com

CONFIGURATION MANAGER 2007 Product Overview – Microsoft Corporation

Operating System Deployment in Configuration Manager – Microsoft Corporation

How to Create a Stand‐alone Media – Microsoft Corporation

Deploy Windows Vista to the Dell Latitude E6400 Using ConfigMgr Operating System Deployment – Dell

TechCenter

Apply Driver Package – Dell TechCenter

Build and Capture Process – Microsoft Corporation

SCCM – System Center Configuration Manager – Dell TechCenter

Task Sequence Options Tab – Microsoft Corporation

About Task Sequence Variables – Microsoft Corporation

Related Reading

Deploying OS Images on Dell Business Client Systems Using MS Deployment Toolkit – Dell


18

Deploying OS Images on Dell Latitude & Precision E Series Systems Using MS SCCM 2007 — Dell

Documents

Leveraging Microsoft® System Center Configuration … Integration.pdfLeveraging Microsoft® System Center Configuration Manager 2007 for Dell Factory Customization 10 Configuring