Implementing Configuration Manager 2007 (SMS V4) OSD

http://blogcastrepository.com/blogs/brian_tucker/archive/2006/07/11/1680.aspx

These steps are required to prepare the Config Manager environment for use with
OSD:
1.Enable DHCP (will not be required in Configuration Manager 2007 Beta 2 as stat
ic IP addresses will be migrated to WinPE)
1.Create a scope with available addresses
2.Enable the DNS scope option
3.Authorize the server and Activate the scope2.Enable an Advanced Client Network
Access account in the SMS site (will not be required in Configuration Manager 2
007 Beta 2)
1.Create the account in Active Directory, configure the account in Configuration
Manager 2007, and implement the account on the client through normal policy ret
rieval and evaluation processes3.Create a package to deploy the Configuration Ma
nager 2007 client
1.Use the built in package definition file (SMS Advanced Client Upgrade)
2.Point the source to \\mpcomputer\smsclient\i386
3.Assign the package to a distribution point4.If you want to use USMT to migrate
user state information, you must create an Configuration Manager 2007 package f
or USMT
1.Point the source to C:\Usmt\Bin
2.No program is required, just the package
3.Distribute the package to a distribution point5.Distribute the boot image you
want to deploy to a distribution point
1.Ensure you distribute the correct boot image there are default images for 32-b
it and 64-bit systems you must use the correct one J
2.If you need to add additional drivers to the boot.wim file, refer to the User i
nterface and tools to update operating system deployment boot images are not pre
sent in Beta 1 section of the Configuration Manager 2007 Release Notes
1.You need to run the modifybootimage.vbs script to add drivers
2.cscript modifybootimage.vbs c:\sms\osd\boot\i386\boot.wim c:\driver1.inf3.If r
equired for troubleshooting, you can modify the boot.wim file to support the com
mand shell, which is useful to gather log files (if necessary)
1.cscript modifybootimage.vbs c:\sms\osd\boot\i386\boot.wim /debug:true
2.This is normally only required when troubleshooting image capture issues, and
is not normally recommended, as the command shell is running with admin privileg
es and not something all users should have access to6.Configure a State Migratio
n Point site system
1.This is not required if you are not migrating user state
2.This is required unless you manually configure the state capture and restore p
rocesses to store state locally on the system
3.If storing state locally, you cannot format or partition the target system har
d drive
Preparing the reference system
These steps are required to prepare the reference computer for image capturing w
ith OSD:
1.Install the appropriate operating system, service packs, applications, setting
s, etc.
2.Configure the reference system to be a member of a workgroup
3.Reset the admin password to be blank
4.Remove the Configuration Manager 2007 Advanced Client from the system
1.This is not a hard requirement, rather a suggestion. It makes the process easi
er especially given that the OSD process completes an installation of the Advanc
ed Client using a package5.Configure the C:\Sysprep folder on the client
1.Copy sysprep.exe and setupcl.exe to the C:\Sysprep folder6.Manually sysprep th
e client
1.Run sysprep mini quiet reseal -reboot
2.This can be automated with a Task Sequence
Capturing an image of the reference system
These steps are required to image the reference computer:
1.Create an Image Capture CD
1.Point to the appropriate boot image (modified one if available)
2.Create CD from the created .iso file2.Boot the computer with the Image Capture
CD
1.This boots WinPE using the boot image selected and added to the Image Capture
CD3.Capture an image using a capture CD
1.Point to the shared network folder to store the image to
2.This process will take a number of minutes to complete depending on the refere
nce system, network, and drive configuration4.If necessary, rebuild the referenc
e system, as it will now require mini setup to run to configure the system for u
ser utilization
Deploying the image in Configuration Manager 2007

These steps are required to use Config Manager to deploy the captured image of t
he reference computer:
1.Create an OS image
1.Point to the image created from the reference computer
2.Assign the package to a distribution point2.Create a Task Sequence to deploy u
se the OS image and use the boot image
1.Select Install an existing image package option
2.Select the appropriate boot image
3.Select the appropriate image package
4.Select the appropriate client installation package and program
5.Designate the domain (and optionally the OU) or workgroup to join
6.Designate the account to use to add the system to the domain
7.Configure default admin password behavior (static or random)
8.Enter the product key for the operating system to be deployed (with dashes)
9.Configure state migration settings (USMT package and whether or not to capture
user state, network, Windows and SMS client settings)
10.Configure software updates implementation (not enabled for beta 1)
11.Configure any additional software distribution programs to install3.If necess
ary, use the ImportMachineEntries.exe utility to create DDRs for systems that ar
e not existing clients (bare metal systems) to prepare the collection for target
ing. Refer to the Computer is not found based on SMBIOS UUID only section of the C
onfiguration Manager 2007 Beta Release Notes
1.Use the MAC address as the key value4.Create an advertisement for the Task Seq
uence to a target collection
1.Select the Task Sequence and then click Advertise in the Actions pane
2.Configure the target collection
3.Configure whether or not to make the Task Sequence on a boot media
i. You then need to crea
te a Task Sequence Media to run remotely
1.Configure the advertisement schedule
2.Configure content access from distribution points (download before execute or
run from DP) and whether or not it is available to be accessed from unprotected
or only protected distribution points
3.Alternately, this can be a removable media Task Sequence if configured to supp
ort removable media
i. Click the Action of Create Task Sequence Media
ii. Beta 1 onl
y supports CD media
iii. Create .is
o file
iv. Select boot
image
v. Configure
password protection (if desired)
1.Run the advertisement on the client
1.Alternately, boot off the removable media and deploy the image
2.If performing the default content access of Download before execute , you will ne
ed to ensure the client s cache size has been increased. The default cache size of
250MB will not be large enough to download Boot.wim and the .wim file for the O
S image.