Jump to content




Sign in to follow this  
anyweb

how can I deploy Windows Vista SP1 using SCCM 2007 SP1



Recommended Posts

Before starting this part, you should have completed all the steps in Part 1 and Part 2, Part 3 and Part 4 .

 

 

This step is optional * This step is optional * This step is optional

Importing a MDT Task Sequence

This step is optional * This step is optional * This step is optional

 

 

We have already created our build and capture task sequence, however with MDT integration you can create your task sequences using a Wizard by doing as follows:

 

Using a single wizard to create a Task Sequence using MDT integration in SCCM 2007.,

 

in the Operatung System Deployment node, right click on Task Sequence and choose to Import Microsoft Deployment Task Sequence,

 

import_ts.jpg

 

now choose a template, we shall choose Client Task Sequence

 

Note: There are several templates available including

 

Client Task Sequence

Client Replace Task Sequence

OEM Preload Task Sequence (Post-OEM)

OEM Preload Task Sequence (Pre-OEM)

Microsoft Deployment Custom Task Sequence

and

Server Task Sequence

 

 

client_task_sequence.jpg

 

give the task sequence a name and comments...

 

client_task_sequence_details.jpg

 

fill in the workgroup/domain settings and for Capture Operating system image settings, specify the full UNC path (and filename) of where the capture should go

 

\\servername\captures_share\MDTClient001.wim

 

specify the capture account eg: w2k8\smsadmin

 

client_task_sequence_details2.jpg

 

then specify a boot environment (32 or 64 bit, we choose 32 for now)

 

boot.jpg

 

*don't forget to create the MDTfiles share first*

 

For MDT files package, choose Create a new Microsoft Deployment toolkit files package, the wizard will copy the files it needs from MDT and the WAIK. Point to an UNC path

for example

\\servername\MDTfiles

 

mdtfiles.jpg

 

give the MDT source package some info (version/etc)

 

mdt_details.jpg

 

then Specify an OS image setting, as we have already created an OS install package in the previous steps in SCCM we shall choose specify an existing OS install package, click on Browse

 

browse_package.jpg

 

and select the Vista Enterprise Edition package listed.

 

osimage.jpg

 

Next we have to specify a Client Package, and we have already created one so click browse and select Configuration Manager Client Installation package

 

client_package.jpg

 

click next for the USMT settings and click on create New USMT package *will need to have usmt installed first, can be downloaded via mdt in the components section*

 

use the UNC path for PATH to USMT

 

\\servername\USMT301

 

package source >

 

\\servername\USMT

 

usmt.jpg

 

fill in the details to describe the pack

 

usmt_details.jpg

 

 

The Settings Package is needed for the CustomSettings.ini and other such settings, we can create a new package and we'll store it in the predefined share we created earlier called MDTfiles

 

\\servername\MDTfiles

 

settings_package.jpg

 

fill in the descriptive details, eg> MDT Settings File, 1.0, microsoft....

 

settings_package_details.jpg

 

If deploying Windows Server 2008 or windows Vista you won't need to create a sysprep package as that functionality is already built in, however if deploying Windows XP you will need to create a package.

 

We are deploying Vista here so no need for a sysprep package.

 

sysprep_settings.jpg

 

next the wizard will create all the packages/files and once done will import the new Task Sequence into The Task Sequence pane in SCCM OSD.

 

you can now view your task sequence in SCCM/osd/task sequence...

 

post_1_1222768151.jpg

 

you can also view all the packags it's created as part of this process in software distribution/packages.

 

mdt_packages.jpg

Share this post


Link to post
Share on other sites


Add Build and Capture Computer

 

 

Our final task is to add a computer object to the Build and Capture (Vista) collection. To do this right click on Computer Association and choose import computer information,

 

import_computer_information.jpg

 

you can import multiple computers using a file such as a spreadsheet or import a single computer, we will choose the single option.

 

import_single_computer.jpg

 

use the computername BUILDCAPTURE001 and fill in the unique Mac address and GUID for that computer, you can pull those values from the computer itself or from SCCM all systems collection properties of the computer.

 

mac_guid.jpg

 

mac_guid2.jpg

 

mac_guid3.jpg

 

once added, we can then specify the collection we want to add it to, at this point we add it to our Build and Capture (Vista) collection we created earlier,

 

collection.jpg

 

done.jpg

 

 

PXE boot the client

 

At this point we can PXE boot our client computer to build and then capture our Windows Vista SP1 image, if PXE boot fails verify that the WDS service is started and verify that you entered the MAC and GUID values correctly

 

properties.jpg

 

you can right click the collection and choose clear last pxe Advertisement,

 

clear_last_pxe.jpg

 

in addition you might consider checking/setting the following registry key for cache delay otherwise you'll get an error such as

 

"TFTP Download smsboot\x64\abort.pxe"

"PXE Boot aborted"

 

adjust following reg Key to 300 (5Min) helps us to solve our issues in the Lab environement:

 

HKLM\Software\Microsoft\SMS\PXE\CacheExpire

Dword : default is 3600 seconds (if nothing is set)

 

Once PXE boot is working correctly you should see it do this

 

pxe_boot.jpg

 

then Windows PE will start to load

 

pxe_boot2.jpg

 

remember the background LOGO we customised earlier ? here it is....

 

windowspe.jpg

 

and the Task Sequence (Build and capture) is now beginning...

 

task_sequence.jpg

 

at this point you can take a well deserved break as this process will take quite a bit of time.

 

vista_setup.jpg

 

after a while the computer will reboot then continue with setup

 

vista_setup1.jpg

 

the Task Sequencer takes over again and here you can see it installing our chosen application (Firefox)

 

firefox.jpg

 

another reboot (this reboot is needed to make sure there are no locked files for the Capture process)

 

reboot.jpg

 

now the capture begins...

 

capture.jpg

 

creating WIM file and copying it to the server (this takes time)

 

capture2.jpg

 

all done !

 

capture_complete.jpg

 

at this point you now have the Captured build stored in

\\servername\captures

and it is this WIM file that we shall be using to Deploy Vista clients in the next and final part.

 

done.jpg

 

 

Continue on to Part 6

 

 

 

 

digg it !

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×