Justin Gao Documented how to deploy Win 8 Using SCCM 2012 SP1 Beta as System Center 2012 Configuration Manager SP1 beta Supports now.

In this post , Justin documented how to use System Center 2012 Configuration Manager(SCCM 2012) SP1 Beta to deployment Windows 8 .

    Including these parts:

• Configuring a Distribution Point to Support PXE
• Capturing a Reference Computer
• Preparing the Site to Support Operating System Deployment
• Deploying an Operating System Image to a Bare Metal Client
• Installing the Operating System Image on a Bare Metal System

Complete post and download PDF document step by step,available here

P.S:Please use Adobe Reader X or above version to open !

Via http://blogs.technet.com/b/justin_gao/archive/2012/10/07/how-to-use-system-center-2012-configuration-manager-sp1-beta-to-deploy-windows-8.aspx

Frequently we see some issues with sccm clients when PXE boot for OS deployment with some locations(WDS servers) because of IP helpers and to identify the issue is caused because of this,it took some days because we have to check from server side if there are any issues running around.

When attempting PXE boots via a System Center Configuration Manager 2007 PXE Service Point, PXE boots will initially work and succeed but then all of a sudden stop working.  Examining the server where the PXE Service Point and Windows Deployment Services (WDS) are installed reveals that the Windows Deployment Services Server service has crashed and is in a hung state. Attempting to restart the Windows Deployment Services Server service on the WDS server does not resolve the issue. Restarting both the Windows Management Instrumentation and the Windows Deployment Services Server services or restarting the server may temporarily resolve the problem, but the issue will eventually reoccur and WDS will eventually crash again.

Trying to reproduce the issue by continually attempting to PXE boot PCs reveals that although the issue may happen frequently, the issue cannot be reproduced on a consistent basis and that the crashes will happen randomly.

Examining the WDS server where the ConfigMgr 2007 PXE Service Point is installed reveals the following errors in Event Viewer

System Event Log:
<Date> <Time>  Error         <WDS_Server>    Service Control Manager          N/A             N/A                                The Windows Deployment Services Server service terminated unexpectedly.  It has done this <x> time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

Continue in reading the rest of the post Via http://support.microsoft.com/default.aspx?scid=kb;EN-US;2510665

This is quite simple to create a bootable ISO image to capture winXP or Win7.On the technician computer ,install WAIK tool Downlaod it from here .

1.On technician system launch ‘Windows PE Tools Command Prompt’ from ‘Microsoft Windows AIK’ on the Programs Menu. The entire CD build process is performed in this CMD window.

2.To begin building a Windows PE CD type: copype.cmd amd64 c:\winpe_x64

3.Now mount the Windows PE boot image as a folder on your machine so that it may be edited by typing the following: imagex /mountrw c:\Winpe_x64\winpe.wim 1 c:\Winpe_x64\mount

4.To copy servicing tools into the mounted PE image, type:
xcopy “C:\Program Files\Windows AIK\Tools\Servicing” c:\winpe_x64\mount\Windows /s

xcopy “C:\Program Files\Windows AIK\Tools\amd64″ c:\winpe_x64\mount\Windows /s /Y

5.To commit the changes made to Windows PE, type: imagex /unmount c:\winpe_x64\mount /commit

6.Copy the updated WIM to the ISO folder for creation:
copy c:\winpe_x64\winpe.wim c:\winpe_x64\ISO\sources\boot.wim /Y

7.Create your ISO image:
oscdimg -n -bc:\winpe_x64\etfsboot.com c:\winpe_x64\ISO c:\winpe_x64\winpe_x64.iso

Using your preferred CD creation software burn the disk image c:\winpe_x86\winpe_x86.iso to CD or CD-RW.

when I advertise the TS on computers ,it failes because of various reasons and could not able to identify the reason for the faliure.So i decied to look into the SCCM default report for the particular Task sequence.the report doesnt give you all the full information just the task name where it failed.So later someother day fould an easy way to look into the smsts.log .Whenyou advertise the any Task sequence onto the computers in WIN PE environment ,you may encounter some of the tasks which fails in the begining.How do you identify the reason for the failure of Task.you can do the in the WIN PE session starts.But to view the logs and other stuff ,you should have enable “enable command prompt support (for testing only)” on theboot image that you select in booting up in SCCM.

Once the WINPE session starts ,press F8 and it gives you the command prompt support with the default path like x:\windows

Usually the logs will the stored in X:\Windows\Temp\SMSTSLog\ or C:\SMSTSLog or C:\_SMSTaskSequence.Now i want to see the smsts.log which is present in x:\windows\temp\smstslog.

Type cd temp\smstslog command prompt looks like below now x:\windows\temp\smstslog If you want to open the smsts.log which is present in smstslog folder ,just do notepad smsts.log,it will open the .log file in notepad which is not good to read /identify the errors.Lets move onto the next step by connecting the network share to copy the log files onto.

on the command prompt x:\windows\temp\smstslog  just type net use k: \\192.168.10.15\soft (Where k: drive letter to map and soft is folder on the share to copy the log files) .It prompt you for the use name and password. Provide user name(ex:eskon\xoluser) and password (which is invisble) where xsoluser should have write permission to the above share and eskon is a domian.when you enter the credentials,it gives you maessage connected successfully.In the commnd prompt i.e x:\windows\temp\smstslog type copy smsts.log  K:\ .you will see 1 file copied sucessgully.You can open the smsts.log with trace32.exe which you can get if you install SMS/SCCM tool kit from microsoft.