deploy win 7 refresh fails at GATHER step

[nalinu]

Hi Niall,

 

Firstly thanks for all the great work you have done on WindowsNoob. It's great site and without sites like yours I simply wouldn't have been able to progress with SCCM ( I have attended the MS training course).

 

I wonder if it was possible for you to tell me how I can debug why a Gather step in a OS deployment TS would send the TS to the last step without doing the intervening steps.

 

I am talking about the gather process that happens right at the start. format and partition, Toolkit package then gather. Soon after this the machine doesn't go to the next step but goes straight to the last step which Gather Logs and statestore on Failure. I went through smsts.og but couldn't find the silver bullet.

 

Is there anything else i can do ?

 

Any help would be greatly appreciated.

[anyweb]

I would press F8 and examine both the smsts.log and ztigather.log if that indeed is where it's failing,

i believe you've already solved this though so good work

[nalinu]

Niall requested me to attach the SMSts.log. I thought about the TS and I though I added the following step to it before it all went pear shape.

 

Extract from exported TS.

 

<step type="SMS_TaskSequence_RunCommandLineAction" name="Run Command Line-- CLEAR DISK" description="" runIn="WinPEandFullOS" successCodeList="0 3010">

<action>smsswd.exe /run:WHS00141 cmd.exe /c diskpart /s clear_disk.txt</action>

<defaultVarList>

<variable name="CommandLine" property="CommandLine" hidden="true">cmd.exe /c diskpart /s clear_disk.txt</variable>

<variable name="SMSTSDisableWow64Redirection" property="DisableWow64Redirection">false</variable>

<variable name="PackageID" property="PackageID" hidden="true">WHS00141</variable>

<variable name="_SMSTSRunCommandLineAsUser" property="RunAsUser">false</variable>

<variable name="SuccessCodes" property="SuccessCodes" hidden="true">0 3010</variable>

</defaultVarList>

</step>

 

When I checked this against other TSs that are running, it was not correctly ditributed to the DP. So I changed to a similar script that had been ditributed to the DPs. That got me past the initial issue where it was failing just after the GATHER phase and going right ot the end of the TS and not doing anything in between.

 

Now I have the TS running, but fails in midstreem with 0x80070002 error !.

 

Having said all of the above, The TS seem to be proceeding without problems now.

 

WHY is SCCM so sensitive ?

 

Thanks Niall for your efforts to help the SCCM community. Without the blogs you guys have, Niall, Michael Niehauss, Xtreme deployment, Mark Arwidmark Kent Agerlund etc etc SCCM would have gone to ground long time ago.One simply can't get SCCM support from microsoft.

 

Nalin.