SCCM and State Migration point (SMP), USMT Demonstration

http://www.myitforum.com/absolutevc/avc-view.aspx?v=2240

Step by Step 4 part guide to Deploying Windows 7 Enterprise.

Deploy Windows 7 part 1.
Build and Capture
Part 1 is the longest part of the 4 part guide and covers the steps required to successfully Build and Capture Windows 7 RTM. It was tested successfully on both X86 and X64 Enterprise RTM releases.
Step 1. get the ISO
Step 2. Add Operating System Install Package
Step 3. Create Distribution Point for the Image
Step 4. Update Distribution Point
Step 5. Create the Build and Capture Task Sequence
Step 6. Advertise the Build and Capture Task Sequence
Step 7. Add a system to the Build and Capture 7 collection
Step 8. PXE boot the newly added Windows 7 client
Deploy Windows 7 part 2.
Add the captured WIM file
Step 1. Add the Captured Wim file as an Operating System Image
Step 2. Distribute the Captured WIM file
Deploy Windows 7 part 3.
Create a new Task Sequence
Step 1. Create a new Task Sequence
Deploy Windows 7 part 4.
Advertise the Task Sequence
Step 1. Advertise the Task Sequence
Step 2. Last Actions
enjoy !
cheers

OSD Task Sequence : Formatted the drive, dropped the image on the PC

Issue:  When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers.

Looking at the SMSTS.log, the following error is logged:

Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager

Cause:  This issue is caused because the "Setup windows and ConfigMgr" task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence.

The "Setup windows and ConfigMgr" task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared.

Resolution: For these reasons, the "Setup windows and ConfigMgr" task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail.

The "Setup windows and ConfigMgr" task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.

Good Posting for Multicasting for OSD : End to End

you can find here http://tinyurl.com/289ho4y

Multicasting is a new feature of R2 in SCCM and is a welcome addition to the OSD feature.  Multicast allows for image deployment with a much reduced network load.  If, for example, you are deploying a 500 MB image to 20 workstations that have just arrived from the OEM then with normal OSD imaging you would see network traffic equal to around 10 Gig!  Using multicasting would result in a significant decrease in network utilization.  Depending on the configuration, as little as about 500 MB of traffic required to deploy to all 20 machines!  This is the same amount of network traffic you would consume deploying to just a single imaging system using typical OSD imaging before multicast!

How do you setup multicast?  Let's walk through the configuration that is required step by step.

First, we need to enable multicasting.  Multicast requires a distribution point and the 'transport server'  component of WDS installed on a Windows 2008 server.  From there select the properties of the distribution point site system role and make sure the option for BITS, HTTP and HTTPS transfer is selected as shown

Note the new multicast tab that is added when R2 is installed.  Select the multicast tab and enable multicasting.

There are two options when using multicast - autocast and scheduled multicast. 

To enable autocast just select to enable multicast.  In this configuration the multicast session starts as soon as the first machine powers up and requests the image.  As additional machines are also booted up for imaging they will 'join' the current multicast session already in progress and consume the remainder of the stream.  When the stream ends it will start again and the systems that joined late will consume the parts they missed.  While autocasting isn't as efficient as scheduled multicast it is still significantly more efficient that standard OSD image delivery.

Scheduled multicast allows for more control of the multicast session.  Here you choose either a time delay before starting the multicast session or a minimum number of clients that must join the session before it starts.  The multicast session will start whenever either of the two requirements are met.  The idea here is to allow the administrator time to get all of the systems started and ready and then all systems can load the image simultaneously - providing the best usage of network   resources. Scheduled multicast is enabled by selecting the 'enable scheduled multicast' check box.

There are other configuration options on this screen but no extra configuration is required unless by your network.  The 'out of the box' settings work fine for most environments.

In addition, while DHCP and Windows 2008 based WDS (transport component as noted earlier - the PXE boot piece does not need to be on the same server) are needed, there is no special configuration requirement for either to make use of multicasting.

The next step is to configure the image package to be deployed by multicast.  In properties of the imported image, select the 'distribution settings' tab as shown

Select the option to allow the package to be deployed by multicast and optionally select the other two options.  In my testing I tried to select to only allow the image to be transferred via multicast but this didn't seem to work.  When I disabled multicast the image would still deploy, even with this option set.

in addition to enabling multicast for the image, you can also enable multicast on any package that is part of the image deployment.  On each package select properties and then select the 'distribution settings' tab.  the same options are available here as were on the image package as shown

As shown on both the image and the package, multicast is something that takes place in Windows PE only.  So, setting these options per package will not result in the package being delivered via multicast through normal software distribution.

Finally, enable the task sequence advertisement to deliver the image via multicast.  On the properties of the advertisement select the 'distribution points' tab as shown.

To enable multicast MAKE SURE you have selected to 'download content locally when needed by running task sequence'.  This requirement isn't documented and I spent hours trying to understand why my multicast sessions weren't starting up before realizing this setting was required.

Thats it - we are now ready to go for delivering images via multicast.  Let's walk through a couple of scenarios using autocast and scheduled multicast.  In our scenarios we will use PXE booted systems but multicast also works fine when booting from media - the experience is just slightly different when in Windows PE.

Autocast - single machine
To test multicast generally you will use a single machine.  So, what is your indication that multicast is actually working?  When the image begins to deploy you will see that a multicast session is requested, the image is downloaded locally via multicast and then reassembled as shown in the following three screenshots.

Autocast - two machines
As mentioned, in autocast the first requesting machine will start the multicast as shown above.  Any subsequent machines that boot up during the existing multicast session will join in progress and then loop back to the start and request the initial bits again.  The screenshots below show two sysems - the one on the left was started ahead of the one on the right but both are downloading the same image.  The one on the right started mid-stream.

After downloading the image the one on the left proceeds to extract while the one on the right finishes up getting the image. 

Scheduled multicast works similarly except here the multicast session will not start until either time has expired or the minimum number of machines have joined the multicast session.  The screenshot below shows a system waiting for either more systems to join or the timeout to expire.

So, while this is all going on - what is happening in the background to make this all work?  The SMSTS log varies slightly in each scenario but the core details are the same.  The SMSTS log section below is from a machine participating in an autocast multicast session.

