Peter van der Woude

It is not needed to extend the AD, but it makes the proces a lot easier... When you do not want to extend the AD, then you have to use a Server Locator Point (http://technet.microsoft.com/en-us/library/bb680672.aspx).

Did you also extend the AD?

Well... it was really straight forward and much of the same. The only difference was that you can now install WebDAV as a part of the IIS install of Windows Server 2008 R2. The rest is exactly the same, with creating a Authoring Rule and making the required WebDAV Settings. The only problem that I had was with the Reporting Services, but I am not sure if it was just bad luck or the combination of 2008 R2 with ConfigMgr 2007 SP2 R2. I will post on my blog about that, but until then you can also find the solution here: http://blogs.technet.com/configmgrteam/archive/2009/05/14/faq-sql-reporting-services-integration-with-system-center-configuration-manager-2007-r2.aspx

What does the pxeMSI.log say?

I do have SCCM SP2 R2 running on Windows Server 2008 R2. Keep in mind that only ConfigMgr 2007 SP2 (R2) is supported to run on Windows Server 2008 R2.

We need some more information, like when does it error and what do the logs says?

By hand, because the machine is not in the same domain it is not possible to let the Site Server take care of it.

Make a change to the Bootimage (like Enable Command Line) and update the Bootimage

You do not need multiple packages when you need to use updates that already excist in a package. Just create a new deployment in which you select the needed updates, ONLY the selected updates in the deployment will be advertised

Did you first mount a image?

Did you create your own Bootimage? If so, did you use Dism to create it?

From the helpfiles that are delivered with the WAIK: The general process for creating a custom Windows PE image includes: Mount the base image by using the DISM tool to a local directory share. For example, Dism /Mount-Wim /WimFile:C:\winpe_x86\winpe.wim /index:1 /MountDir:C:\winpe_x86\mount Using the Dism command with the /Get-Package option to see which packages are installed. For example, Dism /image:C:\winpe_x86\mount /Get-Packages Add packages, and language packs as appropriate by using the Dism command with the /Add-Package option. For example, to add the HTA package you must add both the language neutral package along with the language specific package. For example: Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\WinPE-HTA.cab” Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\en-us\WinPE-HTA_en-us.cab” Where <version> can be the OEM Preinstallation Kit (OPK) or the Automated Installation Kit (AIK). Add drivers as appropriate by using the Dism command with the /Add-Driver option. For example: Dism /image:C:\winpe_x86\mount /Add-Driver /driver:C:\test\drivers\mydriver.inf Add any additional custom files or tools that you intend to include in the image within the \mount directory. For example, you can include ImageX within your image, copy "C:\Program Files\<version>\Tools\x86\imagex.exe" C:\winpe_x86\mount\Windows\System32\ Where <version> can be Windows OPK or Windows AIK. Commit the changes using the Dism command with the /Unmount-Wim /Commit option. For example, Dism /Unmount-Wim /MountDir:C:\winpe_x86\mount /Commit Copy your custom image into \ISO\sources folder and rename to boot.wim. For example, copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim The customized image is now ready to be copied or burned to bootable media. The most common method is to create an .iso file and then burn the image onto a CD-ROM. For more information about bootable methods, see Booting Windows PE.

Did you take a look at the smspxe.log?

First Uninstall WAIK, but the Wizard will say that too.

Looks like a problem with the driver.

Did you import any drivers during the TS?

Did you create a Driver Package, for the HP DC7800, which contains the NIC Driver>

Did you take a look at the harddisk of this machine if it is really full or not?

When you don't want to use USMT with Hardlinks, then you should use USMT in combination with a State Migration Point. By doing this you will save the user data on the server. Just keep in mind that it can really slow down your migration proces. See this link for how to configure a SMP: http://technet.microsoft.com/en-us/library/bb693655.aspx

You could use the variable %~dp0 Take a look a this post: http://blogs.catapultsystems.com/jsandys/archive/2009/08/30/current-directory-in-configmgr-programs.aspx

Reportings Services Point indeed comes with R2

Keep it simple for yourself... just create a standard Build and Capture and remove the not needed steps

A Task Sequence can only be Advertised to Computers

When you are using COnfigMgr 2007 SP2 it will find sysprep itself during the Capture Step

When a machine is within the Boundary (AD Site or IP Address) of a Site it can get Advertisements. Windows 7 has the sysprep tools by default (C:\Windows\System32\Sysprep). It is not possible to only use the step to Capture the machine because the other steps are needed to join a workgroup, to prepare the sccm client and to sysprep the OS.