PXE Boot Requirements

[XistEnCe]

Hi!

 

I've just installed SCCM2007R3 with FEP2010.

I'm trying to configure everything and get this show on the road - but.....

 

When booting, the clients just wait for DHCP from the PXE server, and times out.

Does the PXE boot, require the WDS service?

Or is this optional?

 

The server running SCCM is also a DHCP server, and I have defined a boundary which contains the net in the DHCP scope.

 

Do I have to advertise anything for it to PXE boot?

[XistEnCe]

I'll give that a go then!

I can't see how that should matter - But I'm definitly willing to try, and learn!

One thing I know for sure, is that SCCM lives its own life and you'd better learn to treat it well

[XistEnCe]

One step closer here now.

 

Just to confirm...

DHCP Options:

060 - Value: PXEClient

066 - Value: FQDN of SCCM server

067 - REMINST/Boot/x64/pxeboot.com

 

I've got an advertise out for an OSD TS, on a collection with a newly "imported" PC (with correct MAC-), double checked and updated the DP with x86 and x64 boot images (the ones avalible from installation of SCCM).

 

So far so good?

 

Now, I get the:

 

PXE-T04: Access violation.

PXE-E36: Error recieved from TFTP server

 

And then it exits.

 

What I can see is that it always gets it's IP from the secondary DHCP (The one not running SCCM, but it's the main DC).

I tried disabling the DHCP service on that box, and the result is that the booting PXE client get no DHCP at all (taking ages) and in the end times out.

With "PXE-E55 ProxyDHCP: No reply to request on port 4011".

 

One step closer from before, but I'm even more puzzled now

Any comments would be appreciated!

 

 

EDIT:

After removing option 060 from the DHCP scope options of the server containing SCCM (and pausing the other dhcp), it falls back to the earlier

PXE-T04: Access violation.

PXE-E36: Error recieved from TFTP server

 

But now with the SCCM server as DHCP.

 

Another Edit:

if I try to tftp (from cmd) on any computer in the domain - I can't connect and download the file from the SCCM server.

I've seen loads of tests looking like so:

tftp -i ip.of.sccm.server boot\x64\pxeboot.com

 

I've tried with both forward and backward slash, but no luck.

I can access the share, but not getting anything from tftp....

 

That's probably a bad thing?

It times out if I write

>tftp -i ip.of.sccm.server get boot\x64\pxeboot.com

Tidsavbrudd oppstod.

Mislykket forespørsel om tilkobling

(Norwegian for timeout!)

 

If I change the slashes, I get the Access Violation error.