Getting Started with SCCM 2007 and Windows 7 OSD (Part 1)

SCCM is daunting; almost no one would disagree. Here’s a guide to approaching Windows 7 Operating System Deployment with System Center Configuration Manager 2007. This post will cover most of the preparation necessary to begin creating task sequences that work.



ADSI Files

For ADSI support in WinPE the following files for the intended platform are needed (or both x86 and x64). Copy the files from the %systemroot%\system32 folder from a Windows 7 or Server 2008  installation of the appropriate platform to “C:\Plugins\ADSIx64” or “C:\Plugins\ADSIx86” respectively.
  • adsldp.dll
  • adsmsext.dll
  • adsnt.dll
  • mscoree.dll
  • mscorier.dll
  • mscories.dll

Upgrading to WinPE 3.1

  1. Extract the downloaded file, ‘waik_supplement_en-us’, to C:\workingtemp\wait_supplement_en-us
  2. Run the following command to overwrite the WinPE 3.0 WAIK boot images with the new 3.1 boot images.
    xcopy "C:\workingtemp\waik_supplement_en-us" "C:\Program Files\Windows AIK\Tools\PETools" /ERDY
  3. Extract the ADSI Plugin for WinPE 3.0 to C:\Plugins\.
  4. Copy the ADSI DLL’s listed in the previous section from a Windows 7 x64 or Server 2008 x64 installation into “C:\Plugins\ADSIx64”.
  5. Copy the batch files named “CreateBootImage_x64.bat” and  “CreateBootImage_x86.bat” to “C:\Program Files\Windows AIK\Tools\PETools”
  6. Open a command prompt, navigate to the “C:\Program Files\Windows AIK\Tools\PETools” folder and run the batch file named “CreateBootImage_x64.bat”. This will output a new customized PE image to “C:\WinPE_x64”. The batch file must be run from the PETools folder.
    Note: It is normal for the script to error about the command named “oscdimg.exe”. This file is used to create an ISO of the wim image, which is not necessary for SCCM.
  7. Repeat steps 4-5 for the x86 platform.
  8. Run the following commands to copy the new WinPE images to the source folder.
    mkdir \\sccm\source$\bootimages\winpe3.1\x64
    mkdir \\sccm\source$\bootimages\
    mkdir \\sccm\source$\bootimages\winpe3.1\
    mkdir \\sccm\source$\bootimages\winpe3.1\x64
    mkdir \\sccm\source$\bootimages\winpe3.1\x86
    Copy "C:\WinPE_x64\winpe.wim" \\sccm\source$\bootimages\winpe3.1\x64
    Copy "C:\WinPE_x86\winpe.wim" \\sccm\source$\bootimages\winpe3.1\x86
  9. Make sure that your computer’s AD account has “full control” permissions on the share “\\sccm\source$”.
  10. Open SCCM Console and Navigate to Site Database -> Computer Management -> Operating System Deployment -> Boot Images.
  11. Right click ‘Boot Images’ and choose ‘Add Boot Image’.
  12. For some reason, I can’t figure out how to get sccm to use the regular source$ share as the source path due to a permissions problem. I got around this by using the administrative share. On the ‘Data Source’ screen, enter “\\sccm\<driveletter>$\<pathToSourceShare>\bootimages\winpe3.1\x64\winpe.wim” then select the x64 PE boot image from the drop-down menu.
    Ex: “\\sccm\f$\shares\source\bootimages\winpe3.1\x64\winpe.wim”.
    Note: the path on the image below is not correct.

  13. On the ‘general’ screen, Enter ‘WinPE 3.1 x64″ as the name and press ‘next’.

  14. Click Next through the Summary Screen.
  15. Wait until the ‘Progress’ screen is complete.
  16. On the confirmation screen, click “Close”.
  17. Perform the same steps for the x86 version of winpe 3.1 located at: “\\sccm\source$\bootimages\winpe3.1\x86\winpe.wim”.

Distribute WinPE Images to the PXE Share

Now that your WinPE images are updated with WinPE 3.1 and ADSI, we need to distribute them to the PXE Distribution Point.

  1. Open SCCM Console and navigate to Site Database -> Computer Management -> Operating System Deployment -> Boot Images.
  2. Right-click your WinPE x64 Boot Image and select “Manage Distribution Points”
  3. Click “Next” past the welcome screen.
  4. On the “Select Destination Distribution Point” screen, choose “Copy the package to new distribution points” and click “next”.
  5. On the “Package” screen, check the box next to the distribution point which contains the string “PXE”, then click “next”.
  6. On the “Completion” screen click “next”.
  7. On the “Summary” screen click “next”.
  8. On the “Progress” screen wait until the process is finished.
  9. On the “Confirmation” screen click “Close”.
  10. Perform steps 2-9 for the x86 boot image also.

