1 of 1 people found this helpful
Could be a problem with your DHCP scope not leasing to bootp.
Thanks for the information.
The answer helps us to boot with PXE quicker but we still not get any IP address after windows PE had started.
I still don’t understand why. Our computers over there are exactly the same models we had here.
- The PXE representative is on as it works correctly: The PXE Client computer get an address IP and display the boot menu. Then the computer choose the good PXE menu ( WinPe Provisioning) and start Windows PE.
-Windows PE Boot disk is OK and works correctly: Windows PE start, the network cards drivers are correctly loaded. The problem here is that the network card never obtains a correct IP address. IPCONFIG: IP address 169.x.x.254 mean in windows system failed to get and IP address. The local site should get a 192.168.... IP address.
My provisioning test template for the moment is very simple:
- Create a folder c:\test.gil
In Windows environment the targeted computer begin the provisioning task and the reboot correctly.
As the first boot device is network card, it starts the PXE boot, and then gets the PXE IP address. Then it displays the PXE boot menu, and starts automatically the Win PE provisioning ones. Then Windows PE start and load its drivers, and try to get an IP address. Then it failed to get one.
I confirm that in our Paris main office every provisioning template is working fine. I had OS deployment templates for new computers, and some re-installation ones to repair or migrate OS, with packages installation in the system configuration and we used all these provisioning templates since February 2010. I had updated my boot.wim file tree times and it work fine with all ours computers and laptops.