What OS is your PXE Rep? I got the same PXE-E53 for Windows 8.1 but when I made my PXE Rep Windows 7 it worked fine. Expected behavior is the machine gets the boot.wim or boot_x64.wim file from the PXE Rep. Then the machine boots into Win PE. From here it depends on which .wim file it loads.
My PXE reps are Windows 8.1 Pro 64 (I have 2) Do you think that the PXE rep has to run Win 7?
The bare metal server is WinSvr2012 R2 64
1 of 1 people found this helpful
The only reason it should automatically start is if you have the template scheduled.
Your PXE issue is most likely cased by a configuration issue. Check the required DHCP options are set. Unless you are using an IP helper setup the PXE rep will also need to reside on the same sub net as the machine being booted. I have also seen a bios update on the client machine resolve a PXE error. Or test a PXE boot on a different model of machine if you have one available just to make sure it isn't an issue specific to that machine.
Kenyon, are you saying you have a Windows 8.1 PXE rep working properly? If so, are you on 9.6 with SP1? I have tried for weeks to get a PXE 8.1 working and even have a ticket open with LANDesk without success. After switching to Windows 7 it worked immediately.
Installing WIN 7 right now... Report Back in a few.
I cant say that I have tried the PXE rep on Windows 8. I was responding to the original post. I didn't see the response of the rep being on Windows 8 before. I have seen discussions on Windows 8 and Server 2012 on the board recently. I am pretty sure the PXE software is 32bit. I am taking a wild guess that this might be the root of the issue with PXE.
mmartinvegue, do you have it working on win7 32 or 64?
I have it working on a Win7 x64 Lenovo Laptop.
There are others issues I have come accress, here is one more.... If the device your PXE booting is a Surface Pro 3 then those need the "Microsoft Ethernet Adapter" in order to PXE boot. I have not gotten any other ethernet adapters to PXE boot on Surface Pro 3. Including Belkin and Startech ethernet adapters.
It should work with either 32 or 64 on Windows 7
"The only reason it should automatically start is if you have the template scheduled.'
Yes, is scheduled to run when booting from NET PXE, as I understand now, this should replace the USB Boot, then it should open the landesk user interface, since the NET PXE does not work, as soon as I used the USB Boot it runs the scheduled task.
"Your PXE issue is most likely cased by a configuration issue.
Check the required DHCP options are set. Unless you are using an IP helper setup the PXE rep will also need to reside on the same sub net as the machine being booted.
All machines are in the same subnet/Gateway. The PXE is part of a domain, the bare server is not, I don't think this matters does it?
I have also seen a bios update on the client machine resolve a PXE error. Or test a PXE boot on a different model of machine if you have one available just to make sure it isn't an issue specific to that machine.
I have updated the BIOS on both the bare metal machine and in the PXE reps.
Still the same problem, after installing WIN 7 Pro 64, I still can not Boot from PXE. Any other suggestions?
Thanks for the replies, I really appreciate your input.
1 of 1 people found this helpful
if the template is scheduled it will start on a PXE or USB boot. The scheduled task has priority. If you cancel or delete the scheduled task you will get the authentication UI.
If the PXE rep and the machined being PXE booted are on the same subnet I would make sure the DHCP options are set correct.
You are correct.. the machine being PXE booted does not need to be in a domain.
if all else fails load wireshark on the PXE rep and trace the traffic. This will let us know where the negotiation issue is.
If you do a google search on the error PXE-E53 you will find some more troubleshooting help.
So what I end up doing was this:
1. Set my DHCP Server as "THE" PXE Representative (Removed all other Reps)
2. Ran these 2 commands in the DHCP server
After each commend you should see a "command completed successfully" message or something similar.
netsh dhcp server add optiondef 60 PXEClient String 0 comment=PXE support
netsh dhcp server set optionvalue 60 STRING PXEClient
Then rebottled the bare metal server in PXE (in my server by pressing F12) and voala! it worked.
Answering the 2 questions above:
1. Is this the expected behavior? I thought the concept of using PXE Net Boot was to NOT use the USB (provisioning Boot Media) and that it would get the task from the network.
Yes. When the USB is used, it connects to the Core and runs the scheduled task. The PXE Net Boot (When configured correctly) bypasses the need for the USB, in essence, the PXE is a piece of software needed to initialize the OS or an application, in this case the LANDESK Provisioning Application, which in turn connects to the Core. Since there was a scheduled task, it doesn't needs the credentials, it just runs the task. If there wasn't a task scheduled, the normal logging prompt and selection of template would appear.
2. If the above is not as expected, what do I suppose to see once the system boots from PXE Net Boot? Is a DOS screen so I imagine it will be some kind of task detailing the progress of the capture?
The normal LANDESK Provisioning Windows will appear, just as when using the USB.