In the log snip below we see the imaging system flag the multicast enabled distribution point that it wants to use for the multicast session, construct details for the multicast session request and then send the request to the multicast point

Continuing in the log we see the request information submitted to the multicast point followed by a reply with information the imaging system needs to join the multicast session.  Once we get the proper information back from the multicast point we then request and establish the multicast session

Next we see the response from the multicast server, the session get setup and the download begin

Once downloaded we begin to reconstruct the wim file and start applying the image.

When initially setting up the multicast session we say reference to sending information to the multicast point.  If we look in the mcsisapi log we see the request received, processed and the resulting reply sent back to the imaging agent as shown

There is certainly more 'behind the scenes' detail that takes place but this give a good picture, end to end, of how to configure, use and understand the process of using multicasting in R2.

wds.txt

Option 60: "PXEClient"
Option 66: "2k3-wds.domain.local"
Option 67: "boot\x86\wdsnbp.com"


sysprep -mini -quiet -factory -reboot
c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /shutdown /oobe

Troubleshooting WinPE and task sequence issues

You can troubleshoot some common WinPE and task sequence issues.

WinPE never starts the task sequence

Check the SMSTS.LOG file at X:\windows\temp\smstslog\smsts.log. If a package never downloaded, it is likely that you simply do not have the appropriate network drivers installed, which prevents the machine from communicating with Configuration Manager.

Check your driver catalog to ensure you have the right network drivers available and installed into the boot image, and update the boot image to your distribution points.

Additional network or storage drivers might be needed in the boot image to enable the WinPE boot to function correctly. You should add those through Drivers in the Operating System Deployment node.

The right drivers have been added to the boot image, but are not loading

The original boot.wim file (WinPE boot image) created during Configuration Manager installation is copied and modified with IBM-specific drivers and other files. Your task sequences that use the IBM Deployment Pack must use this boot image or the tools might not work properly.

Check to make sure the image into which you loaded the drivers is the same image being used by the task sequence.

This is a common error for administrators who maintain multiple boot images.

Servers will not boot using PXE

PXE is an extension of DHCP, which uses a broadcast type of communication. Broadcast communication uses standard timeout values that are not readily changeable. As a result, a computer waits for a default timeframe to receive a DHCP or PXE response before timing out and causing a failure condition.

Each time a server is rebooted, it must renegotiate the connection to the switch. Some network switches arrive configured with default settings that might incur connectivity delays. That is, the settings on the switch might cause a DHCP or PXE timeout because they fail to negotiate a connection in time.

One of the features that can be affected by this issue is Spanning Tree Protocol (STP). STP is a protocol that prevents loops and provides redundancy within a network. A networking device using this algorithm might experience some latency as it collects information about other network devices. During this period of information collection, servers might boot to PXE and time out while waiting for a response from Windows® Deployment Services. Disable the STP or enable PortFast on end-node ports for the target server to prevent such occurrences. Refer to the manufacturer’s user guide for further information.

Another feature that can be affected by this issue is the EtherChannel or Port Aggregation Protocol (PAgP). EtherChannel allows multiple links between devices to act as one fast link that shares the load between the links. Running the EtherChannel Protocol in automatic mode can cause a connectivity delay of up to 15 seconds. Switch to a manual mode or turn off this feature to eliminate this delay.

Speed and duplex negotiation can also play a role in negotiation timeouts. If auto-negotiation on the switch is set to off, and the server is not configured to that speed and duplex setting, the switch will not negotiate with that server.

For more information, see the Cisco Web site and the following Cisco documents:

• Cisco: Using PortFast and Other Commands to Fix Workstation Startup Connectivity Delays
• Cisco: Configuring and Troubleshooting Ethernet 10/100Mb Half/Full Duplex Auto‑Negotiation

Default boot order does not allow PXE to boot when a valid drive exists

When an active partition is created on a hard drive, it automatically becomes a bootable device if a valid operating system has been installed. If your PXE NIC is after the hard drive in the boot order, the hard drive tries to boot before PXE and boots to Windows, or causes an Invalid System Partition error if Windows is not installed.

To resolve this issue, be sure that PXE is placed before the hard drive in the boot order. Keep in mind that even if PXE is first in the boot order, the computer does not actually boot to PXE unless Configuration Manager has a task sequence for it to run.

When using a “Reboot” action after initializing an array controller, the task sequence fails

Configuration Manager 2007 does not allow a task sequence to reboot back to PXE. It can reboot back to WinPE or to an installed operating system, both of which require a disk partition and the appropriate installed software.

Without a disk partition, Configuration Manager will fail when attempting to reboot during a task sequence because it expects to copy WinPE to the disk. Additionally, the management point tracks when a machine has booted to PXE to run a task sequence, and once a machine has booted to PXE for a task sequence, it cannot use PXE as a boot method again for that task sequence unless the advertisement is reset.

To perform a reboot to PXE if you need to within a task sequence, use the custom action called “Reboot To PXE." This custom action, written using C# and VBScript, connects to the Configuration Manager 2007 SDK, and contains custom code to drive actions in the admin console as well as the machine being deployed. This custom action performs all the steps necessary to perform the reboot to PXE and allow for proper program flow when it occurs.

The only other way to accomplish a reboot to PXE is to use more than one task sequence, let the computer “fall off the end” of the first task sequence and manually reset the PXE advertisement for the computer.

Task sequence fails with “Failed to Download Policy” and code 0x80093102 or 0x80004005

This error code typically refers to a certificate validation issue.

The SMSTS.LOG file will show an entry with the following text:

