using System Center 2012 Configuration Manager - Part 7. Build and Capture Windows 7 X64 SP1

[anyweb]

have you deployed the task sequence to the Unknown computers collection ?

were there any records in All Systems called Unknown ?

[keywan]

Hi anweb,

 

Could you please help me to resolve my problem.

When I perform a deployment via System Center Configuration Manager 2012 on a client PC(it is a physically Hardware), the PC may boot into WinPE but within a few minutes(by proparing Network Connection), it automatically reboots and does not perform the Task Sequence advertised to the PC, Examining the SMSTS.log obtained from X:\Windows\Temp when the Command Support option is enabled, I see the following error message:

 

Failed to download pxe variable file. Code(0x00000001)

PxeGetPxeData failed with 0x80004005

 

I have the "Intel Network card 82579LM"

 

I get while booting an valid IP-Address from DHCP and it connect to my sccm Server and while "proparing Network Connection", it reboot the PC.

 

Regards

 

P.S: I see in All Systems called x64 Unknown Computer and x86 Unknown Computer, but I see my imported computer named "Windows8build" too!

[anyweb]

press f8 before it reboots, does the client get an ip address ? if not you might need to add network drivers for the network card on that client pc to your boot images and re-distribute them to the distribution points

[keywan]

I did press F8 and type "ipconfig" , it display "Windows IP Configuration". I did add drivers for my NIC into the boot image. If I try after adding drivers into boot image to re-distribute the boot image to the distribution points, it does not display a distribution points. I am going to my boot image-->right click and choose "Distribute Content" and I click on "Add" and choose "Distributions Points", it displayed nothing. Or do you mean I have to go to my boot image-->properties-->Content Location--Redistribute??

 

Could you give me a link how to add drivers into boot image? Is there on windows-noob.com?

 

thanks for help

[anyweb]

once you've added the driver to your boot.wim images you need to Update Your Distribution Points (not add dp's)

 

see the screenshot below..

 

[narcoticmind]

Anyone else experiencing the slowness when using multiple Application Installations on the Build & Capture sequence?

 

More on the topic here: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/1aca7077-2ae0-4c45-9527-88236fd66f29

[hhancock]

I am receiving a Task Sequence error now.

 

"Failed to Run Task Sequence

 

This task sequence cannot be run because the program files for ATL00004 cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator."

 

I have distributed the image installer, the configuration manager client update package, and both boot images to the distrubution point. Do you have to distribute the task sequence to the distribution point too? What am I doing wrong?

[hhancock]

It appears that updating my Boundaries resolved this issue.

[keywan]

Hi anyweb,

 

I did add new drivers to boot image and updated distribution Point". After finshed I got follow error message:

 

Error: Boot image to update:

MDT Custom PE

Error: Actions to perform:

Add ConfigMgr binaries

Enalbe Windows PE command line support

Add drivers

Error: Failed to import the following drivers:

Intel® 82567LM-3 Gigabit Network Connection - Failed to inject a ConfigMgr driver into the mounted WIM file

Error: The wizard detected the following problems when updating the boot image.

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

The ConfigMgr Provider reported an error.: ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

Description = "Failed to insert OSD binaries into the WIM file";

ErrorCode = 2152205056;

File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";

Line = 4104;

ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

Operation = "ExecMethod";

ParameterInfo = "SMS_BootImagePackage.PackageID=\"WES00092\"";

ProviderName = "WinMgmt";

StatusCode = 2147749889;

};

[Oneone]

Hi anyweb,

 

I did add new drivers to boot image and updated distribution Point". After finshed I got follow error message:

 

Error: Boot image to update:

MDT Custom PE

Error: Actions to perform:

Add ConfigMgr binaries

Enalbe Windows PE command line support

Add drivers

Error: Failed to import the following drivers:

Intel® 82567LM-3 Gigabit Network Connection - Failed to inject a ConfigMgr driver into the mounted WIM file

Error: The wizard detected the following problems when updating the boot image.

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

Failed to inject a ConfigMgr driver into the mounted WIM file

The ConfigMgr Provider reported an error.: ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

Description = "Failed to insert OSD binaries into the WIM file";

ErrorCode = 2152205056;

File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";

Line = 4104;

ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

Operation = "ExecMethod";

ParameterInfo = "SMS_BootImagePackage.PackageID=\"WES00092\"";

ProviderName = "WinMgmt";

StatusCode = 2147749889;

};

 

Yes you need to unmount the WinPE img, what you could do is remove the image from your PXE and DP , then add the drivers, then after you have added the drivers you update the dist points with the updated WinPE img.

 

You could also check this post out.

 

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/9d4a42e8-1268-4a65-ba73-d0bdd21a7f43/