ConfigMgr Client Package

One of the packages you need for an operating system deployment is a ConfigMgr 2007 client package.  This package simply contains the setup files for the ConfigMgr client, which will be installed once Windows setup has completed.  This package does not require a program. The ConfigMgr 2007 client package must be manually created prior to creating…


Troubleshooting Tips

The follow is a collection of tips that may be helpful when troubleshooting issues with ConfigMgr 07 Operating System Deployment. Error Codes There is no definitive list of error codes that can be returned in a task sequence, because most of the error codes originate from calls to other Windows API functions.  The error lookup functionality provided…


Why can’t I import a driver from a local drive path?

Boot Images, Operating System Images, Operating System Install Packages, and Drivers must be imported from a UNC path in ConfigMgr 07.  Many people have asked why they can’t reference a local drive path instead.  Here is the explanation for drivers, courtesy of Michael Kelley.   The explanation for the other types of packages is analogous. Because…


Intel ICH8USB drivers demystified

For the folks that are having difficulties with the Intel ICH8USB drivers there is a simple explanation and workaround. Explanation The driver references a system DLL (usbui.dll), which is not present in Windows PE.  This causes the driver installation to fail, and since it’s considered a boot critical device (chipset), the task sequence may fail….


Boot Critical and Mass Storage Drivers

The following contribution from Brett Flegg outlines the steps for working with boot critical and mass storage drivers in ConfigMgr 07 Operating System Deployment. First, you will need to determine if the default boot image contains a compatible driver for your RAID controller.  The easiest way to do this is enable the boot image’s debug…


How do I assign a drive letter in the Format and Partition Disk step?

The short answer is, “you can’t”.  Drive letters are only applicable to an instance of a running operating system.  Any drive letters assigned in Windows PE would not be persisted when you reboot into the new operating system (or when you reboot to Windows PE for that matter), which will re-enumerate the drives and assign…


Why does Vista end up on the D: drive?

Several people have tried to use the install.wim from the Windows Vista installation media in an Install an existing image package task sequence.  They are surprised to discover that, upon completion, the operating system is on the D: drive instead of the C: drive.  The short explanation for why this happens is that the operating…


Joining a Domain: Epilogue

Fault Tolerance with Join Domain or Workgroup  Previously I mentioned that the Apply Network Settings step simply writes the domain join information to the Windows Setup answer file, and Windows Setup handles the actual domain join.  As a result, the Task Sequence is unaware of the domain join status and will continue execution after Windows…


Joining a Domain, Part 2

Capture Network Settings and Apply Network Settings are designed to work together to migrate network membership (and other network configuration info) from the old operating system to the new operating system.  For network membership, these actions share the following Task Sequence variables: OSDJoinType (0 = domain, 1 = workgroup) OSDDomainOUName OSDDomainName OSDWorkgroupName These variables are…


Joining a domain during an OS deployment

There are two ways to join a domain as part of an OS Deployment: Using the Apply Network Settings step in Windows PE Using the Join Domain or Workgroup step in the new operating system Apply Network SettingsApply Network Settings simply writes the required information to the Windows answer file (sysprep.inf, unattend.txt, or unattend.xml) and…