CryptDecryptMessage ( &DecryptParams, pbEncrypted, 
 nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=80093102

or

no cert available for policy decoding

Possible causes are:

• Misconfiguration of your domain or a site server, such as DNS not pointing to the site server, or the site server not specifying a valid FQDN (which is referred to by the DNS listing).
  

  If your site server does not specify a FQDN (and only specifies the NETBIOS name), and your DNS server refers to the FQDN, a faulty lookup might cause this error.

  
  
• The certificate being used for PXE and boot media.
  

  Check the certificates under the Site Settings node and see if any certificates are blocked or missing. Open the certificates and ensure that they are actually installed into the certificate store. If not, install them.

If these actions do not work, try removing the package from the distribution point (via Manage Distribution Points) and adding the package again to regenerate the package hash.

Task sequence fails with “Failed to Download Policy” and code 0x80004005

This error code typically refers to a certificate validation issue.

The SMSTS.LOG file will show an entry with the following text:

failed to download policy

Check the certificates under the Site Settings node to if any certificates are blocked or missing. Open the certificates to ensure that the certificates are installed into the certificate store. If not, install the certificates.

Task sequence fails because the package is not downloading

In WinPE, the default option of “Download content locally when needed by running task sequence” will not work. When in WinPE, the task sequence engine will ignore (and fail) all actions that have packages set for this option.

Set all packages needed for use in WinPE to “Access content directly from a distribution point when needed by the running task sequence.”

Task sequence does not run again even after clearing the PXE advertisement

You must set the advertisement to “Always rerun” so that any time you reset the PXE advertisement, the advertisement is applied to the computer regardless of whether it ran the task sequence before.

Task sequences fail or act incorrectly after an upgrade

When upgrading from a previous version of this product, existing task sequences using these custom actions are not automatically updated.

To function correctly, open each task sequence action that uses a custom action in an editor. Add a “.” to the description and remove it to enable the Apply button. Click Apply to refresh the properties of the custom action and save any new automatic data or formatting that is required to function with the new version.

Files and logs are not being returned from the client

A number of issues can prevent the task sequence from returning files or logs from the client.

Among the possible issues that might prevent the task sequence from returning files or logs from the client are:

• Failure of the client-side script prior to the file copy, which is usually evident in the log file.
  

  Repeat the task and press F8 during the task to get to a command prompt, if you selected the check box for Enable command support on the boot image properties > Windows PE page.
  

  Then open the SMSTS.LOG file. The location varies. In WinPE via PXE, the location is at X:\Windows\Temp\Smstslog\smsts.log.

  
  
• Malformed XML in the IBM Deployment Packconfiguration file.
  
• The command being executed actually has an error but exits with code 0.
  

  This can occur when a severe error is encountered in the script while the script is set to ignore errors and use programmatic error handling. Then the error handling did not catch the same error.
  

  Report such issues to the IBM® support site, as described in Getting help and technical assistance.

  
  
• The task sequence cannot access the share or mapped drive that is the target drive for copying the files or logs.

Logs are being returned but not output files

A number of issues can prevent the task sequence from returning output files while allowing the task sequence to return log files.

Among the possible issues that might prevent the task sequence from returning output files from the client are:

• No return file parameters are specified in the configuration XML.
  
• Return file parameters in the configuration XML are incorrect.
  
• An error is occurring with the operation of the utility that generates the output file.
  
• A null variable is causing an error in the file name of the file to be returned.

Task step execution does not automatically change after a change to the configuration XML file

If you change the configuration XML, previously existing task steps do not automatically change unless you edit them.

To fix the existing task steps, open the task sequence editor and make a minor edit to each custom action step in the sequence. You can simply add a “.” to the description and then delete it to enable the Apply button. Click Apply. The task sequence steps are now saved with the automatically updated information from the new XML file.

Task sequence fails at “Apply Operating System” with “Failed to make volume X:\ bootable”

Several problems can cause this error.

This issue is indicated by log content similar to the following text:

MakeVolumeBootable( pszVolume ), 
HRESULT=80004005 
(e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759)

Failed to make volume E:\ bootable. 
Please ensure that you have set an active partition on the boot 
disk before installing the operating system.

Unspecified error (Error: 80004005; Source: Windows)

ConfigureBootVolume(targetVolume), 
HRESULT=80004005 
(e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,326)

Process completed with exit code 2147500037

This issue can be related to two different scenarios:

• If you are using a Format & Partition action in your task sequence to partition the hard drives, make sure that you select the check box for Make this the boot partition on one of the partitions.
  

  If you do not make a drive bootable and the computer has only the single drive, the task sequence engine automatically makes one of the partitions the boot partition. But if there are multiple drives, the task sequence engine cannot determine which drive should be bootable, and you see this error.

  
  
• If you upgraded from the Configuration Manager RTM to SP1, you might have a problem if both hard drives are completely raw. If you have never partitioned the drives, a known bug in Windows PE prevents Windows PE from determining the drive where it was booted, and you see this error.
  

  This situation is likely on a server with a RAID controller where you have just formed two or more RAID sets. The new RAID sets are completely raw because they have never existed before.
  

  The only workaround to the problem of multiple raw drives is to manually boot into Windows PE and run "diskpart" to partition at least one of the drives. Then run the task sequence again. The task sequence should work.
  

  The known problem with Windows PE is fixed in Windows Vista SP1 and hence in the Windows PE that is derived from Vista SP1.

Install Configuration Manager 2007 SP1

Configuration Manager 2007 SP1 includes the SP1 version of the Windows Automated Installation Kit (WAIK). Download and install Configuration Manager SP1 to get the new version.

Upgrading to Configuration Manager 2007 SP1 automatically updates your default boot images, but does not automatically upgrade the IBM boot images.

Upgrade the IBM boot images by rerunning the IBM Deployment Pack installer and selecting “Modify”. You must also update your distribution points so that the new images are used. You should also update the distribution points for the default boot images as well.

The product installer detects the version of WinPE that is currently in use by the default boot images. If the default boot images are not Vista SP1, the product cannot install.

How to tell if your boot images are upgraded to Vista SP1

Boot image properties contain an identifier for “OS Version.”

Perform this procedure to see the version of WinPE in your boot images:

1. Click Computer ManagementOperating System DeploymentBoot ImagesIBM Deployment.
   
2. Right-click the boot image and select Properties.
   
3. Click Images.
   
4. Check the OS Version property for a value of 6.0.6001.18000 or greater.

What to do if your boot images are not upgraded to Vista SP1

You can manually recreate your boot images using the Windows AIK and following the steps listed in Technet: How to Add a Boot Image to Configuration Manager.

If your Configuration Manager processes permit, you might find it easier to remove the old boot image packages using the Admin Console, delete the files in the OSD\boot directories, and rerun the SP1 upgrade installation.

How to tell if WAIK was upgraded to Vista SP1

1. Click Start > Run; then run the Regedit command.
   
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ComponentStudio.
   
3. There should be a single key under this key, which is named with the number of the Windows AIK version.
   

   Note: Only one version of Windows AIK can be installed. However, an uninstall operation might have failed to remove the registry key.
   

   In such a case, the registry key with the highest version number should be the correct version number.

What to do if Windows AIK was not upgraded to Vista SP1

Configuration Manager is supposed to automatically upgrade the Windows AIK version during an upgrade to Configuration Manager SP1. If that did not occur, try manually uninstalling Windows AIK and rerunning the Configuration Manager SP1 upgrade.

To download Windows AIK, see the Microsoft Download Center: AIK page.

System environment variables are not carried over to the next action in the task sequence

When a task sequence runs, commands run in a command shell. When the task ends, so does the command shell environment, which causes the loss of any system variables that are defined in the task.

To pass variables between tasks, set the variables as “Task Sequence variables,” “Collection variables,” or “Machine variables.”

OSD Log Files Location

Unfortunately, the smsts.log can be stored in one of 7 locations, depending on the stage of the build and the architecture of the OS:

• WindowsPE, before HDD format:
        x:\windows\temp\smstslog\smsts.log

• WindowsPE, after HDD format:
        x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

• Full version windows, before SCCM agent installed:
        c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

• Full version windows, after SCCM agent installed:
        c:\windows\system32\ccm\logs\Smstslog\smsts.log

• Full version x64 windows, after SCCM agent installed:
        c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

• After Task Sequence has finished running
        c:\windows\system32\ccm\logs\smsts.log

• After Task Sequence has finished running(x64)
        c:\windows\sysWOW64\ccm\logs\smsts.log

Sysprep parameters

Sysprep parameters

You can use the following optional parameters with the Sysprep command in Windows XP:

• -activated - Do not reset the grace period for Windows product activation. Use this parameter only if you have activated the Windows installation in the factory.
  Important The product key that you use to activate the Windows installation must match the product key that is located on the COA sticker that is attached to that particular computer.
• -audit - Restarts the computer in Factory mode without having to generate new security IDs (SIDs) or process any items in the [OEMRunOnce] section of the Winbom.ini file. Use this command-line parameter only if the computer is already in Factory mode.
• -bmsd - Populates all the available mass storage devices in the [SysprepMassStorage] section.
• -clean - Clears the critical devices database that is used by the [SysprepMassStorage] section in the Sysprep.inf file.
• -factory - Restarts in a network-enabled state without displaying Windows Welcome or mini-Setup. This parameter is useful for updating drivers, running Plug and Play enumeration, installing programs, testing, configuring the computer with customer data, or making other configuration changes in your factory environment. For companies that use disk imaging (or cloning) software, Factory mode can reduce the number of images that are required.
  When all the tasks in Factory mode are complete, run the Sysprep.exe file by using the -reseal parameter to prepare the computer for end-user delivery.
• -forceshutdown - Shuts down the computer after the Sysprep.exe file finishes.
  Note Use this parameter with computers that have an ACPI BIOS that do not shut down correctly with the default behavior of the Sysprep.exe file.
• -mini - Configures Microsoft Windows XP Professional to use Mini-Setup instead of Windows Welcome. This parameter does not affect Microsoft Windows XP Home Edition, where the first-run experience is always Windows Welcome.
  Note that if you plan to use the Sysprep.inf file to automate Mini-Setup, you must either run the Sysprep tool by using the -mini switch, or click to select the MiniSetup check box in the GUI interface. By default, if you do not choose to run Mini-Setup, Windows XP Professional runs the Windows Welcome.
• -noreboot - Modifies registry entries (SID, OemDuplicatorString, and other registry entries) without the computer restarting or preparing for duplication. This parameter is mainly used for testing, specifically to see if the registry is modified correctly. Microsoft does not recommend this option because making changes to a computer after the Sysprep.exe file has run may invalidate the preparation that was completed by the Sysprep.exe file. Do not use this parameter in a production environment.
• -nosidgen - Runs the Sysprep.exe file without generating new SIDs. You must use this parameter if you are not duplicating the computer where you are running the Sysprep.exe file or if you are preinstalling domain controllers.
• -pnp - Runs the full Plug and Play device enumeration and installation of previous devices during Mini-Setup. This command-line parameter has no effect if the first-run experience is Windows Welcome.
  Use the -pnp command-line parameter only when you must detect and install previous, non-Plug and Play devices. Do not use the sysprep -pnp command-line parameter on computers that only use Plug and Play devices. Otherwise, you will increase the time that it takes for the first-run experience without providing any additional benefit to the user.
  Note When unsigned drivers are unavoidable, use the UpdateInstalledDrivers=yes parameter in conjunction with OemPnPDriversPath= and DriverSigningPolicy=ignore instead of the -pnp command-line parameter to provide a more seamless installation.
• -quiet - Runs the Sysprep.exe file without displaying onscreen confirmation messages. This is useful if you are automating the Sysprep.exe file. For example, if you plan to run the Sysprep.exe file immediately after the unattended Setup program finishes, add the sysprep -quiet command to the [GuiRunOnce] section of the Unattend.txt file.
• -reboot - Forces the computer to automatically restart, and then starts Windows Welcome Mini-Setup, or Factory mode, as specified. This is useful when you want to audit the computer and verify that the first-run experience is operating correctly.
• -reseal - Clears the Event Viewer logs and prepares the computer for delivery to the customer. Windows Welcome or Mini-Setup is set to start the next time that the computer restarts. If you run the sysprep -factory command, you must seal the installation as the last step in your preinstallation process. To do this, run the sysprep -reseal command or click the Reseal button in the Sysprep dialog box.

Why is upgrade from Windows XP® to Windows 7 not supported?

Why is upgrade from Windows XP® to Windows 7 not supported?

There are many changes in how PCs have been configured (applets, hardware support, driver model, and so on), and a clean installation yields the highest quality. The User State Migration Tool provides support for moving files and settings, but you must reinstall applications. For a set of customers this tradeoff may seem less than perfect, but the upfront time is well worth it. For more information about this topic, read the blog Engineering Windows 7: Delivering a quality upgrade experience. For more information about how to migrate data from Windows XP to Windows 7, see Step-by-Step: Windows 7 Upgrade and Migration.

 

 

What specific changes are there in Windows 7 compared to Windows Vista that could affect application compatibility?

What specific changes are there in Windows 7 compared to Windows Vista that could affect application compatibility?

Compatibility between Windows Vista and Windows 7 is very high. There are relatively minor changes that affect application compatibility, including the following:

• Operating system version   The internal version number for Windows 7 and Windows Server 2008 R2 is 6.1.
• Removal of Windows gallery applications   Windows Mail, Messenger, Address Book, Photo Gallery, and Movie Maker are deprecated in Windows 7.
• National Language Support changes   The National Language Support (NLS) functions help applications support the different language-specific and locale-specific needs of users. Windows 7 includes some NLS changes.
• Internet Explorer 8 user agent string   The user agent string is the Internet Explorer® identifier that provides data about its version and other attributes to Web servers. Many Web applications rely on the Internet Explorer user agent string.
• Removal of Windows registry reflection for 64-bit operating systems   The registry reflection process copies registry keys and values between two registry views to keep them in sync.
• New low-level binaries   To improve engineering efficiencies, Microsoft has relocated some functionality to new low-level binaries.
• File library replaces document folder   Libraries provide a centralized folder for file storage, search, and access across multiple locations, both local and remote.
• User interface high DPI awareness   The goal is to encourage end users to set their displays to native resolution and to use DPI rather than screen resolution to change the size of text and images.
• Internet Explorer 8 DEP/NX   Internet Explorer 8 enables DEP/NX protection when run on an OS with the latest service pack.

Why is upgrade from Windows XP® to Windows 7 not supported?

Why is upgrade from Windows XP® to Windows 7 not supported?

There are many changes in how PCs have been configured (applets, hardware support, driver model, and so on), and a clean installation yields the highest quality. The User State Migration Tool provides support for moving files and settings, but you must reinstall applications. For a set of customers this tradeoff may seem less than perfect, but the upfront time is well worth it. For more information about this topic, read the blog Engineering Windows 7: Delivering a quality upgrade experience. For more information about how to migrate data from Windows XP to Windows 7, see Step-by-Step: Windows 7 Upgrade and Migration.

Which tools are available to help with my Windows 7 deployment project?

Which tools are available to help with my Windows 7 deployment project?

The following are some of the predeployment and deployment tools that help you automate common project-related tasks:

• Microsoft Assessment and Planning (MAP) Toolkit This tool inventories hardware and devices.
• Application Compatibility Toolkit (ACT) version 5.5 This tool inventories applications, analyzes compatibility, and creates compatibility fixes for applications.
• Microsoft Deployment Toolkit (MDT) This tool helps you create images and automate the OS and application installations, data migration, and desktop configuration process.
• Microsoft System Center This is a family of products for large organizations that provides end-to-end deployment and management support.

During OSD, format first partition only

Our helpdesk asked me to make a task sequence that can be used on computers with more than one partition. In this case, I had to make sure that the operating system will install only on first partition and will not touch the data on other partitions.

To achieve this, I copied another TS and modified the following 2 steps:

• removed any “Format and Partition Disk” step
• in the “Apply Operating System Image” step, under “Select the location where you want to apply this operating system” made the following modifications:
  • Destination: Specific disk and partition
  • Disk: 0 (if all computers are installed on first hard disk)
  • Partition: 1 (if all computers have OS installed on first partition)
    

This way, when TS runs, it automatically wipes partition 1 from disk 0 and will not touch any other partition or disk.

 

 

=============================================================================================

Detailed steps are below…for dummies

Format and Partition Disk:

In SCCM console navigate to Computer Management, Operating System Deployment, Task Sequences. Suppose you already created or imported a new Microsoft Deployment Task Sequence. If not, do it now.

• Select the desired Task Sequence and click Edit in the Actions pane

• In the <Name> Task Sequence Editor window, in the left pane select Format and Partition Disk

• Click the yellow star to add a new partition
• In the Partition name type the name of your system partition, this will be you disk C:
• Under Partition options, select the Partition type as Primary
• Choose how you want to set partition size, use a percentage of all hard disk drive or a fixed value. I use 50% of the HDD size, because not every time I know what HDD size new laptops/PCs will have but for sure it will be more than 80GB
• Check the box to make this partition bootable
• Under Formatting options, choose the file system you want and check the Quick format checkbox (optional) to save time during installation
• Under Advanced options write a Variable name
• Click OK when you’re done making your changes

Now you’ll see this volume in the task sequence editor.

To add another partition click the yellow star again and fill in the following details:

• In the Partition name type the name of your partition, this will be you disk D:

• Under Partition options, select the Partition type as Primary

• To use all the remaining disk space, select “Use a percentage of remaining free space” and set the Size(%) to 100

• Under Formatting options, choose the file system you want and check the Quick format checkbox (optional)

• Under Advanced options write a Variable name

• Click OK when you’re done making your changes

Now you’ll see both volumes in your task sequence editor window. Next time you will deploy an operating system, the hard disk will format and create 2 partitions (C: and D:) and your computer will boot from the first partition (C:).

How does SCCM know that it needs to apply the OS image on the first partition and not the second? Well, it doesn’t, we will set this up in the “Apply Operating System Image” task.

Apply Operating System Image:

In SCCM console navigate to Computer Management, Operating System Deployment, Task Sequences.

• Select the desired Task Sequence and click Edit in the Actions pane

• In the <Name> Task Sequence Editor window, in the left pane select Apply Operating System Image

• If you are installing the OS using the source media, then choose “Apply operating system from an original installation source” option using Browse choose one of the installation packages you have created when making the task sequence

• If you have captured and OS image previously as a .wim file, you can select “Apply operating system from a captured image” option and select the image you want

Check to use a sysprep answer file and select the package using the Browse button

• Now is the time to tell SCCM where you want your image to be applied.

          - To apply the image on a specific partition, under Destination select “Specific disk and partition”. Under Disk select 0 (zero) and under Partition select 1 (first partition). This is the option I use every time
          - To apply the image on the C: partition, under Destination select “Specific logical drive letter”. Under Disk letter select C:

This is it about these two tasks. Of course these tasks can be further customized using the Option tab of each task.

How to create a Windows Image (.wim) file

Method one:- With SCCM build and capture

Method two : WDS capture Wizard

method three: details steps are below

Depending on what you need the .wim file for, you can create it manually or automatically.

- To manually create a .wim file (capture image) you need a bootable CD with Windows PE (with ImageX.exe included) that you can create using Windows Automated Installation Kit.

The basics steps are:

1. Boot your computer using Windows PE disk.
2. In the Windows PE command prompt navigate to the folder with ImageX.
3. To capture the C: partition, use the following example:
   imagex.exe /capture C: D:\CapturedImage.wim “My captured image”

   Where: C: is the partition to be captured; D:\CapturedImage.wim is the place of the captured file; “My captured image” is the name of the file.
   More switches can be found on the ImageX Command-Line Options page.

If you need the image for deployment, do not forget to run sysprep before capturing the image!

- To automatically create a .wim file you can use a capture media created using Configuration Manager.

If you want to capture a Windows XP OS, copy sysprep files to C:\sysprep. Newer operating systems have sysprep files installed by default.

To use capture media:

1. Insert the CD into your CD/DVD drive and shortly autoplay will open Image Capture Wizard.
2. Clicking Next will show you Image Destination page. Select where to save the wim file.
3. On the next page enter some information about the image.
4. On the Summary page click Finish. The task sequence will start sysprep and restart the computer. After restart, the computer will boot to Windows PE and will capture a image of the machine.

Install drivers by computer model using WMI query

When using task sequence, you might want to install different driver packages for different computer models. This can be accomplished by using a WMI query.

First of all you need to have driver packages for all your computer models and know the exact model name for every computer.

To find this, open a command prompt and type WMIC ComputerSystem GET Model (use this command on every computer to find it’s model).

Then, Edit your task sequence. Add how many steps you need with “Apply Driver Package”. Select the driver package you have created for a certain computer model (HP dc5700 in my case).

In the Options tab, click Add Condition and select Query WMI. In the WMI Query Properties window, make you sure you have root\cimv2 as WMI Namespace and write the following query in the WMI Query input box:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%dc5700%” for HP Compaq dc5700 computer models.

Now, for every driver package, replace the model name with the computer model name the driver package is for. This way, the task sequence will install the correct drivers on every computer that will match the model specified in the query and will skip other steps sending the following status message: “The task sequence execution engine skipped the action (HP Compaq dc5700) in the group (Apply driver packages) because the condition was evaluated to be false”.

Install software using Task Sequence

The TS Looks like this… to install software using a TS, is to have only Install Software steps. This way, you can install multiple software products using one advertisement instead of advertising every package. I use this only when I have an OS installed and I want to install software on it.

This is how such a TS looks like:

All the Third-Party Solutions for SCCM & SMS

Web Sites:

MyITForum is the premier online destination for IT professionals responsible for managing their corporations' Microsoft Windows systems; it is especially useful for IT professionals working with Microsoft Systems Management Server. (http://www.myitforum.com)

FAQshop endeavors to provide a "one-stop-shop" for systems management questions, answers, and utilities. (http://www.faqshop.com)

SMS Alliance is a consortium of companies that leverage joint resources to strengthen the capabilities and benefits of SMS. Their mission is to provide organizations with the best-of-breed solutions and services to enhance and extend SMS 2003. (http://www.sms-alliance.com)

1E is one of the founding members of the SMS Alliance, 1E is a company on the cutting edge of systems management. It enhances and extends Microsoft management and deployment technologies, delivering advanced automation and reporting across the enterprise. (www.1e.com)

Macrovision Corporation, another founding member of the SMS Alliance, Macrovision Corporation is a recognized leader in software deployment packaging, software installation, and software updating solutions. They offer one of the best software packaging tools with AdminStudio.
(http://www.macrovision.com/)

PS'SOFT, as a founding member of the SMS Alliance, offers extenders for SMS 2003 that focus on IT asset management. They offer a web-based software cataloging system called SMS Software Requests. (www.pssoft.com)

Vintela, another founding member of the SMS Alliance, Vintela offers a seamless solution to extend security and compliance of Microsoft Active Directory to Unix, Linux, and other platforms and applications. They offer solutions that help IT administrators manage Unix, Linux, and MAC systems using SMS 2003. Vintela is now part of Quest Software. (www.vintela.com)

iAnywhere, the last founding member of the SMS Alliance, iAnywhere offers frontline security and management to SMS and provides extensions to manage your enterprise's mobile and wireless devices through SMS. (www.iAnywhere.com)

AppDeploy is the Internet resource to go to when you need to script or repackage an application for distribution. Among other points of interest at the site is a massive library of applications, sorted by application name and vendor name. For each application listed, you'll find a community-based thread discussing the best practices, links, scripts, and challenges met/overcome with working with the application in regard to installation scripting/repackaging.(http://www.appdeploy.com/)

DesktopEngineer is perhaps one of the best resources in the Windows Installer arena. This site offers a wealth of information on Windows Installer technology, techniques, and troubleshooting tips. I have noticed that he is starting to increase the content related to Microsoft's upcoming PowerShell scripting language. (http://www.desktopengineer.com/)

Tools

SMSView is a utility that is used to extend the functionality of the Microsoft Systems Management Server 2003 advanced client. SMSView allows you to perform the following actions on an SMS advanced client: All nonadmin users to view current mandatory assignments and advertisement status, View advertisement history (past 60 days), View current mandatory assignments, Rerun advertisements, Remote operations (remotely view and manage the SMS client), Display hardware/software inventory status, Display management point/proxy management point, Repair the SMS advanced client. (http://www.smsview.com/)

SMS 2003 Monster MOF is a MOF file that contains several new classes of MOF that will improve SMShardware inventory capabilities. The Monster MOF will enhance inventory data without requiring intimate knowledge of the SMS_DEF.MOF file. (www.smsexpert.com)

SMS 2003 Web Remote Tools assist SMS administrators and allow client administration from a web page. (http://www.myitforum.com/articles/19/view.asp?id=8662)

Corey Becht's Right-Click Tools is one of the best set of tools for all SMS administrators. This tool allows you to right click on any collection or individual PC within the SMS Administrator console and initiate hardware inventory, reassign the site code, restart the SMS Agent Host service, rerun advertisements without modifying the advertisement, perform discovery, initiate software inventory, create file collections, monitor software metering usage, refresh machine policies, evaluate policies, update Windows installer sources,change port number, and change cache size.These tools can run per computer resource or for all the members of a collection.(www.myitforum.com/articles/8/view.asp?id=7099)

Microsoft SMS Toolkit 2: Microsoft released a very nice set of tools for SMS called the SMS Toolkit version 2 . It contains the following tools: IIS Lockdown 2.1 Template, URLScan 2.5 Template, Policy Spy, SMS Trace, Advanced Client and Management Point Cleaner, Advanced Client Spy, Policy Verifier, Send Schedule, Management Point Spy, Set Preferred Distribution Point and CAP, Delete Certificate, Patch Management Evaluation, Delete Group Class, Transfer SMS ID, Package Loader, Management Point Troubleshooter, Client Site Assignment Verifier, Site Boundary Tool, Create Secondary Site Tool, Create SMS Address Tool.(www.microsoft.com/smserver/downloads/2003/tools/toolkit.mspx)

Security Logon Audit Tool (SLAT) extends SMS hardware inventory to include user logon information.This data can be used in web reports and queries. The tool includes the following samplereports: Top users for all systems, User logon information for a specific computer, Systems where the last logged-on user is not the top user, Systems where a specific user has logged on SLAT searches the security event log for the 528 event, which is created when user logon events occur and is enabled via Group Policy. (http://www.systemcentertools)

Enhanced System and User Discovery Tools, out of the box, SMS 2003 does a pretty good job of discovering systems from Active Directory. It's not perfect, though—there are a few gaps in its methods. The Enhanced System Discovery tool, assists in filling these gaps. Out of the box, SMS 2003 does not perform Windows NT 4 domain discovery. This tool solves that by enumerating all machines from a list of NT 4 domains, resolving their IP addresses from DNS or WINS, and creating data discovery records for each system. (http://www.systemcentertools/)

BITS Bandwidth Manager is an SMS Installer script that lets you throttle BITS bandwidthon Windows XP SP2 systems. You do not need to manually adjust any settings. The script takes care of the Registry key manipulation for you.(http://www.myitforum.com/inc/upload/11332BITSManager.zip)

1E SMSWakeUp: this WOL product is able to turn on computers after they have been shut down by users. The wake cycle can be triggered on a regular schedule to power up systems in preparation for the workday, or to perform software deployment activities. (http://www.1e.com/)

1E NightWatchman: Since we are talking about waking systems that have been shut down, it maybe a good practice to examine how best to shut down those systems in the first place. Why dowe want to shut down systems? We do this to enforce reboot cycles and to save energy costs. (http://www.1e.com/)

1E SMSNomad Branch: Some offices may not have the server hardware to allow for a Distribution Point (DP). But those offices may have a substantial number of users and/or be separated from the rest of the network by a low-speed or saturated WAN link, which you would rather not send multiple copies of a package across. SMSNomad Branch acts similar to a peer-to-peer network, allowing other computers to become DPs. If one machine is shutdown, another is selected as the DP. Included in this technology is multicast, increasing its efficiency to reduce network traffic on the local network segment. (http://www.1e.com/)

1E OSD Plus Pack: This is an enhancement to the SMS OSD Feature Pack. It allows you to leverage the SMS OSD Feature Pack in offices that do not have DPs. OSD Plus Pack offers similar functionality to SMSNomad Branch, but also has a few other applications bundledwith it: State Migration Editor, which is an interface for the User State Migration Tool, AppMigrator, which allows the automatic reinstallation of applications after OS imaging, PXE Lite, which is a local PXE server to allow deployment of OS images to bare-metalmachines booted from the network PXE server. (http://www.1e.com/)

SMS Companion 2006: This product provides WOL capabilities, similar to 1E's SMSWakeUp, but leverages slightly different technologies behind the scenes. A key difference is that SMS Companion puts systems in hibernation, rather than powering them off. The following are some of the key applications included with this product:Wake-on-Schedule: Allows clients to come out of a hibernation state. Service Windows: Allows you to restrict the SMS inventory and software distributions from happening during specific time periods, to reduce or eliminate user interruptions. Load Balancing: Allows you to reduce peak network and SMS server loading by making sure that the clients use these resources in a controlled manner. (http://www.smsexpert.com/)

Quest Management Xtensions for SMS: Since Windows platforms are not the only systems in an enterprise, you may need a way tomanage other platforms, such as Unix, Linux, and Mac OS X. These management extensions offer that capability for SMS 2003. One of the unique aspects of this product is its support route: first-level support is handled by Microsoft Product Support Services. (http://www.quest.com/quest-management-xtensions-for-sms)

-------------------
Thanks,
http://sccm07.blogspot.com/

SCCM OSD Error code 80004005

Tasksequence Issue:

In Build and Captured error "Task Sequence Manager could not resume SMS components. code 80004005 TSManager 2/12/2009 12:15:04 AM 1268 (0x04F4)"

Resolution 1:- Make sure in Task Sequese you have joining to Workgroup. Because sysprep can not be make under joining into domain
Resolution 2:- Check your Network desgin if it is build with Cisco then might be Fast Port opened need to stop this to fix it.. Yep I never find this information microsoft site (I ver bad in searching )but this is the solution What i found.

-------------------
Thanks,
http://sccm07.blogspot.com/

OSD error

Current issues which I amruning :)

 

OSD

 

 

 

 

-------------------
Thanks,
http://sccm07.blogspot.com/

SCCM OSD All Log Files

Operating System Deployment Log Files

 

The following table lists and describes the operating system deployment log files.

Log File Name	Description
CCMSetup.log	Provides information about client-based operating system actions.
CreateTSMedia.log	Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
DriverCatalog.log	Provides information about device drivers that have been imported into the driver catalog.
MP_ClientIDManager.log	Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
MP_DriverManager.log	Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
MP_Location.log	Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
Pxecontrol.log	Provides information about the PXE Control Manager.
PXEMsi.log	Provides information about the PXE service point and is generated when the PXE service point site server has been created.
PXESetup.log	Provides information about the PXE service point and is generated when the PXE service point site server has been created.
Setupact.log Setupapi.log Setuperr.log	Provide information about Windows Sysprep and setup logs.
SmpIsapi.log	Provides information about the state migration point Configuration Manager 2007 client request responses.
Smpmgr.log	Provides information about the results of state migration point health checks and configuration changes.
SmpMSI.log	Provides information about the state migration point and is generated when the state migration point site server has been created.
Smsprov.log	Provides information about the SMS provider.
Smspxe.log	Provides information about the Configuration Manager 2007 PXE service point.
SMSSMPSetup.log	Provides information about the state migration point and is generated when the state migration point site server has been created.
Smsts.log	General location for all operating system deployment and task sequence log events.Log file location:·         If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\logs·         If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG·         If task sequence completes when running in WindowsPE: <largest fixed partition>\SMSTSLOG Note <CCM Install Dir> is %windir%\system32\ccm\logs for most Configuration Manager 2007 clients and is <Configuration Manager 2007 installation drive>\SMS_CCM for the Configuration Manager 2007 site server. For 64-bit operating systems, it is %windir%\SysWOW64\ccm\logs.
TaskSequenceProvider.log	Provides information about task sequences when they are imported, exported, or edited.
USMT Log loadstate.log	Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
USMT Log scanstate.log	Provides information about the USMT regarding the capture of user state data.

-------------------
Thanks,
http://sccm07.blogspot.com/

50 steps to deploye XP Sp2 with OSD

 

 

1. Create a network access account, it only need be a domain user and its password should not expire. Add the account to the Computer Client Agent in the Client node under Site Settings
2. Import XP SP2 as an operating system Install Package (Note most common issue here.
3. Add a Distribution point to your new XP SP2 package created in step 1
4. Create the XP SP2 sysprep package in SCCM
5. The Deploy.cab included on the CD was not updated properly for XP SP2 so you must download a new version here.
6. Create a package that points at the extracted CAB file for its source
7. You do not need to create any programs for the package the build task sequence takes care of this
8. Add the package to a DP that can be used during your build
9. Create a package from definition for the Config Mgr Client (a definition is available called "Configuration Manager Client Upgrade" in the create package from definition wizard)
10. Specify always obtain file from source directory
11. Usually here I create a share at \\SCCMSERVER\SCCMClient pointing to \\SCCMSERVER\SMS_XXX\Client where XXX is the site code in order to make it easier for manual installs in the future. Note I also usually grant domain computers read access to the share and directory to prevent permissions problems in the future (Note this last permissions step may no longer be necessary in SCCM but I haven't tested it yet)
12. Update the ccmsetup command line properties accordingly. Extensive information about command line properties on TechNet here.
13. Add the package to a DP that can be used during your build
14. Create a "Build and capture a reference operating system image" task sequence
15. Name the task sequence something appropriate like "Build Windows XP Gold Image"
16. Select a boot image (I suggest x86 as it will run on all platforms, plus you will be booting from PXE so it really doesn't matter)
17. Select the Operating System Package you created in step 1
18. Enter a product key
19. Set the local admin password to blank
20. Join a workgroup
21. Select the Config Mgr client you created in step 4
22. I generally don't install updates in this phase but this is debatable. You must weigh time to deploy if you have to deploy a bunch of updates during deployment time vs. superseded updates and rebuilding your image more often.
23. Don't add any software to the base image
24. Set your image properties
25. Select a location to save the image and make sure you include the full path including the .wim extension
26. Enter an account with rights to write to the share
27. Finish up
28. Change the task sequence to use "Quick Format"
29. Right Click on the Task Sequence and choose Edit
30. Select the "Partition Disk 0″ step
31. Choose properties on the Default (Primary) partition and check the "Quick Format" option
32. Create a collection to which you will advertise the task sequence; I usually use _OSD\Base Builds
33. Advertise the task sequence to the collection you created in step 7 as optional
34. Right click Task sequence and choose advertise, follow the wizard
35. Make sure you select the check box "Make this task sequence available to boot media and PXE"
36. If you are in test and your boundaries are not defined make sure you select "When no local distribution points are available, use remote distribution point"
37. Make sure you completed step 1
38. Select a client to build your base image
39. I suggest using a virtual platform to keep the drivers in the image at a minimum
40. VMWare ESX is not a good candidate as a platform as it uses SCSI disks only to my knowledge. You do not want SCSI Mass storage drivers in your image, use MS Virtual Server / Virtual PC / Hyper-V or VMWare Server / Workstation
41. Ensure that you have the network and mass storage drivers to boot the device on the boot image and in the driver store (If you have to do this in the future you must update the PXE and standard DPs)
42. Add the appropriate boot images (x86 / x64) to the PXE and standard DPs
    1. If you don't see a PXE DP it means you don't have one :), get WDS installed and your PXE Service point
43. Allow the client to boot from PXE
44. If this client previously had an SCCM agent on it you just need to add the client to the collection you created in step 6
45. If this is a new client and SCCM is pre-R2 add the client manually
    1. Add the client by right clicking the Computer Associations node under OSD and choosing "Import Computer Information"
    2. Enter the Name of the computer; I use XPBase
    3. Enter the MAC and or SMBIOS GUID
    4. Add the computer to the collection you created in step 7
46. If you are using SCCM R2 you can enable unknown computer support on the PXE service point but choose wisely; option 10.2 may still be the best choice given the risk of accidentally formatting your CXOs laptop
47. Boot the device up to PXE and choose your task sequence. In less than an hour you should have the start of a great XP Image
50. 
    -------------------
    Thanks,
    http://paddymaddy.blogspot.com/