OSD Task Sequence fails on laptops but works on desktops.

[roym]

Hi,

I am using SCCM 2012 R2 and have a task sequence that captures the user state, reinstalls Windows 8.1 and then restores the user state. It works fine on our Lenovo desktops.

We have HP 640 G1 and G2 laptops that fail when the task sequence boots to PE. If I open a command prompt within PE and run an IPConfig, I see that the NIC isn't operational. If I then run "wpeutil initializenetwork" it sits for a minute before showing a success message. Running IPconfig then shows an IP address.

Am I correct in thinking that because the wpeutil line gives me an IP address, it isn't a missing driver?

Any ideas what it could be?

Thanks in advance.

Edited February 24, 2017 by roym

[Config Mangler]

Strange one. When you do ipconfig /all does it show a real NIC and MAC address? Can you ping the FQDN of the SCCM box?

 

I'd be looking at adding a proper NIC driver. It's the Windows 10 / NDIS 6.5 one you want. Import that and add it to the boot images.

[roym]

Thanks for the reply. It doesn't allow any form of network interrogation (as if no NIC is present).

I'll give your suggestion a shot. I guess if its not using a "proper" driver, it isn't automatically initializing.

Edited February 27, 2017 by roym

[roym]

I have tried installing the drivers from Intel as well as the HP ones. I have even tried the x86 boot image. I get the same error.

 

smsts shows the following:

 

Failed to create list element with key value '74-df-bf-18-2f-0a' (0x8022001B) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

pSetupPass->addListItem( m_spSettingsEngine, pszNamespace, pszPath, pszKeyValue ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\smiinterface.cpp,1187) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

m_pSMIInterface->addListItem( SetupPassValue[eSetupPass], pszComponentName, pszPath, pszKeyValue ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,738) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

AddListItem( eSetupPass, XML::TcpIp::ComponentName, XML::TcpIp::Interfaces::InterfaceElement, sIdentifier ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,1063) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

m_pImpl->AddAdapterTcpIpSettings( XMLAnswerFileImpl::WindowsPE, adapterInfo ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\winpeanswerfile.cpp,176) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

pAnswerFile->AddNetworkAdapter(adapterInfo), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\netadaptersettings.cpp,575) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

Failed to configure adapter 1 (0x8022001B) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

adapterSettings.Configure( pAnswerFile ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\netsettings.cpp,188) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

Failed to configure network settings for adapter 2 (0x8022001B) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

m_pNetSettings->Configure(pAnswerFile), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootstrapsettings.cpp,191) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

this->createAnswerFile(sAnswerFilePath), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootstrapsettings.cpp,140) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

pSettings->configureAnswerFile(), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootshell.cpp,601) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

Execution failed with error 8022001B. TSBootShell 28/02/2017 14:22:22 800 (0x0320)

hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,810) TSBootShell 28/02/2017 14:22:22 800 (0x0320)

RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence TSBootShell 28/02/2017 14:22:22 800 (0x0320)

GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 28/02/2017 14:22:22 800 (0x0320)

End program: TSBootShell 28/02/2017 14:22:22 800 (0x0320)

I'm at my wits end with this. If I don't find a solution to this soon, I'll end up quitting my job and working in a shoe shop; as far away from SCCM as possible!

[Narcis]

If the IP configuration takes a longer time to initialize, or if it does not initialize by itself automatically during the Task Sequence engine start, you can trigger it just before the Task Sequence Engine starts. Some good tips where present here: https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence/but the article was updated and the section of interest removed. The ideea is that you add a modified winpeshl.ini file in the following location in SCCM [Program Files\Microsoft Configuration Manager\OSD\bin\i386\winpeshl.ini], then it will get added to your boot images when you update them. There are two files, one for i386 and one for x64.

A more similar example, where a guy is adding just a 10 seconds delay, can be found here: https://social.technet.microsoft.com/Forums/en-US/a60feb9b-d968-4a2c-9449-773c61bcdf58/os-deployment-unable-to-read-task-sequence-wpeinitexe-does-not-start-automatically?forum=configmgrgeneral

 

The last line from the file needs to be adapted for each architecture:

%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe

 

or

%SYSTEMDRIVE%\sms\bin\x64\TsBootShell.exe

[Config Mangler]

It's still missing a driver.

 

From your log - Failed to create list element with key value '74-df-bf-18-2f-0a'

 

Is that the MAC address of your Ethernet NIC? 74-DF checks out as a Liteon hardware so that probably isn't the Ethernet NIC.

 

Confirm the Ethernet MAC address, then install windows on one of each model of the laptops and check exactly what driver it's using in device manager - something like e1d65x64.sys - confirm you imported the matching driver.

[roym]

Sorry, there was an additional line with the same error and a different MAC address. It relates to Intel 217-V network card. I have tried a handful of drivers for that chipset (HP and Intel's own) to no avail.

 

Is it just a case of keep trying until something sticks?

[Config Mangler]

There is an element of trial and error!

 

Just want to check your process:

 

- Identify the right driver for your OSD - it must be x64 to connect to x64 task sequence - and use a Win 10 driver for SCCM 2012 R2

- Import the driver

- Tick the box to update the boot images - this takes 10 minutes or more

- If booting off USB stick - re-create it. PXE will be fine.

[roym]

Right!

Found the driver (lady luck was with me and it was only the 8th one I tried today). Still failed so I went back to the SMSTS log. That LiteOn MAC was still failing and was now the only one.

Quick IPconfig on a built laptop showed that 74-df-bf-18-2f-0a relates to the onboard Broadcom WiFi device. Stuck the drivers in for that (I hate red in my logs) and it now all works!

Thanks for the help, I owe you several!

[anyweb]

and for those of you reading this topic, do checkout https://www.windows-noob.com/forums/topic/12277-updated-script-how-can-i-check-for-network-connectivity-storage-before-starting-a-task-sequence-in-system-center-2012-r2-configuration-manager/as it automates telling you what the problem is and with what hardware

 

instructions for the previous version here and this is based on this post http://www.niallbrady.com/2011/08/31/missing-nic-driver-in-winpe-boot-image-no-problem/