Installing and Integrating MDT

  1. First close SCCM console. MDT won’t integrate with the SCCM console running.
  2. Install MDT from the downloaded package.
  3. In the Start Menu there should be a folder named “Microsoft Deployment Workbench”. In this folder, run “Configure ConfigMgr Integration”.
  4. On the “Options” screen enter your SCCM server name and site code then click “next”.
  5. On the “Completion” screen click “Finish”.
  6. Create the folder \\sccm\source$\packages\MDT2010
  7. Create the folder \\sccm\source$\packages\MDTSettingsDefault
  8. Open SCCM Console and Navigate to Site Database -> Computer Management -> Operating System Deployment -> Task Sequences.
  9. Right click “Task Sequences” on the left pane then click “Create Microsoft Deployment Task Sequence”.
  10. On the “Choose Template” screen select “Microsoft Deployment Custom Task Sequence” from the drop-down and click “Next”.
  11. On the “General” screen enter a name for the task sequence and click “Next”.
  12. On the “Boot Image” screen click “Browse”, select your boot image, and click next.
  13. On the “MDT Package” screen click “Create a new Microsoft Deployment Toolkit Files package” then enter “\\sccm\source$\packages\MDT2010” for the path and click “Next”.
  14. On the step “MDT Details” screen enter “MDT 2010 Toolkit Package” for the name and “English” for the language and click “Next”.
  15. On the “Settings Package” screen choose “Create a new settings package” and enter “\\sccm\source$\packages\MDTSettingsDefault” for the path, then click “Next”.
  16. On the “Settings Details” screen enter “MDT Default Settings Package” for name and “English” for language, then click “Next”.
  17. On the “Summary” screen click “Next”.
  18. On the “Progress” screen, wait until the process is finished.
  19. On the “Confirmation” screen click “Finish”.
  20. Right click each new package and select “Manage Distribution Points”.
  21. Distribute the MDT Toolkit and Settings packages to the SCCM distribution point, but do NOT distribute them to the PXE distribution point.

Creating an Operating System Install Package

  1. Extract your Windows 7 Media to \\sccm\source$\ospackages\win7x64sp1 (change the folder name if you need to).
  2. In SCCM console navigate to Site Database -> Computer Management -> Operating System Deployment -> Operating System Install Packages.
  3. Right-click “Operating System Install Packages” and choose “Add Operating System Install Package”.
  4. On the “Data Source”‘ screen enter “\\sccm\source$\ossource\win7x64SP1” for the source directory and click “Next”.
  5. On the “General” tab enter “” for name then click “Next”.
  6. On the “Summary” screen click “Next”.
  7. On the “Confirmation” screen click “Close”.
  8. Right click the new Operating System Install Package and click “Manage Distribution Points”.
  9. Distribute this package to your SCCM server’s distribution point but do NOT distribute it to the PXE distribution point.


A lot is now done, but there’s a lot left to do — drivers, sccm client package, usmt package, etc. Watch for part two of this post soon!


6 thoughts on “Getting Started with SCCM 2007 and Windows 7 OSD (Part 1)

  1. Pingback: SCCM – Adding Active Directory Support to WinPE 3.1 « windowsmasher

  2. Pingback: SCCM Task Sequence – Robocopy and WIM Image Backups from WinPE « windowsmasher

  3. Once again, great documentation!! Keep up the good job.

    I am experiencing a very strange issue and don’t know where to look to resolve it. perhaps you can help?

    I’d followed every steps from your blog and it works great.
    I can build and captures images for both x86 and x64 on “VMware” with no problem. However, If I try to perform the build and capture on a physical workstation, It boots into PXE no problem, but it failed to do anything after.
    It’s just sitting there doing nothing.

    My SCCM is configured to prompt for the password, it worked when it’s running on VM, but not on Physical computers.

    Any idea why? or where should I check if there are any logs I should read?

  4. Pingback: SCCM: Windows Updates for an XP Task Sequence | Windows Stuff That Your Dreams Dreamed Of

  5. Pingback: Getting Started with SCCM 2007 and Windows 7 OSD (Part 1) « windowsmasher | Virtually Cloudy

  6. Pingback: Table of Contents | windowsmasher

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s