50 steps to deploye XP Sp2 with OSD

  1. Create a network access account, it only need be a domain user and its password should not expire. Add the account to the Computer Client Agent in the Client node under Site Settings
  2. Import XP SP2 as an operating system Install Package (Note most common issue here.
  3. Add a Distribution point to your new XP SP2 package created in step 1
  4. Create the XP SP2 sysprep package in SCCM
  5. The Deploy.cab included on the CD was not updated properly for XP SP2 so you must download a new version here.
  6. Create a package that points at the extracted CAB file for its source
  7. You do not need to create any programs for the package the build task sequence takes care of this
  8. Add the package to a DP that can be used during your build
  9. Create a package from definition for the Config Mgr Client (a definition is available called “Configuration Manager Client Upgrade” in the create package from definition wizard)
  10. Specify always obtain file from source directory
  11. Usually here I create a share at SCCMSERVERSCCMClient pointing to SCCMSERVERSMS_XXXClient where XXX is the site code in order to make it easier for manual installs in the future. Note I also usually grant domain computers read access to the share and directory to prevent permissions problems in the future (Note this last permissions step may no longer be necessary in SCCM but I haven’t tested it yet)
  12. Update the ccmsetup command line properties accordingly. Extensive information about command line properties on TechNet here.
  13. Add the package to a DP that can be used during your build
  14. Create a “Build and capture a reference operating system image” task sequence
  15. Name the task sequence something appropriate like “Build Windows XP Gold Image”
  16. Select a boot image (I suggest x86 as it will run on all platforms, plus you will be booting from PXE so it really doesn’t matter)
  17. Select the Operating System Package you created in step 1
  18. Enter a product key
  19. Set the local admin password to blank
  20. Join a workgroup
  21. Select the Config Mgr client you created in step 4
  22. I generally don’t install updates in this phase but this is debatable. You must weigh time to deploy if you have to deploy a bunch of updates during deployment time vs. superseded updates and rebuilding your image more often.
  23. Don’t add any software to the base image
  24. Set your image properties
  25. Select a location to save the image and make sure you include the full path including the .wim extension
  26. Enter an account with rights to write to the share
  27. Finish up
  28. Change the task sequence to use “Quick Format”
  29. Right Click on the Task Sequence and choose Edit
  30. Select the “Partition Disk 0″ step
  31. Choose properties on the Default (Primary) partition and check the “Quick Format” option
  32. Create a collection to which you will advertise the task sequence; I usually use _OSDBase Builds
  33. Advertise the task sequence to the collection you created in step 7 as optional
  34. Right click Task sequence and choose advertise, follow the wizard
  35. Make sure you select the check box “Make this task sequence available to boot media and PXE”
  36. If you are in test and your boundaries are not defined make sure you select “When no local distribution points are available, use remote distribution point”
  37. Make sure you completed step 1
  38. Select a client to build your base image
  39. I suggest using a virtual platform to keep the drivers in the image at a minimum
  40. VMWare ESX is not a good candidate as a platform as it uses SCSI disks only to my knowledge. You do not want SCSI Mass storage drivers in your image, use MS Virtual Server / Virtual PC / Hyper-V or VMWare Server / Workstation
  41. Ensure that you have the network and mass storage drivers to boot the device on the boot image and in the driver store (If you have to do this in the future you must update the PXE and standard DPs)
  42. Add the appropriate boot images (x86 / x64) to the PXE and standard DPs
    1. If you don’t see a PXE DP it means you don’t have one :), get WDS installed and your PXE Service point
  43. Allow the client to boot from PXE
  44. If this client previously had an SCCM agent on it you just need to add the client to the collection you created in step 6
  45. If this is a new client and SCCM is pre-R2 add the client manually
    1. Add the client by right clicking the Computer Associations node under OSD and choosing “Import Computer Information”
    2. Enter the Name of the computer; I use XPBase
    3. Enter the MAC and or SMBIOS GUID
    4. Add the computer to the collection you created in step 7
  46. If you are using SCCM R2 you can enable unknown computer support on the PXE service point but choose wisely; option 10.2 may still be the best choice given the risk of accidentally formatting your CXOs laptop
  47. Boot the device up to PXE and choose your task sequence. In less than an hour you should have the start of a great XP Image

  48. ——————-

Leave a Comment