Deployment and Imaging Group

Hello

We working on DS 7.6 using WinPE 5.0

We have updated Windows 7 x64 compatiable Lan drivers into Preboot and Deployanywhere both database but stiill facing same error.

Restarting DHCP Client service: retry 1

Restarting DHCP Client service: retry 2

Restarting DHCP Client service: retry 3

Restarting DHCP Client service: retry 4

Depending on the NIC that you have built-in to the client, you might have to look for drivers from the NIC vendor instead of the hardware vendor for the machine. A general thought here is - if I'm not wrong - WinPE 5 is based on the Windows 8.1 kernel, so I'd be looking for such drivers and also the corresponding chipset drivers where needed.

-BBC

Forgot to mention that there are a few issues around with the Intel i219-LM NIC. You'll also find a bunch of discussions around here...

Hi vikas,

Did you put the last network driver in your PXE?

Regards,

Hello David_SES

I am not using PXE, I am using WinPE 5.0

Regards

 

As BBC said, you'll need Windows 8.1 drivers for Win PE 5.0.

Hi vikas1101,

Sorry, it's exately what I meant, with WinPE 5.0. I used both, ;-).

But as BBC snd andykn101 say, it's typically when your WinPE doesn't manage your netcard driver.

So ,the best way is to find the good network driver for winpe and then add it in your winpe.

Regards,

Hello Guys

The good network driver for winpe means what exactly?? bcoz lenovo t460 model NIC drivers all we get from lenovo website and yes all operating system compatible windows 7, 8 and 8.1.

We have tried and used drivers which we manully installed.

 

Have a look at this post, which might help further. It appears that there are various issues out there surrounding the i219-LM NIC, which is now very common to new hardware platforms.

Its lntel(R) Ethernet Connection I213-LM

This post as well: https://www-secure.symantec.com/connect/downloads/intel-i217i218i219-drivers-winpe4-x86

 

Just one confusion...

We using WinPE 5.0 and trying to upload drivers from Altiris Console Driver Database Management.

Where we have to add Deployanywhere or Preboot...Just a confuse.

and we trying to deploy image for x64 and created winpe under preboot configuration x64 and x86 both. After adding drivers when we try to Recreate Preboot Environment after that background under task manager if we check it just showing 32 bit running not 64 bit till end.

The boot disk creator is an application that is running, but not the actual pre-boot environment that is created. This you want to check against the PXE Manager.

Regarding the question, DeployAnywhere is - at least as far as I know (since I don't use DeployAnywhere) - for the deployed OS so that production drivers can be pulled and the OS can silently detect and install device drivers from a repository on the DS.

Preboot is the PXE boot envirnment with which you have issues, so that is where you want to use the drivers. Does this help and clarify this for you?

We have standard image with us and now we want to deploy that image using deployanywhere on lenovo t460 model or any other lenovo or HP model desktop / laptop.

We not using any PXE, we using WinPE 5.0 in our environment.

While deploying image on lenovo t460 we facing this DHCP retrying error which we know that it is related to missing critical NIC card drivers. We have tried all types of drivers but still issue same.

When talking WinPE 5, you mean a standalone ISO, or USB device or are you referring to network boot (which then is what we refer to as PXE booting)?

And again, regardless of which WinPE environment you use and struggle with the ethernet connection, you need to have the appropriate NIC drivers included. Would that make sense?

You have to put Windows 8.1 drivers into Preboot for WinPE to work. You have to regenerate your WinPE boot file every time you add a new driver. In Device Manager you can check the properties of the NIC to see what the VEN and DEV IDs are and make sure the INF file in the driver set contains these IDs.

Hi BBC

Yes we have the appropriate NIC drivers included in Drivers DB.

Now there is new issue occure image got deploy but fails becoz of NIC drivers.

Means after OS deployed machine didnt get NIC drivers and it happens for all model machine imaging.