Hello,

The Task Sequence that was deploying W7 with SCCM 2012 SP1 has stopped to deploying the Lenovo X240 laptop.

The Laptop must load WinPE on Workgroup & PXE

When I get on F8 to get an ipconfig, nothing but the message "configuration IP" is dysplayed, then WinPE reboot.

I don't know if the laptop has joined the workgroup

The smsts.log show 2 main errors :

Failed to download pxe variable file. Code(0x00000001) TSPxe 24/07/2015 16:09:06 1176 (0x0498)

PxeGetPxeData failed with 0x80004005 TSPxe 24/07/2015 16:09:06 1176 (0x0498)

RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 24/07/2015 16:09:06 784 (0x0310)

GetTsRegValue() failed. 0x80070002. TSBootShell 24/07/2015 16:09:06 784 (0x0310)

The driver are the following : SCCM package for Windows 7 (32-bit, 64-bit) - ThinkPad X240, X240s

Please, Help me.

• Edited by PascalC93 Tuesday, July 28, 2015 11:35 AM
• Moved by Emile SupiotMicrosoft contingent staff Wednesday, July 29, 2015 9:08 AM written in English

Hi,

Since you cannot even get an IP address, that should be a driver issue.

Please find NIC driver applied to your computer model and import into win PE 

Thanks for reply,

It seems to evolved to a compatibility issue because when I try a ipconfig /renew, I get the following message :

 

The operation failed as no adapter is in the state permissible for this operation.   With the following preconization :   WinPE 3 = Drivers Windows 7
WinPE 4 = Drivers Windows 8
WinPE 5 = Drivers Windows 8.1   I have tested the following configuration without succeed :   - SCCM 2012 SP1, - Boot Image x64 4.0 / WinPE 6.2.9200.16384 / Driver SCCM Lenovo X240 for Windows 8 x64,

- TS W7 x86 / drivers SCCM Lenovo X240 for Windows 7 x86.

 

Any more advice, please ?

You've completely ignored what Daniel said above. You don't need additional advice, you need to add the correct drivers to your *boot image* for the device type you are PXE booting.

Of course ipconfig /renew is not going to work if the correct driver is not loaded.

Of course, I allready done what Daniel adviced.

The following configuration lauch WinPE but not the TS.

- SCCM 2012 SP1, - Boot Image x86 4.0 / WinPE 6.2.9200.16384 / Driver SCCM Lenovo X240 for Windows 7 x86,

- TS W7 x86 / drivers SCCM Lenovo X240 for Windows 7 x86.

That's why I decided to work on the version of the Boot Image & the version of the WinPE Kernel, based on the following lynk : http://mistype.reboot.pro/mistype.docs/readme.files/winpe.htm

But, No succeed...

Please, keep share you're experience on that topic

The version of the boot image is irrelevant. This is a driver issue; specifically, the boot image does not have the correct driver in it.

What exactly did you do?

Are you testing the driver in WinPE using drvload to validate it? Just because a driver is in a driver pack from a vendor does not make it the correct driver?

You have to give us technical details of what you are doing and what you have done, not just "it doesn't work" as that doesn't help us help you at all.

I deploying a W7x86 TS on Lenovo X240 with the x86 type of Drivers :

http://support.lenovo.com/us/en/downloads/ds038819

I add the drivers with the SCCM 2012's Image Boot dialog box / Driver Tab dedicaded for...

Please, give your opinion

What you have above are not details -- all of them. I have no idea what exactly you are doing -- you need to provide actual details of what you are doing, I don't have a crystal ball to see what you are doing explicitly.

Same answer though, just because yo loaded drivers from the vendor, doesn't make them right.

Also, are you adding all of the drivers from the driver pack to the boot image? If so, that is very bad. You only need to add NIC drivers (and sometimes storage drivers) to boot images.

Finally, did you update the DPs with the updated boot image after injecting the drivers? If you are using boot media, to you re-create the boot media? Are you sure your task sequence is set to use boot mage you are updating?

Did you update the boot image to the DP's after injecting them?

Of course, I did.

I think that the fact that Lenovo don't provide a Driver Pack dedicaded for the Lenovo X240 for a Boot Image 4.0 x64 / WinPE 6.2 matter, but I'm not enough experienced for validating.

cf : https://support.lenovo.com/us/en/documents/ht074984

Now, my question has evolved in "Do you know the recipe of the drivers to select for a Boot Image 4.0 x64 / WinPE 6.2 ?"

I heard said that those drivers can be differents than those of the OS pack...

Best Regards

There is no "recipe" per se, but first, you only ever need to inject NIC drivers into boot images (and sometimes storage drivers) and then only if the boot image doesn't already contain a suitable driver. Thus, you need to test the boot image on a device before injecting anything and then only inject the NIC driver if you lack network connectivity (or a storage driver if you lack storage connectivity). That's it. The drivers in the boot image have *nothing* to do with the OS or image being deployed.

Concerning the X250 Lenovo deployment the situation is as following :

- I have reconfigured my Boot Image 4.0 x64 / kernel 6.2 & accessed the test support,

- I make sure that the network drivers was adapted, as get a TCP IP configuration,

- I make sure that the mass storage drivers was adapted, as I can access to the diskpart commands,

- I ping my MP with success

- I ping my DP/PXE with success

 

But the problem remains the same as the X250 always reboot after the test support,

 

My smsts.log keep showing the same error code :

 

Failed to create E:\_SMSTaskSequence (1392) TSPxe 02/09/2015 15:23:35 512 (0x0200)   The TSM directories could not be created at this time (80070570) TSPxe 02/09/2015 15:23:35 512 (0x0200)

 

RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 02/09/2015 15:23:35 808 (0x0328) GetTsRegValue() failed. 0x80070002. TSBootShell 02/09/2015 15:23:35 808 (0x0328)   It seem that the W7 Task Sequence can't downloading & I don't understand why...   Please keep sharing