Jump to content

  • 0

how can I deploy Windows XP SP3 using SCCM 2007 SP1 - Part 2


This guide assumes you have installed SCCM 2007 SP1 and then configured it as outlined here in Part 1 you must then do the additional configuration outlined in Part 2, and you must have completed the final configuration tasks in Part 3. Lastly you must be able to deploy an application using SCCM 2007


In addition to the above you must have completed Part 1 of this guide



Create the Task Sequence


right click on Task Sequences and choose New Task Sequence




choose the second option (Build and Capture a reference operating system image)




fill in your Task Sequence Information




click browse and select our X86 boot image


Note: if you don't see the x86 windows PE boot enviroment for SCCM 1.0 EN-US image listed then follow these steps first.






On the Install Windows screen click on Browse and select the XP SP3 operating system install package we created in Part 1.




Input your product key and make sure to enable the local Administrator account,




Configure Network


Here we need to enter our network configuration and click next, choose Join Workgroup (recommended best practise). Although joining the domain will work just fine you may have GPO's in place, or startup scripts (login scripts) etc which may taint your master image, keeping it off the domain will keep it clean.


on the Install ConfigMgr screen, browse to the Predefined ConfigMgr Client Package we created earlier






for the Updates and Software screens choose don't install any (ie: next, next)


for the System Preparation screen click on browse and choose the sysprep package we created earlier




fill in the image properties




On the Capture image screen, browse to a share on your network for copying the image to, and give the file a name





fill in your user account for capturing the image with, I use SMSadmin




click next, next and close at the confirmation screen



Share this post

Link to post
Share on other sites

Recommended Posts

  • 0

Edit the Task Sequence


Now that we have made our task sequence let's make the deployment process faster by forcing the Format process to do a quick format.


Right-click on the TS and select Edit.




In the Task Sequence, click on Partition Disk 0 and then click (to highlight) the Default volume listed, once done you can edit the properties of it by clicking on the middle icon (edit, see screenshot)




when the partition details come up, place a checkmark in Quick Format




click OK when done.

Share this post

Link to post
Share on other sites

  • 0

Advertise the Task sequence


We will now advertise the Task Sequence to the Build and Capture XP Collection we created in Part 1, so to do this right click on the Task Sequence and choose Advertise.


On the general screen click browse and select the Build and Capture XP Collection




make it available to boot media and pxe







Set your schedule depending on whether you are in a Lab or Production Environment.


For a Lab Environment


Make the Task Sequence mandatory by clicking on the yellow star and select As soon as possible.


Select ignore maintenance windows when runing program and allow system restart, set the program rerun behaviour to always rerun program so that we can rerun the task sequence over and over as we require for testing.


for a lab env.jpg


For a Production Environment


In a Production environment set the advertisement from Mandatory to Optional, this gives us less risk of an accidental deployment but also introduces the possibilty of choice.



for a prod env.jpg


if you want to remove choice then keep the advertisement mandatory but change the program rerun behaviour to never rerun (see below screenshot).


never rerun.jpg










set the distribution points as follows:




and interaction options...




click next through security, summary and progress and close at the confirmation screen after verifying all is ok



Share this post

Link to post
Share on other sites

  • 0

Import computer into the collection


In the Operating System Deployment section, right click on computer Association and choose import computer information, select import single computer




for computername call the computer bacapXP


fill in the MAC or GUID details (or both)




the MAC or GUID can be obtained from the bios screen when the client PXE boots....




click next for the data preview, check for typos


on the Choose target collection screen, click browse and scroll down to our Build and Capture XP collection, select it




review the summary and click next then click close at the confirmation screen



Share this post

Link to post
Share on other sites

  • 0

PXE boot the client and start the deployment


PXE boot your client




Windows PE should start




and the Task Sequence should kick in...




and XP is being installed




after a reboot you'll see some old familiar XP setup screens...






then back to the XP setup GUI




if you get this error




then you'll know that you need to edit your Task Sequence and change the following setting (Apply Windows Settings)




back to the Task Sequence...




Just before running Sysprep, the task sequence will run the 'Install Deployment Tools' section within our Task Sequence and you may see a failure here where you get an error similar to


task sequence failed with the error code 0x00000002


If you get this error then verify the following:


1. you have added the Windows XP network driver for the client's network card as a driver in SCCM and added it to a driver package and added in to the Task Sequence

2. create a distribution point and then updated the distribution point for the network driver package


Once done, re-run the TS and all should be ok.


running Sysprep




capturing the sysprepped XP image to a WIM file and storing it on our SCCM server




After the capture is done, the computer will restart and boot into XP, at this point you now have a captured WIM file with your Windows XP image.


You can use that WIM file to Deploy your XP clients. In other words, you now have a WIM image of a Sysprepped Windows XP installation targetted for the hardware you just ran this on.


You now have the options to


* create a new Operating System Image using this WIM file,. and then create a new Task Sequence for deploying it to bare metal pcs,




* use a Custom Installation DVD.


or deploy this image using imageX or other methods like WDS\MDT, but you really want to use SCCM for this right ? :)

Share this post

Link to post
Share on other sites

  • 0

Please note that all screenshots below here are what your systems will see on first boot after being deployed with the captured WIM we have just created above.




after the computer restarts you'll get the chance to see your sysprep settings...








after a few more screens and one last reboot you'll get to play with your XP SP3 client, if you are left with some drivers not installing correctly then take a look at this post.


Now all you have to do is deploy the image by creating One more task sequence, this time the task sequence will use the Captured XP sp3 image as the operating system image.







If you find the SCCM client is not installed after deploying this image then read this post


You can then install 974571 as the very last step in the TS using for example an install software step. Apparently we’ve seen very similar symptoms a few times now and this resolves.




974571 MS09-056: Vulnerabilities in CryptoAPI could allow spoofing






Share this post

Link to post
Share on other sites

  • 0

Thx for the great tutorial.

Really helped me alot.


Just one question though:

I don't want the system to ask for the regional and language settings and licence agreement etc, I want this in an answer file for an unattended setup.

What is the best way to do this?




Share this post

Link to post
Share on other sites

  • 0

use sysprep to configure all those settings in your image before capturing it


ie: place a file called sysprep.inf with your chosen settings into your Sysprep package for XP,


this sysprep package will be used as part of the build and capture process

Share this post

Link to post
Share on other sites

  • 0

hi anyweb,

i have followed each and every step for deploying windows xp sp2 using SCCM 2007. But when i PXE boot my computer it gave me an error: No boot file name received." so can u tell me where did i go wrong?

appriciate it a lot

Share this post

Link to post
Share on other sites

  • 0

it sounds like your dhcp server is not telling the pxe client where the pxeboot.com file is


so is your dhcp server on the same server as the SCCM server or another one ?, if its on another one you'll need to configure options 60, 66, 67 iirc

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.