using SCCM 2012 in a LAB - Part 7. Build and Capture Windows 7 X64

[PolishPaul]

Hello and thank you for your tutorials.

I'm getting stuck on the Task Sequence after PXE booting. I enter my password and get the 80004005 error.

 

Here's what I'm doing:

I'm using Hyper-V 2008R2, created a virtual machine and i'm able to network boot.

I'm unable to interrupt the bootup with F8.

Once the PE is initialized, it asks for my password. After typing it in, it fails.

 

I can't see anything in the SMSPXE.log logs about that issue.

 

Kinda stumped here. I've been reading this forum post's replies and trying what i can, but no luck so far. This looks like a permissions issue?

 

EDIT:

I enabled Command support on the x64 package and was able to get to the smsts.log. Turns out I'm having the same issue as lishi. The virtual machine is getting DHCP from my router and not the DC. I'm going to have to figure out how to have it poll the DHCP from my DC.

 

EDIT 2:

So yes, my VM is getting my router's DHCP settings. I edited the hosts file in the PE environment (notepad x:\windows\system32\drivers\etc\hosts) and punched in the hostname of my SCCM server.

 

Does anyone have any suggestions on how to run this in a lab so that I'm picking up the right DHCP/DNS server? The Hyper-V server is on a standard home internet connection.

Edited March 2, 2012 by PolishPaul

[PolishPaul]

New problem. The Task Sequence: build and capture Win 7 x64 has failed with the error code (0x00000002).

 

[anyweb]

what does your smsts.log file say about the error ?

[boyjaew2]

what does your smsts.log file say about the error ?

 

I am having the exact same problem. I believe, even though I have added the correct drivers to the boot image I am loosing my NIC sometime before this part of the task. I quick look at the log (which I can admittedly barely make sense of) the first error I see is this:

 

==========[ TsProgressUI started in process 2940 ]========== TsProgressUI 3/2/2012 3:06:15 PM 2420 (0x0974)

Command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE TsProgressUI 3/2/2012 3:06:15 PM 2420 (0x0974)

Registering COM classes TsProgressUI 3/2/2012 3:06:15 PM 2420 (0x0974)

sbModulePath = C:\Windows\CCM\TsProgressUI.exe TsProgressUI 3/2/2012 3:06:15 PM 2420 (0x0974)

Unregistering class objects TsProgressUI 3/2/2012 3:06:15 PM 2420 (0x0974)

Shutdown complete. TsProgressUI 3/2/2012 3:06:15 PM 2420 (0x0974)

Process completed with exit code 0 TSMBootstrap 3/2/2012 3:06:15 PM 868 (0x0364)

Successfully registered TS Progress UI. TSMBootstrap 3/2/2012 3:06:15 PM 868 (0x0364)

No valid network adapter found. TSMBootstrap 3/2/2012 3:06:15 PM 868 (0x0364)

 

It's seems that after the OS installs the NIC and Storage drivers are no longer there. One question I have is how does the task keep running if it looses network? Is it running from the host at this point? And, how do I get the drivers to "stick"? Where the heck are they going?

[anyweb]

are you applying any network drivers in an apply driver package step ? what hardware is this ? virtual ?

[boyjaew2]

I do have an "Apply Device Drivers" step in my task sequence as part of "Build the Reference Machine".

 

It is physical hardware - laptop HP 8560w - I have included just the x64 drivers for Intel 82579LM NIC, ESB2 SATA AHCI Controller and ESB2 SATA RAID controller.

 

Just after booting into win pe the drivers are there, verified with ipconfig and diskpart from CLI, but sometime before the image can be captured, post OS installation, I no longer have network.

[PolishPaul]

<![LOG[Failed to set log directory. Some execution history may be lost.
The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="14:18:09.390+300" date="03-02-2012" component="OSDSetupHook" context="" type="3" thread="832" file="osdsetuphook.cpp:192">
<![LOG[Executing task sequence]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="osdsetuphook.cpp:277">
<![LOG[Task Sequence environment not found.  Task sequence completed in Windows PE.]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1291">
<![LOG[uninstalling Setup Hook]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1427">
<![LOG[Removing setup hook from registry.]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="0" thread="832" file="vistasetuphook.cpp:143">
<![LOG[successfully removed C:\Windows\system32\OSDGINA.DLL]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1183">
<![LOG[successfully removed C:\Windows\system32\OSDSETUPHOOK.EXE]LOG]!><time="14:18:09.546+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1183">
<![LOG[successfully removed C:\Windows\system32\_SMSOSDSetup]LOG]!><time="14:18:09.562+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1220">
<![LOG[successfully finalized logs to SMS client log directory from C:\Windows\CCM\Logs]LOG]!><time="14:18:09.578+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="tslogging.cpp:1542">

This is the smsts.log on the win7 machine.

 

EDIT:

So i went through all the settings once more and (as usual) i made a mistake. In Step 6. Create the Build and Capture Task Sequence, i pasted in the line SMSMP=sccm.server2008r2.lab.local without updating it to my domain! <facepalm>

 

Looks like the capture is working this time around.

Edited March 5, 2012 by PolishPaul

[boyjaew2]

Hmmm...that's interesting. Did you point it to your wsus server. I thought I did the same thing, but when I updated the string I still had no luck. Would you mind posting an example of how you formatted the string in your case? I did mine this way:

 

SMSMP=myWsusServer.mydomain.com

 

Does that look incorrect?

[ski_bum2010]

I am having some trouble with the PXE Boot. It seems like it boots into PXE just fine but it reaches "Preparing Network Connections" and then restarts. I am not sure what I did wrong. I have deleted and readded the distribution point. I have tried to press F8 when I get into Windows PE to get the command prompt but nothing comes up and it restarts. I have also verfied that "Enable command support" is enabled. Is there anything else I can try? I can't even get in to look at any log files on the the client because it restarts before it gets to anything. I appreciate the help.

[ski_bum2010]

So I got PXE Boot to work. I had downloaded the bit drivers .cab file from Dell and thought that this would have the network drivers. Apparently not. So I just got the straight drivers from dell and I think that did the trick. There was also some drivers that were not letting me update the Boot Images on the distro point so I removed those. Now however when I get to the Task sequence it almost immediently fails saying " This task sequence cannot be run because program files for DBU00004 cannot be located on a distrobution point" Any ideas on this one?