Not able to build and capture a Win7 computer

[Balthier]

My keyboard layout while inserting the password for the Network Access Account is not US, while the Keyboard layout for the WinPE in the Task Sequence is US. Could that cause the Network Access account to fail?

 

Because when I tried to connect to Server01 (which is my All in One server) I received an error

 

I wrote

 

net use u: \\server01\images$

 

The error I received

 

The password is invalid for \\server01\images$

 

Then I had to enter credentials, user name first, and password afterwards. At the end I was able to connect to SERVER01 and upload smsts.log (which was in C:\_smsTaskSequence\Logs"

 

Here is its content

 

http://s22.postimg.org/omsf2h8a9/image.png

 

Can't say it tells me much at the moment.

[Rocket Man]

So you are using a pysical machine for testing purposes??

Have you attached the correct driver bundle specifically the network driver??

 

There are alot of errors in that snippet stating that it cannot find the appropriate drivers to match your systems hardware.

 

If the system has no active NIC then how can the device find the content share where the client package is if it does not have a network driver installed after the OS is applied??

 

Have you started the machine into windows after the client has failed? Does it have an active NIC??

[Balthier]

Its not a physical machine, both are Hyper-V guest machines.

Server01 is an all in one server

Client02 is the client

 

I have not attached any drivers, because I have tried to run this task sequence before, but it failed at the same stage as it is failing now, so I figured it might have something to do with wrong drivers being added to the boot image, so I removed all drivers.

 

If I try to boot the machine after the TS has failed, I get the following error message BOOTMGR is missing.

 

So apparently it has not installed the OS properly, before it fails. I created the OS install package during the Create Microsoft Deployment Task Sequence Wizard (I have integrated MDT2010 with SCCM), but even then it would stop at the same point. So now I am trying to run just a generic SCCM TS, without involving MDT.

 

Should I add the Hyper-V drivers?

[Rocket Man]

There should be no need to add hyper-v drivers......the only drivers I ever inject into the boot.wim where the Dell winPE3.0 or 4.0.....and the very odd network driver for rare models.

 

Can you try and deploy a standard deploy TS(not B&C) and attach a windows7 or windows8.wim directly to it to see if this has a different outcome. It could be the OS installer package you have created that may be corrupt so then....

 

It is an OS installer package you have created for the B&C process?