[anyweb]

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,



on the configure networking screen decide whether you want to join a domain or not



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

eg:

\\WIN-AE2V1IRN067\captures\xpsp3r.wim

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



click next, next and close at the confirmation screen

[anyweb]

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.

[anyweb]

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




Schedule

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 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.




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











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

[anyweb]

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

[anyweb]

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

Quote

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,

or

* 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 ?

[anyweb]

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

Quote

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

http://support.micro...kb;EN-US;974571

cheers
anyweb

[blackout]

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?


Thx

[anyweb]

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

[ssjacky]

Great work........

please upload more tutorials on SMS, SCCM 2007 ...
Thanks

[infotech]

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

[anyweb]

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

[infotech]

anyweb, on Jun 15 2009, 01:37 AM, said:

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

Thanks, anyweb for ur help
First to explain the network settings the dhcp server and SCCM are on a separate sever. So, i have only configured option 66 (boot server host name) on my dhcp server. Option 60 is not available on my dhcp server. I don't know why? I tried to configure option 67 but i don't know which entries to insert on the string value. so can you please tell me that too?
Additional information:
the dhcp server and SCCM are on different vlan than the pxe client.

Thank you very much in advance!

[infotech]

Hi,

yesterday after i only configured option 66 on my other dhcp server, when i boot my pxe client from the network the dhcp server gave an IP address, sub mask and gateway to the client computer. After that it displays the following error messages
1. TFTP error: file not found
2. PXE-T01: file not found

My guess is i didn't configure option 67 with the boot file name string. I use this guide to configure my SCCM server and could you please help me what is the string that i am suppose to enter in option 67? If my guess is wrong, what will be the cause for displaying those errors?

Appricated it a lot!

[anyweb]

take a look at this post, it should give you some ideas

[dgunz]

Quick questions for this type of deployment. The purpose of this deployment is to install and later caputer the image that was just deployed and copy it back to the server.
Now if you do that, you will only be able to use that image on one TYPE of hardware pc only because of the different (HAL) Hardware Abstraction Layer and so on.
Is it possible to use that deployment to just install the operating system without capturing it later. I just want to deploy the operating system to multiple computers regardless of the hardware they are running, I want a gold image in other words. This process could install the base operating system regardless of hardware and later I can just create task sequences to deploy Software installations on the computer.

The computer you used to deploy the Windows xp Sp3 files, was that a barebone machine without an OS. Please share your thoughts on this and what could be the best solution. Thanks in advance.

[anyweb]

yes its possible, just disable the entire capture portion of the task sequence,

btw you can customise the hal as well, look for a post about that right here

http://www.windows-n...p?showtopic=574

[dyos]

Thanks for this excellent post as it has gotten me to successfully replicate what you have done. One question I do have. Let's say after I deployed this OS I want to go in and add some applications change some backgrounds add customized features etc. What is the process of modifying the image then just doing a sysprep and capture as to save all my changes? Can you provide me with a broad overview? Thanks in advance I really appreciate it.

[anyweb]

to change it you would place the image back on the machine it was created on, make the changes you want, re-sysprep it and capture it again, but remember you shouldn't sysprep an image more than three or so times

the other alternative is to use imagex to mount the WIM file and edit it directly, but that is more advanced

cheers

[dyos]

anyweb, on Jul 1 2009, 10:12 PM, said:

to change it you would place the image back on the machine it was created on, make the changes you want, re-sysprep it and capture it again, but remember you shouldn't sysprep an image more than three or so times

the other alternative is to use imagex to mount the WIM file and edit it directly, but that is more advanced

cheers

You say you will only want to sysprep 3 times or so? I've never heard this before. What are the reprucussions of Sysprepping a machine too much?

[anyweb]

see here