Hello

I have a problem imaging a Dell Precision T5810 that has me stumped. Sequence of events is

• Boot machine off USB
• Confirm Network connectivity
• Select Task Sequence
• Remove USB stick and Reboot
• Machine comes back up and after awhile errors out with error "Unable to read task sequence configuration disk"

Opening a command prompt and running ipconfig shows that the machine has no NIC present

Logs show

• LOGGING: Finalize process ID set to 876
  ==============================[ TSBootShell.exe ]==============================
  Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
  Debug shell is enabled
  Waiting for PNP initialization..
  RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM
  ::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\nts_sccm_release\sms\framework\tscore\devicepath.cpp,163)
  DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\nts_sccm_release\sms\framework\tscore\devicepath.cpp,119)
  DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\nts_sccm_release\sms\framework\tscore\bootsystem.cpp,112)
  ConvertBootToLogicalPath failed (0x80070003). Retrying (0)...
  

I can;t figure out why the NIC is present on first boot but when it reloads winpe the second time to begin the image process it is absent. The WinPE is the same version on both the USB boot stick and the SCCM server

I have tried

• Booting off another USB
• Booting off CD
• Booting via PXE
• Usingg a USB Ethernet apapter

But the results are always the same. 

Any help would be appreciated as I have run out of talent on this issue

• Edited by todd_au Tuesday, March 03, 2015 12:38 AM

Have you tried manually loading the driver that you have on the loaded WinPE environment at the time it fails?

That will tell you whether the problem lies with the driver or somewhere else.

Thankyou for the reply

I have been this morning but no success so far

I did notice though when you first boot off USB, towards the end of the boot process, a DOS window pops up with the following

x:\windows\system32>cmd /c "netcfg -e -c p -i MS_NDISUIO"

Once this has run the network is working. Running it manually when the machine reboots to image doesn't fix the issue. Having successfully images some 990's and 9020's this morning I realised that this command was only running on the 5810

Did you inject the NIC driver into the boot image?

Jeff

Hi jeff

No not yet. My supervisor checked the server boot image yesterday and the driver for the NIC is listed as being there. 

The boot.wim I use on the USB stick is the same as the one the server uses. When I boot off USB i have a working NIC, when the machine reboots to begin the imaging process the NIC doesn't work. The same thing happened when I tried a USB Ethernet adapter.

Hi jeff

No not yet. My supervisor checked the server boot image yesterday and the driver for the NIC is listed as being there. 

The boot.wim I use on the USB stick is the same as the one the server uses. When I boot off USB i have a working NIC, when the machine reboots to begin the imaging process the NIC doesn't work. The same thing happened when I tried a USB Ethernet adapter.

That sounds like the boot image you're using on the USB -stick isn't the same as the one that get's booted when you start the sequence, if the adapter isn't recognized, confirm that one first.

Enable command line support (F8) on your boot image, boot the machine and hit F8 to open command prompt. With ipconfig /all you should see is the network adapter recognized or not. Some times the network adapters might need a little bit of time before they are initialized properly, I've done this by adding ping -n 10 localhost > null for my boot image's prestart command.

• Edited by Narcoticoo Tuesday, March 03, 2015 4:43 AM

Hello

I know it sounds like the boot.wim's are different, to me its still the logical and most likely scenario, but I can't figure out why or how to fix it.

The client got tired of the delay so I ended up applying the image manually with the dism command. Issues remained though, when you reboot or shut down the machine windows shuts down, the monitor goes off but the machine remains on.

So, it was taken off me and sent up the SCCM food chain to see if someone higher up could fix the issues

Thanks for everyone's help

Cheers

Hi, 

I have finally found the issue that was causing DELL T5810 to fail the SCCM Deployment. The reason why was the Network driver from the DELLs package was a wrong one, meaning, at a certain level of the deployment (Windows PE, maybe second or third reboot later), when the package needed to be pushed, the machine lost connectivity get APIPA Address, as a result, the deployment would fail. It was hard to find the solution quickly because there was neither a log error anywhere which would point to a missing driver nor an error while windows was online (as a workstation, not a member of the domain). Device manager also didnt show errors or warnings.

 

I have found the right driver, not from DELL, but from Intel which worked fine during my troubleshooting.

 

I have then injected the good Driver into the DELL package and we retested a deployment which result in success.

The driver you find here:

https://downloadcenter.intel.com/download/18713/Network-Adapter-Driver-for-Windows-7-

the exact folder inside the PROWinx64 is:

PROWinx64\PRO1000\Winx64\NDIS62

When creating a SCCM package, use only the drivers inside the NDIS62 folder, the other ones dont work.

what I did, I just injected the NIC drivers inside my T5810 package I had already in my SCCM. Of course, later, redistribute to DPs and retest.

Good luck.

Eden Oliveira

• Marked as answer by Daniel JiSunMicrosoft contingent staff, Moderator 11 minutes ago