Is the client virtual or physical?

Are you sure that the client gets an ip address?
The "Restarting DHCP Client service: retry X" is usually because the nic drivers is missing from the pxe image.

Seen this lots of times when PXE booting a virtual machine. Fixed by either editing the vmx file to use the e1000 NIC or injecting the VMware NIC drivers into WinPE

Hi,

markr1963-2 is more or less right. The problem is actually a driver problem. You have to add the correct driver to you WinPE PXE boot file.That driver could be for a VMware virtual machine, but it could also be for a say laptop :)

Hi,

I had this issue before.. they are right.. just add the driver to your winpe configuration and it will solve the problem.. thanks

FYI some hardware won't work with just the NIC drivers injected via bootwiz.exe.

I have actually just opened a case about this as well as a post about it here:  https://www-secure.symantec.com/connect/forums/winpe-21-nic-driver-issue

I had this same issue for some reason the DS required a reboot after the drivers are uploaded to for it to stick in the win pe

You can add more then just NIC drivers, it could also be eg. storage drivers. A good advice is to look at the number of drivers allready listed, then add the additional drivers and click refresh and see that the number of drivers has increesed.

An easier way to fix this on a VM virtual is to add another NIC and this time instead of flexible select e1000.

Nelo

We havent been informed of the kind of client, so we actually do not know if this is a physical or a virtual client. sunzoom could you please provide us with that information?

Also had this with HP Thin clients and this was fixed by injecting the appropriate NIC drivers into WinPE

All, Apologies for going offline again. Actually, I was on annual leave, so didn't monitor this thread and then when I came back, I forgot my SymAccount password. It took me a while to remember Now, I am back.

Seondly, thanks for Chris, Jhay, Jah, Mark and MLogon for your suggestions.

The hardware I am dealing with is Lenovo Thinkpad T410. This is a model which I never imaged in our environment below. Actually, it was the Vista drivers which I had to add to PXE Boot Image of Win PE. However, it actually didn't work. Until, I add to delete the boot image and then re-add it with a new WinPE. It then worked.

explain that again sunzoom.

You deleted all your WinPE pxe images and then created a new one AFTER using bootwiz to inject them?

Thanks,

Chris

First, it is a physical laptop. So, we are dealing with a physical machine for capturing an image.

So, this is what I did.

File > Choose PXE Server.

Select Shared Configuration

Click Open.

There, on the first tab, which reads Boot Menu.

Had WinPE. Selected and clicked Delete.

Clicked New > Pre-Boot Images. Select WinPE and x86. Follow the Wizard and on Step 6, change the drive mapping from default of F: to M: (or anything) and continue on the Wizard through Finish. This will re-generate the boot image and you should be ok.

Regards,
Sandeep