Unable to PXE Boot with WinPE

[Arnfinn Auestad]

I had the same problem. I resolved it by selecting "factory -winPE" in sted of "factory -minint" in step 7 of Altiris Boot disk Creator. Booting on the new image worked fine

[Goran Kubelka]

Hi Larry,
I have same situation with BL460.

I have tried all previously sugested things but still no success.
Did you find any solution?

[GenePro]

It looks like your WinPE image on PXE server is missing correct NIC drivers.
I was able to solve this problem by adding latest nic (NC371i in my case) drivers to WinPE image.

Lood Luck!

[Digex]

Try Linux boot. I thought WinPE was too slow. Linux boot is faster and has worked seemless for me.

[Barthel_1]

Hello,

in our case the reason for the mentioned problem was a missing entry for the Wins-Server in the Scope Options of the DHCP-Server(option 044 + 046 on Microsoft DHCP-Server)

Figured it out by stoping the Logon-Script while booting WinPE by pressing CTRL + C.

A ping to the Deploymentserver-Hostname didn't work. But I was able to ping the Deploymentserver-IP and to oben the Deployment Share by using the IP Adress.
So the NIC-Driver was working for shure.

As mentioned setting the correct Wins-Server in the DHCP-Options fixed the problem for us...

[lesc02]

Hi, we upgraded to 3.70 and are experiencing the same issue.

Once we start the Proliant Windows image job, the image does get copied to the server, the server reboots, RAMDISK downloads for a very long time, the script runs again, the dhcp client service starts, then tries to validate the ip and goes into a starting dhcp client service loop. We are using BL20p G4's, this is very frustrating.

Any suggestions?

thanks

[Gerrit Leverland]

Were running RDP 3.6 since friday, however we have the same problem. When you breakout of the restart DHCP client batch file you are able to see your taskmanager. However when i click on network connections there are no nics available. So that must be the problem.

I`ve added manually the NC 373I drivers for our new DL 380 G5`s. But the windows pe installation still doesnt see them. Any suggestions to solve this problem ?

BTW, i think its strange thet the drivers of the DL 380 G5 are not onboard of the standard installation.

[Rodney Kurlin]

I just upgraded to RDP 3.80 with DS 6.9 and WinPE 2.1. I am have the exact same issue with getting a VM Guest to Boot to PXE. My pysical servers build just fine, but not the VM's. I get the exact same error message with the Restarting DHCP then fails on the 19th try. Has anyone been able to solve this issue?

[Troy Harrell]

I too am running into the same problem after installing RDP 3.8 and WinPe 2.1. So far I haven't been able to figure this one out. I have done everything from disabling NICs in BIOS, regenerating Boot Images, verifing nic drivers and verifying internal ports on the blade switch is set to the correct vlan and enabled. Can someone assist me?

[Rodney Kurlin]

Troy,

I found this information on the Altiris Forum, I am going to try it and see if it works.

"If you have a requirement to build Vmware Guests with WinPE 2.0 you will notice very sporatic network connectivity.
Just to make sure I have injected the Vmware Nic drivers into my base .WMI file.
Add both, the vmxnet.inf and vmware-nic.inf
I added the Win2k drivers into my image and they seem to be working much better."

[Rodney Kurlin]

Troy,

Here is what I found.

1. Add the following to the vmx file.

ethernet0.virtualDev = "e1000"
ethernet0.present= "true"

2. Add the VMNET drivers to the WinPE image. You can find these on any VM guest that you have deployed. They are, well should be under the "%systemDrive%\Program Files\VMware\VMware Tools\Drivers". Copy the vmxnet folder to your bootwiz folder on your deployment server. I built a test WinPE 2.1 Boot image and included the vmxnet.inf and vmware-nic.inf. This seems to work also, but there is an error during the NIC Driver Loading phase of WinPE. But the VM stills grabbed a DHCP address and finished booting. I am still looking into this.

[Troy Harrell]

To resolve the issue I was having, I had to reinstall RDP 3.8. When I first build my RDP server I installed WAIK2.1 after the installation of RDP, thus not allowing the HP drivers to be added to WAIK WinPE image. Once I installed RDP 3.8 the problem was resolve.

[Kase]

I just fixed this issue. It was caused by not selecting the full hardware detection option during the PXE boot disk creator process. I selected the other option (said something about "faster") and that is when it broke. I rebuilt the PXE boot disk with the full option and it works fine. This is on bl680cs with Altiris RDP 3.6.

[Christopher Younger]

I noticed that the original poster was asking about the authenicating connection hang and everyone addressed an issue with DHCP.

I had this problem after a fresh install of ICDVD 2.30. After several hours of craziness, we looked in the WinPE Boot Image editor. The WinPE image was using incorrect credentials (the domain I input during setup was changed to "workgroup"). I went through the Boot Image Wizard, input the correct credentials and everything was peachy.

Hope this helps someone.

[Matthijs van den Berg]

Hi All,

I have the issue with the VMware deployment. Initial install runs okay, but a reinstall of the server will not PXE boot (or only once). It does get an IP address, sees Altiris but does not get a job. (3 seconds countdown, then reboot)

When I delete the IP address the installer uses from the DHCP server and reboot the server I am installing the install continues, Altiris provides the server a job.

So if someone knows how to handle this... please let me know!

[Graeme Wood]

I would strongly suggest trying the solution that Christohper Younger posted. I have just had this problem with IC DVD 2.35...it was the problem with some part of the installation deciding to change the domain name I had entered to 'Workgroup' Once I edited the Boot Image it worked first time...superb!!!

[Simon Payne_1]

After 2 days of ripping my hair out, I was receiving this error because I had only allocated 256mb to my test VM client.
It was running out of memory before loading all the drivers including the NIC.

I increased it to 1GB and it worked first go.

[Bhavani N]

I faced same problem.
BL465CG7 and after I injected the HPNC551i drivers and recompiled WINPE 2.1 its good now.

Although imaging windows 2008 R2 is having problems with Altiris Dagent not getting installed and its stuck after booting to automation on sending wake on LAN signal.