FR: RecMedia has no Network on Dell E7470

[BDIBioenergy]

Support case: 02318845

Aleksandr Deydey aked me to post a Feature Request here.
So here it is:

We have noticed, that the recovery medium of the most recent Version is not able to install a network driver for the Dell E7470 series notebooks.
Since we want to push the restore over the network, we ´need this to be fixed in a future Version.

Thank you

Here is some logging:

Code: Select all

[05.10.2017 09:29:05] <17> Info     [DriverManager] Installing driver from INF file [X:\Drivers\e1d65x64.inf_amd64_2305982aeee58c7f\E1d65x64.INF]
[05.10.2017 09:29:05] <17> Error    Failed to install driver
[05.10.2017 09:29:05] <17> Error    Ausnahme von HRESULT: 0xE0000102 (System.Runtime.InteropServices.COMException)
[05.10.2017 09:29:05] <17> Info     [DriverManager] Driver from INF file [X:\Drivers\e1d65x64.inf_amd64_2305982aeee58c7f\E1d65x64.INF] has been installed. Reboot required: False
[05.10.2017 09:29:05]      Info     < 5e4>     Starting reenumerate for hardwareID: [PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21\3&11583659&0&FE].
[05.10.2017 09:29:05]      Info     < 5e4>         Dev instance was found [47]
[05.10.2017 09:29:05]      Info     < 5e4>     Starting reenumerate for hardwareID: [PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21\3&11583659&0&FE].. Ok.
[05.10.2017 09:29:05] <17> Error    Failed to install driver. Error code: ERROR_NO_DEVICE_ID (System.Exception)
[05.10.2017 09:29:05] <17> Error       at Veeam.EndPoint.CDriverManager.InstallDriver(String infFile, String deviceId)
[05.10.2017 09:29:05] <17> Error       at Veeam.EndPoint.Recovery.UI.DriverManagementDlg.<>c__DisplayClassc.<_lvDrivers_MouseClick>b__9()
[05.10.2017 09:29:05] <17> Error       at Veeam.Backup.Common.CBackgroundFunctionRunner.ThreadProc()
[05.10.2017 09:29:05] <01> Error    Failed to install driver. Error code: ERROR_NO_DEVICE_ID   at Veeam.Backup.Common.CBackgroundFunctionRunner.Run(Function function, Form splashForm, Int32 minShowTime)
[05.10.2017 09:29:05] <01> Error       at Veeam.Backup.Common.CBackgroundFunctionRunner.Run(Function function, String message)
[05.10.2017 09:29:05] <01> Error       at Veeam.EndPoint.Recovery.UI.DriverManagementDlg._lvDrivers_MouseClick(Object sender, MouseEventArgs e)

[Dima P.]

Hello BDIBioenergy,

We will review your case details and discuss it with the team. Thank you for your post!

[Dima P.]

BDIBioenergy,

QA team has reviewed your case. They confirmed that on the latest windows 10 build driver collection works correctly. Can you please try to update your OS and re run the Recovery Media creation wizard? Once done please boot newly created Recovery Media and check if the issue still persists. Thanks in advance.

[BDIBioenergy]

Hey Dima.
Thank you for your replies!

btw: We tested a Macrium Reflect WinPE stick without any problems with LAN support, so I guess, that the problem is on your side.

Ich have trouble understanding what you mean with:

They confirmed that on the latest windows 10 build driver collection works correctly. Can you please try to update your OS and re run the Recovery Media creation wizard?

We run a 1511 Windows 10 LTSB Windows here.
What do I need to do?

[dmayer]

Since you have lTSB you have Volume Licensing. If you have Software insurance through Microsoft, Veeam is basically asking you to download a newer LTSB version which should be 1607 (Anniversary update) and do an in place upgrade. I believe 1607 is the latest LTSB as Creators (1703) is Semi-Annual and not sure about fall Creator's (1709) if it made it onto LTSB.

[Dima P.]

Daniel is right. Please update to the latest possible version and then recreate the Recovery Media. If the problem still persists, please update this thread.

WinPE stick without any problems with LAN support, so I guess, that the problem is on your side.

Veeam Agent does not use PE (Programming Environment). Instead, it leverages native Windows Recovery Environment which does not require additional components like ADK being installed. That said, you still can test a Recovery Media based on PE – the only requirement is to install the ADK which is about 3GB packed and contains a lot of unnecessary components (that’s why we don’t use or request it by default).

Thanks!

[BDIBioenergy]

Thank you for your brief explanations!
It worked after I created the rescue media on my own (I am an external here) NB Dell E5550 with a Windows Enterprise 1703.

perfect, thanks!