PXEFilter question

[Joe]

I've got WDS and SCCM installed on separate boxes. I installed MDT on my SCCM server and installed the PXE role on the WDS box. I'm having some problems getting a machine to PXE boot properly.

 

I'm not sure if I need to use the PXE filter. It's my understand that is just for unknown clients? Is that the case?

 

I tried to install it through the MDT start menu option, but I get an error message telling me that I need to "Please fix all errors before continuing". It doesn't give me any other error messages so I'm not sure what to fix! There is nothing in the event log and no error messages show up in the trace logs during a PXE boot.

 

In regards to this filter -- I'm assuming it needs to be installed on the SCCM server, not the WDS server. Is that correct?

 

Thanks in advance for any help.

[anyweb]

first things first

 

I'm having some problems getting a machine to PXE boot properly.

 

what problems exactly ?

[Joe]

first things first

 

 

 

what problems exactly ?

 

I have WDS installed and the router is forwarding request directly to the WDS server. I'm trying to "upgrade" the environment to use SCCM for OSD. I assigned the PXE role to my WDS server, added the boot images, added the Operating System installation files, created my collection and imported my computer into the SCCM. I then created a task and advertised it to the collection where that my computer is in.

 

I set the delay on the WDS server to 7 seconds and the delay at the SCCM console (on the WDS servers PXE role) to 0 seconds. This should allow SCCM to answer PXE requests for hosts with jobs, but still move on to PXE boot for other utilities that we have available (such as data recovery, etc) via the WDS server.

 

What happens is that "it" never seems to answer requests for the advertisement. The machine will PXE boot, but it displays the menu from the WDS server instead of the booting to the boot media I've specified in the task.

[anyweb]

did you set any dhcp options on the WDS server ? are you absolutely sure you are not prompted to press F12 as part of the pxe process (to gain access to sccm...)

[Joe]

did you set any dhcp options on the WDS server ? are you absolutely sure you are not prompted to press F12 as part of the pxe process (to gain access to sccm...)

 

Both DHCP options are unchecked -- Do not listen on port 67 and Configure DHCP option 60 to 'PXEClient'. I believe this is default.

 

I'm pretty sure I'm not prompted to hit F12 for the SCCM task. I only see the options that were present on the WDS server before I added the PXE role in SCCM. It also takes a while to actually PXEboot which makes me think SCCM isn't responding and WDS is picking up the request.

 

I double checked the boot -- it waited about 7 seconds before the PXE started. If I hit F12 I'm given the boot menu from WDS, if I let it go it continues on to boot to other devices.

 

I've double checked the mac. I've recreated the computer with the mac, with the GUID, with the mac AND the guid -- same result. Is there a log I can check to see if SCCM is passing on the client or not answering at all?

[anyweb]

what does your SMSPXE.log say ?

[Joe]

I've attached the log to this message. I stop the service, deleted it, then started it up and initiated a PXE boot. I did not hit F12 to boot into the WDS menu.

 

It seems to be recognizing the client:

[10148] 07:46:31: [WDSPXE] [bINLSVC] 000027a4 08/06 07:46:31 [MISC] Client Guid: {85674d56-535a-34dc-d819-0c7cb5bc7e1d}

[10148] 07:46:31: [WDSPXE] [bINLSVC] 000027a4 08/06 07:46:31 [MISC] MAC: {00000000-0000-0000-0000-000c29bc7e1d}

[10148] 07:46:31: [WDSPXE] [bINLSVC] 000027a4 08/06 07:46:31 [MISC] cache hit: returning success without querying DS

[10148] 07:46:31: [WDSPXE] [bINLSVC] 000027a4 08/06 07:46:31 [OPTIONS] Recognizing client.

[10148] 07:46:31: [WDSPXE] [bINLSVC] -> CBootImages::AppendImageOptions

[10148] 07:46:31: [WDSPXE] [bINLSVC] -> CBootImages::DoesBootBcdFileExists

[10148] 07:46:31: [WDSPXE] [bINLSVC] -> CBootImages::DoesFileExists

[10148] 07:46:31: [WDSPXE] [bINLSVC] <- CBootImages::DoesFileExists=2

[10148] 07:46:31: [WDSPXE] [bINLSVC] Boot Image Information

MAC: {00000000-0000-0000-0000-000C29BC7E1D}

UUID: {85674D56-535A-34DC-D819-0C7CB5BC7E1D}

BCD File Path: \Tmp\x86.{24406B82-E6E4-4123-85C3-B809B3BE3115}.bcd

[10148] 07:46:31: [WDSPXE] [bINLSVC] <- CBootImages::AppendImageOptions=0

[10148] 07:46:31: [WDSPXE] [bINLSVC] -> CAutoApprove::ProcessRequest

[10148] 07:46:31: [WDSPXE] [bINLSVC] <- CAutoApprove::ProcessRequest=0

[10148] 07:46:31: [WDSPXE] [bINLSVC] Client Information:

MAC: {00000000-0000-0000-0000-000C29BC7E1D}

UUID: {85674D56-535A-34DC-D819-0C7CB5BC7E1D}

Prestaged Account: No

SamAccountName:

MachineDN:

Prestaged to specific Boot Program: No

Boot Program: boot\x86\pxeboot.com

Boot Program being sent to client: boot\x86\pxeboot.com

Prestaged to specifiec Server: No

Server Address: 0.0.0.0

Server Address being sent to client: %WDS_SERVER%

Prestaged to specific Boot Image: No

Boot Image:

 

Is it not receiving the advertisement properly?

 

Another thing I noticed -- the GUID is wrong. It should be 564D6785-5A53-DC34-D819-0C7CB5BC7E1D.

[Joe]

Any ideas at all? I'm hoping it's something simple I'm overlooking...

[anyweb]

hmm have you tried importing the client computer into SCCM using computer associaton and see what happens then ?