Hello, Is the SCCM client a prerequisite on the reference machine when I want to capture it using capture media? Regards, Mark

If you are using the Capture media then you shouldn't have the client installed because it should be a clean image, no client and should have never been joined to a domain. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Hi Mark, To build the reference computer, the reference computer must meet the following requirements: 1. The computer must be a member of a workgroup. 2. The local Administrator password must be blank. 3. Logon does not require a strong password (with letters, digits, special characters, such as %$* and others, or require a minimum length) in the local system policy. See this artile for details: How to Capture an Image from a Reference Computer by Using Capture Media http://technet.microsoft.com/en-us/library/bb694129.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Configure the reference computer with the: Description Appropriate operating system. The reference computer must be installed with the operating system that you intend to deploy as an image to a collection of one or more target computers. For all operating system images except Windows Vista, the associated HAL type must match the target computer's HAL type. For example, you cannot capture a virtual operating system image and apply that image to a target computer. Appropriate service pack. It is recommended that the operating system running on the reference computer should have the most current service pack applied. Appropriate software updates. It is recommended that the operating system running on the reference computer should have the most current software updates applied, especially security updates. Appropriate applications. You can install all software applications that you would like to include in the image you are deploying to a collection of one or more target computers. You can also install software applications manually or as a custom task sequence step rather than as part of the image when you deploy the captured image. The advantages and disadvantages of each method of installation are described in the section Advantages and Disadvantages of Installing Software Applications and Tools as Part of an Operating Image Deployment. 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. Configuration Manager 2007 uses Sysprep to collect information about the applications you installed. However, not all applications are compatible with Sysprep. You must install those applications as a separate task sequence step after the image is deployed, or manually. Reference computer must be a member of a workgroup The reference computer must be configured as a member of a workgroup. Appropriate version of Sysprep or another migration tool. When you are preparing a Windows XP, Windows 2000 Professional, Windows 2000 Server, and Windows Server 2003 operating system image, the reference computer must have the version of Sysprep appropriate for that operating system installed, particularly if you are deploying the image to more than one target computer. Configure a C:\Sysprep folder in the reference computer by copying sysprep.exe and setupcl.exe to that folder. You can manually Sysprep the reference computer by running the command: sysprep -mini -quiet - reseal -reboot When you are deploying a Windows Vista or a Windows Server 2008 operating system image, the Sysprep location is created by default. The default location is %windir%\System32\sysprep You can also automate Sysprep using a task sequence step or if you are using capture media. For more information about creating capture media see: How to Capture an Image from a Reference Computer by Using Capture Media Important The Prepare Windows for Capture task sequence step attempts to reset the local administrator password on the reference computer to blank before running Sysprep. If the Local Security policy Password must meet complexity requirements is enabled, then this task sequence step fails to reset the administrator password. In this scenario, disable this policy before running the task sequence. Appropriate tools and scripts you require to mitigate installation scenarios. You can install the application compatibility tools and scripts necessary to troubleshoot known installation scenarios on target computers as part of the image that you are deploying to a collection of one or more target computers. You can also install these tools and scripts manually or as a custom task sequence rather than as part of the image. The advantages and disadvantages of each method of installation are described in the section Advantages and Disadvantages of Installing Software Applications and Tools as Part of an Operating Image Deployment. Appropriate desktop customization (wall paper, branding, default user profile). The reference computer can be configured with the appropriate desktop customization properties that you want to include as part of the image you are deploying to a collection of one or more target computers. Desktop properties include specified wall paper, organizational branding, and a standard default user profile. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.