1 of 1 people found this helpful
Hi, as indicated in the screen it happens that WinPE Operating System cannot acquire an IP address from DHCP and hte most probable reason is that WinPE does not have correct driver for the hardware network adatper you are trying to imaging. You can test this launching from that same DOS window an ipconfig /renew command to verify if it recognize tha network adapter and if it can see a DHCP.
i often had the same issue and i resolved it adding the right drivers for the network adapter (or pc model). Consider that WinPE is an XP based OS for LDMS8.8 and Vista based OS for the LDMS.9 so you need the drivers for Vista in 9 release OS Deployment.
Anyway theese article are very usefull
http://community.landesk.com/support/docs/DOC-9485 provisioning documents launch page
http://community.landesk.com/support/docs/DOC-8091 adding drivers on Winpe(bbot.wim) in LDMS9
http://community.landesk.com/support/docs/DOC-2158 adding drivers on Winpe (ldvpe.img) in LDMS8.8
p.s= in some cases, if the right driver is addedd but it again timeouts on acquiring IP address, it coul be necessary to modify a file on Winpe environment to force ipconfig /release command during the start process. the file is startnet.cmd there is a discussion on it in the community about this.
You have to inject the good NIC driver in the WINPE image file,
So you have to find the good driver of your Ethernet Card before ....
You have to go in OS deployment menu, after click on the button you can see on the screeshot,
A new windows appear, choose Next, Add...another driver ...put the inf and sys file, all the others files include in the package of the driver in the lower window.
Then next next next ... ;-)
If the driver is the good one, it will fix the issue.
Good luck !
I've add driver, only let me add one of the .inf, also I've add all other inf and sys to boot.wim using the Manage Driver Library..
Same error still come out... Why?!?!
Any Hero... please help...
What is your core server version?
Can you give me the error message and what is the driver you add for what device ?
the error message is posted at the top of this topic.
My Core version is 9.0 SP2~
I've added several network driver such as Broadcom 57xx, Intel PRO1000 NDIS 6.1 and some of other minor network drive.
But the error still came out and cannot find the driver or sth...
I follow the procedures in LANDesk user guide but still finish my job.
Recently, I can't even boot up to PE = _ =
Before loading to PE, the TFTP seems cannot download the image...then the screen turn to a message:
"Ramdisk device creation failed due to insufficient memory"
From LDMS 9 you need to inject the Vista drivers (even though you deploy XP image) for the specific models.
Thanks for all of you!!
I can bootup to PXE menu, get IP address and start deploying OS via WINPE.
However, after I deploy the captured image to machine, the screen left WINPE and restart,
before I entered to Windows 7 welcome screen, It shows the windows shutdown with error last time and let me to enter to windows directly or repair some else,
I force machine to enter to Windows 7 then, it go to Welcome screen and all turn to Black screen after several secs. REBOOTED!!
that means the deployment is failed. or captured image is corrupted???
For the captured image,
I setup a windows 7 and installed all desired software, then run "sysprep /oobe /generalize /shutdown"
then the PC will shutdown, then I turn it on and let it boot via PXE boot to WINPE and capture image to LANDesk Server..
Can anyone tell me the solution???
How the problem resolved? Did you inject the vist drivers on the core server?
I've tried to inject vista driver but it's not useful.
For Lenovo PC, the vPro network card can support WINPE bootup and no any addtion driver.
For Dell (Optiplex 360), I think that some of the broadcom network card did not support DOS bootup so that I inject the broadcom DOS network drive that can successfully bootup the PXE menu.
Any advise in my existing case??
I can't deploy the OS regularly... seems like the boot sector corrupted.
just curious - using imagex, imagew, ghost?
i've similarly problem. how to add NIC driver when you have to add and browse path of .inf , .sys files? ,because driver that i was downlaoded is EXE file
and LD dont let me go Next if i dont add the both path of inf and sys
I use Imagew 2 and I've fix this problem after I 've recapture a new image file.
The image can be deployed to another machine successfully but how do I stop the Audit mode???
I have enter to Windows 7 but can't enter a normal mode Win7.
Of course you should find the suitable NIC driver come from OEM disc or you can spend more time to find the inf / sys drivers from internet.
EXE file should not be abled to attached.