Not able to build and capture a Win7 computer

[Balthier]

Hello guys, I am not able to run a Build and Capture Task sequence successfully. There are no drivers included, and I use the boot image called Boot Image (x64) version 6.1.7600.16385
I am running Sccm2007SP2 with R3 installed. Here is what I do step by step

 

1. Create a package for the SCCM client (I select the default options unless otherwise stated)

 

 

 

 

Then I create a Task Sequence

 

 

 

Then I advertise the task sequence, and pxe boot a computer (I am using Hyper-V). After a while the task sequence stops with the following error

 

 

Where do I go wrong? Which log files can I check?

[Balthier]

I do provide a product key (I have just not included that in the picture posted about), and the Task Sequence always stops at the Setup Windows and ConfigMgr part.

[Rocket Man]

Does configuring the configMgr client properties to the actual FQDN help any? i:e

 

SMSLP=Server01.local; SMSMP=Server01.local

 

Also you could try and use an x86 boot.wim image instead of the x64 boot.wim!

 

Your selected configMgr client in your TS above is the one you created from definition??

[Balthier]

Does configuring the configMgr client properties to the actual FQDN help any? i:e

 

SMSLP=Server01.local; SMSMP=Server01.local

 

Also you could try and use an x86 boot.wim image instead of the x64 boot.wim!

 

Your selected configMgr client in your TS above is the one you created from definition??

Yes, the selectd configMgr client package in the TS is the one I crated.

 

If I am going to deploy an x64 Win7 image, shouldn't I then select the x64 boot.wim?

 

Btw, which log file can I take a look at, to see why and where it stopped?

[Balthier]

Well I tried changing to FQDN and x86 boot image, former gave the same result as earlier, while the latter had it stop at an earlier stage (Apply OS stage).

[Rocket Man]

The smsts.log is the log that you should be looking into.

 

You can deploy an x64 OS image with an x86 boot.wim.........but apparently not the other way around. I also read somewhere that if you are deploying custom built OS images then you should only use a 32bit boot.wim........if it is a x64 OS from an OS installer package then you use the x64 boot.wim!

 

Yes, the selectd configMgr client package in the TS is the one I crated.

 

 

 

BTW you have distributed this package and it is has been configured to copy to content share on your DP(s)?

 

Rocket Man

[Balthier]

Yes it has been distributed. Where can I find the smsts.log?

[Rocket Man]

Below are the locations the log file will be in depending on what stage the TS is at:

 

 

During OS Deployment

 

Before your hard drive is formatted and partitioned

X:\windows\temp\smstslog\

 

After your hard drive is partitioned formatted

X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\

 

Within Windows

Within Windows before the SCCM agent is installed:

C:\_SMSTaskSequence\logs\smstslog\

 

Within Windows after the SCCM agent installed:

C:\windows\system32\ccm\logs\smstslog\

 

When the Task Sequence completes on a x86

C:\windows\system32\ccm\logs\

 

For x64 Systems

C:\windows\SysWOW64\ccm\logs\

 

You will need to enable your boot.wim with f8 support to retrieve the log if it bombs out before apply OS stage so that you can bring up the command prompt and copy the log to a share on the network.

 

Considering your TS is bombing out after the OS is applied but before the installation and initialisation of the agent then it should be in the latter of locations mentioned above!

 

Good Luck!!

[Rocket Man]

Just a thought also have you configured your Network Access account....looking at your failed snippet I see it has an error of 0x80004005........this could be the fact that the system is unable to get the data from the shares!!

[Balthier]

My network access account is set as Administrator, so that should be fine. I'll try to check the log this time, just have to wait for the TS to fail first (my lab computer is quite slow, an old Dell T105).

 

Thanks for your input so far, really appreciate it.