Restarting DHCP client service....
Updated: 21 May 2010 | 9 comments
Getting this issue when I'm trying to PXE boot into a job on the DS 6.9 Sp2. I am trying to image a HP BL220 server and I'm pretty sure the drivers for the nics are installed and auto detect drivers is selected for the boot image.
Any ideas?
I have attached 3 files below as to what happens during this process.
discussion Filed Under:
Comments
Hi Don, As you've already
Hi Don,
As you've already stated this i'm afraid this looks like the NIC drivers aren't present in your WinPE environment. I'm not a WinPE guru though.
As you're using the 64bit WinPE I would double-check you've got the 64bit version of the drivers loaded.
Kind Regards,
Ian,.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
DHCP
Don,
I agree with Ian. It is either the NIC drivers aren't loading properly, or your DHCP server is not serving up IP's the way it should. The first thing I would check would be to ensure that your DHCP server is running and not running out of IP's in it's scope. Then I would double-check the drivers that WinPE is using. If you are specifying a driver and it isn't working, you might try the UNDI driver (slower performance, but it might at least tell you where your problem is).
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Server I'm trying to image is
Server I'm trying to image is a HP ProLiant BL2x220c G5 Server Blade
I've attached two screen shots, one from the server indicating what the NIC is and the other is from editing the WinPE boot file that shows the driver on the list. Note that I do have the box checked to auto detect the driver.
Is there something else I'm missing here?
Which OS did you use?
Hi Don,
For WinPE you need to use the Vista Driver even though you might be imaging a 2003 Server. Try that and see how it works.
Rapid Deployment Pack?
Hi,
Since you are deplying HP BladeSystems, I surpose you are actually running HP Rapid Deployment pack (RDP). In case you are, which version is it? You need to be above RDP 3.80 for the BL220's to be supported.
RDP doesn't include DS SP2 so I guess that you might have a mix or only DS.
I havent tried to install RDP on an existing DS with SP2, but you could try installing the ProLiant Integration Module (PIM) only. In that case you should use autorun and uncheck everything else then the PIM.
When installing the PIM you should get all the drivers for HP BladeSystems.
________________
/mlogan
Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!
Didnt work
I downloaded the Server 2008 Drivers from here:
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3707416&lang=en&cc=us&prodTypeId=3709945&prodSeriesId=3707371&taskId=135
installed them into the list, still have it set to autodetect and still nothing. As for the HP Rapid Deployment Pack, its not listed in add/remove programs and the only indication I have is on this screenshot:
RDP version
Sorry, I don't have an RDP server at hand as I am on vacation, so if I remember correctly In the Tools > Proliant Integration there is an about too, here you should be able to see the RDP version. Otherwise there is a file called rdpabout.exe located somewhere in \\RDPSERVER\eXpress\techsup and the I think it is Windows, but not sure.
Hope this helps a little.
________________
/mlogan
Connect Etiquette: Please "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads!
Thanks for that, looks like
Thanks for that, looks like its 3.83.15
okay I've tried the link and
okay I've tried the link and its still not working. Although I must say I'm not sure how to edit the bootwize and sort by deviceID to find out of the drivers are in there or not.
It did however clear up the fact that now I can select the OEM extensions.
http://www.symantec.com/connect/blogs/troubleshooting-driver-issues-your-winpe-bootdisk
Would you like to reply?
Login or Register to post your comment.