[sccm 2007] SCCM 2007, PXE and OSD

[adamf]

I've started to play around with SCCM 2007, i've got it setup and am able to distribute software to clients without a problem.

 

I'm now trying OSD and running into problems booting from PXE/getting a response from the SCCM.

 

This is what I have done so far, hopefully someone can point me in the right direction....

 

SCCM is setup, installed on our servers VLAN, the client I am testing it with is on another VLAN and has the client installed.

 

WDS has been installed and not configured on the SCCM server

 

I've created PXE service point and add the 2 images that come with SCCM to the DP (SMSPXEIMAGES$)

 

In DHCP (which is on a different server) I have the following options set (on 1 scope that I am testing this with)

 

Option 60 = PXEClient

Option 66 = 10.59.100.50 (IP of SCCM server)

Option 67 = REMINST\Boot\x86\wdsnbp.com

 

On my Core Switch I have IP Helper address which forward requests to the 2 DHCP servers.

 

When I try and boot the client using PXE I get the error that says:

 

proxydhcp did not reply to request on port 4011

 

Can anybody point me in the right direction as to what I have done wrong or missed?

[3s-gtech]

Try it without port 60 ticked - that's the error I was getting when trying to boot into FOG yesterday, 60 was supposed to be unticked but was enabled on my scope.

[adamf]

Ok..... That worked in fashion.... I'm getting this now:

 

PXE-T04: Access Violation

PXE-E36: Error recieved from TFTP server

 

Any ideas?

[tarquel]

I had a bit of fun setting this up myself.

 

On our setup, we have the site server, and two "Deployment Points" that effectively have the following SCCM Roles on them (i.e. installed via the SCCM server itself). These are:

 

ConfigMgr component server, distribution point, PXE service point, site system

 

These DP servers (as i lovingly call them) have the WDS and DHCP Server roles on them. DHCP is setup as normal with a range that the booting machines can use, and (despite popular believe) I had to run through the initial config of WDS, BUT ensuring that it doesnt respond to requests.

 

The result of the WDS configuration is: "do not listen on port 67" and configure DHCP option 60 to indicate that the server is also a PXE server" ticked, with the PXE Response tab set as "Do not respond to any client computers". Pretty much all the other options are whatever it chose, or are blank.

 

In my DHCP Scope options are:

- 003 Router -

- 006 DNS Servers -

- 015 DNS domain nane - ladeda.gov.uk (obviously, the FQDN of whatever ur windows domain is)

- 060 PXEClient - PXEClient

 

Some of that might be different in ur setup, and I didnt do the IP Helper part of it on the comms/switch side unfortunately so not sure what you'd need there exactly.

 

Hope that helps in some way.

 

Cheers

[TheScarfedOne]

Some more shameless blog plugging! Once you get to the build/capture stage...

 

Until then, the guys over at windows-noob.com got me set up and running.

[tarquel]

Handy place windows-noob.com is. I did use it to some extent, although I had to find my own way with this part of things (their setup was all on one server, whereas ours certainly isn't ).