Hi Mkuriel, You have to enable DHCP in your environment, the following is the requirement to prepare SCCM environment for use with OSD: 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 static 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 scope 2. Enable an Advanced Client Network Access account in the SMS site (will not be required in Configuration Manager 2007 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 retrieval and evaluation processes 3. Create a package to deploy the Configuration Manager 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 point 4. If you want to use USMT to migrate user state information, you must create an Configuration Manager 2007 package for USMT 1. Point the source to C:\Usmt\Bin 2. No program is required, just the package 3. Distribute the package to a distribution point 5. 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-bit 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 interface and tools to update operating system deployment boot images are not present 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.inf 3. If required for troubleshooting, you can modify the boot.wim file to support the command 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 privileges and not something all users should have access to 6. Configure a State Migration 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 processes to store state locally on the system 3. If storing state locally, you cannot format or partition the target system hard drive Preparing the reference system These steps are required to prepare the reference computer for image capturing with OSD: 1. Install the appropriate operating system, service packs, applications, settings, 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 easier especially given that the OSD process completes an installation of the Advanced Client using a package 5. Configure the C:\Sysprep folder on the client 1. Copy sysprep.exe and setupcl.exe to the C:\Sysprep folder 6. Manually sysprep the 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 file 2. Boot the computer with the Image Capture CD 1. This boots WinPE using the boot image selected and added to the Image Capture CD 3. 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 reference system, network, and drive configuration 4. If necessary, rebuild the reference system, as it will now require mini setup to run to configure the system for user utilization Deploying the image in Configuration Manager 2007 These steps are required to use Config Manager to deploy the captured image of the reference computer: 1. Create an OS image 1. Point to the image created from the reference computer 2. Assign the package to a distribution point 2. Create a Task Sequence to deploy use 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 install 3. If necessary, use the ImportMachineEntries.exe utility to create DDRs for systems that are not existing clients (bare metal systems) to prepare the collection for targeting. Refer to the Computer is not found based on SMBIOS UUID only section of the Configuration Manager 2007 Beta Release Notes 1. Use the MAC address as the key value 4. Create an advertisement for the Task Sequence 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 create 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 support removable media i. Click the Action of Create Task Sequence Media ii. Beta 1 only supports CD media iii. Create .iso 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 need to ensure the clients 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 OS image.