When you create the operating system image to deploy to target computers, the image contains the operating system and related files. Other applications and tools can be installed as a separate task sequence step, or manually, after the operating system is installed, or the supporting applications and tools can be pre-installed as part of the image. Here are some considerations for configuring the operating system image.
Packages that Support an Image Deployment
There are several Configuration Manager 2007 packages that you need to create to support the deployment of an operating system image:
- Configuration Manager 2007 client
installation package
- User State Migration Tool (USMT) packages
- Other packages
 Important |
|---|
| Configuration Manager 2007 software packages that use the Run another program first option to install a dependent program as part of the package are not supported by Operating System Deployment |
You should create and test these packages before you create a task sequence to deploy the operating system image.
Configuration Manager 2007 Client Installation Package
To use a task sequence to install the Configuration Manager 2007 client on a destination computer, create a Configuration Manager 2007 package using the “Setup Windows and ConfigMgr” task sequence step. The package source location is %ProgramFiles%\Microsoft Configuration Manager\Client. Packages defined using the “Setup Windows and ConfigMgr” task do not require an associated program. All parameters needed for operating system deployment will be supplied by the task sequence when it is run. For more information about the available Configuration Manager 2007 client installation properties, see About Configuration Manager Client Installation Properties.
 Note |
|---|
| It is recommended that the program be configured to run when no user is logged on, and from a network share. |
USMT Package
If you are migrating user state from one desktop to another, then you must use USMT 3.0 as your migration tool for Configuration Manager 2007. You can download USMT from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=88300. Use Configuration Manager 2007 to create a package to install and run USMT on the target computer. A package program is not required. Be sure to include the configuration files (.INF) as part of the USMT package. Refer to the documentation for USMT for configuration information.
Other Packages
There are several other packages that you can create to support the operating system image deployment as well as the building of a reference computer. For more information about these packages, see About Creating the Operating System Deployment Packages.
Server-Specific Deployments
Any hardware configuration that needs to be done as part of the image deployment to a server computer must be considered and included as part of the deployment task sequence.
For example, for a new server installation you might need to flash the computer BIOS, or configure the RAID controller.
It is recommended that you include packages that contain the appropriate tools to configure the server computer hardware as part of the deployment task sequence, or include it in the Windows PE image. For example, you could create a package that runs the vendor's flash bios tool and include that as a Run Command Line task sequence step that references the package in the deployment task sequence.
Advantages and Disadvantages of Installing Applications and Tools using a Task Sequence
Applications and tools can be preinstalled as part of the image being deployed, or they can be installed separately (either manually, or as a custom task in a deployment task sequence) after the operating system has been deployed. This table outlines the advantages and disadvantages for each.
| Installation method | Advantage | Disadvantage |
|---|---|---|
|
Install as part of operating system image |
Potentially faster deployment to target computers No need to host the application for deployment separately |
Need to create a new image when updates are required Need to create an image for each distinct set of installation or setup properties Potentially larger overall image sizes Not all applications can be part of an image. The applications must be able to be generalized by Sysprep to be part of the image. |
|
Install separately from the image |
Fewer images to maintain Fewer update images to create |
Potentially longer deployment and installation times, using separate Configuration Manager 2007 packages. |