asked on

WDS - Can't PXE boot

I have a WDS server configured with a standard boot and install image. DHCP does not run on this WDS server, it runs on a different server.

I configured that DHCP server with scope options:

060 HPDM PXEClient, Standard, PXEClient (I amnot sure how this scope got called HPDM PXEClient, but HPDM is not running anywhere)
066 Boot Server Host Name, Standard, 10.3.100.232 (this is the WDS server's IP address)
067 Bootfile Name, Standard, boot\x86\pxeboot.com

However when I try to F12 PXE boot off one of my laptops I get the message "pxe-e55 proxydhcp service did not reply to request on port 4011".

Online solutions suggest running the commands "Wdsutil.exe /delete-autoadddevices /devicetype:rejecteddevices" and "Wdsutil.exe /delete-autoadddevices /devicetype:approveddevices" but that is not working, as I get the error "An error occurred while trying to execute the command. Error Code: 0xC1050100
Error Description: The Pending Devices policy is not enabled on the server."

Unfortunately I do not learn anything about this kind of stuff in the MCTS material.

ASKER CERTIFIED SOLUTION

Casey Weaver

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Garry Shape

ASKER

Yeah I have it set to respond to all (known and unknown)

motnahp00

Just to verify, you are using an Active Directory authorized DHCP server?

Garry Shape

ASKER

motnahp00, that does not appear to be the case. In the 'Manage Authorized Servers" in AD, I see some servers listed, but I do not see the DHCP server listed that I set the scope options on, nor do I see the WDS server.

Do I need to add both the dhcp server with scope options to it, as well as the WDS server to authorized servers? Or do they both have to have AD installed on them?

SOLUTION

motnahp00

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Garry Shape

ASKER

Hmm ok well I authorized the DHCP server I set the scope options for, rebooted laptop but stil get the port 4011 error. Let me keep trying.

Garry Shape

ASKER

Well I deleted some unnecessary scope options left over there from some previous HPDM (HP Device Manager) confgiruation. Then it proceeded to network boot but got some boot error. I then removed the scope option 067 (boot file name) and tried again, but now the PXE boot says not boot file received.

So maybe I'm getting somewhere, or maybe farther away. lol.

motnahp00

A lot better. Did you import your boot.wim files?

Garry Shape

ASKER

Should I configure option 67 value to "C:\RemoteInstall\Boot\x86\pxeboot.com"

motnahp00

I do not configure anything more than I need to.

Garry Shape

ASKER

Yeah the boot wim and install wim are already in WDS I imported them from the soure folder of an extracted ISO of an x86 Win7 Enterprise

I think option 67 has to be set to something but I see multiple pxeboot.com files
If I try option 67 value to "C:\RemoteInstall\Boot\x86\pxeboot.com" i get some access violation tftp msg trying to pxe boot

motnahp00

One sec while I open my lab.

motnahp00

DHCP tab -> Nothing selected

Multicast -> Use address from the following range is selected | Transfer Settings - Keep... is selected

Advanced -> Allow WDS to dynamically... is selected | DHCP Authorization - Do not authorize is selected

Network 64001 65000

PXE Response -> Respond to all client computers (K and U) PXE Response Delay 0

AD DS -> %61Username%#

Boot -> Both Require buttons are checked

Client -> nothing checked

Garry Shape

ASKER

Ok thanks. and your DHCP and WDS are different servers?

I think my Windows OS may be corrupt so I'll download again from volume licensing.

I am forced to hit F12 again after network boot, even though I told WDS not to require hitting F12. Then the "Windows Boot Manager (server IP 010.003.100.232) msg comes up saying "Windows failed to start" bla bla bla "File: \Boot\BCD" "an error occured while attempting to read the boot configuration data".

motnahp00

I have my DHCP scope on my DC.

Garry Shape

ASKER

Yeah I have no idea. Wish this wasn't so complicated. Seems like it should be so simple.

motnahp00

At least you made some progress earlier, which is a good sign.

Garry Shape

ASKER

I change option 67 boot value to "boot\x86\wdsnbp.com" on the dhcp/dc server

Now when I pxe boot from the laptop I get:

Downloaded WDSNBP...
Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 10.3.100.232 (Gateway: 10.3.11.1)...

No response from Windows Deployment Services server.
Launching pxeboot.com...
Press F12 for network service boot
Exiting pxe

I tried restarting WDS Service but ssame thing

motnahp00

That's a good sign. Did you press F12?

Garry Shape

ASKER

Yeah but after that it's TFTP download failed exits pxe, I'm not sure.

Maybe I'll just use a WinPE boot with imagex instead. this seems more troublesome than it needs to be

motnahp00

Hmmm... maybe we can work on a clean installation when you get some free time. Once you have a working demo environment, administration is really easy.

Garry Shape

ASKER

how could I do a clean install, you mean the WDS server? Would I just remove the role then re-add? I tried the wdsutil unintailize and then re-opened it and re-added the wim files through the wizard.

motnahp00

I was thinking a clean install of the WDS server.

Garry Shape

ASKER

Yeah I'll try.

I know this has worked in this environment before, because I used to work here and had it working. Someone must have changed something.

I also been looking around and see some type of bug or known issue with x64 architecture CPU and the tftp thing failing with WDS pxeboot.com...

motnahp00

Okay, let me know how things go.

Garry Shape

ASKER

Well according to this page http://blogs.technet.com/b/oob/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx it says that DHCP options should NOT be used when DHCP and WDS are on different servers and/or subnets. Instead IP helpers should be used only.

motnahp00

I've seen a few people mention the IP helper as a resolution but that is something I never configure in my environment.

SOLUTION

vivigatt

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial