Windows DHCP and FOG

[treyw00]

Hey Guys,

I’m trying to implement FOG with our current setup here. I had the Network team add the scope I needed (options 66 and 67 were set) but I’m getting an error SMS is looking for policy. It also goes on to say Contacting server but the IP address isn’t that of the Windows DHCP server.

Windows DHCP server IP: 10.65.224.63
Contacting Server: 10.65.224.104

Any idea what’s failing here?

Thanks,

[Wayne Workman]

What is the FOG server’s IP?

Also, can you post photos of the messages and errors your seeing please?

[treyw00]

Think the issue seems to be that the Fog server is on a separate VLAN. Would the windows DHCP server need a helper IP for this scenario?

[ITSolutions]

@treyw00 Are the vlans accessible to each other? If you can ping the FOG server from the other VLAN you should be okay with them on separate vlans. I am assuming that 10.65.224.104 is the FOG server IP? It shouldn’t contact the DHCP server, it is looking for the FOG server in order to get the PXE files and boot.

[treyw00]

@ITSolutions No sorry the FOG server is actually 10.81.231.11

[treyw00]

@Wayne-Workman https://goo.gl/photos/WBM1SUmZnNhf7sSm9

[Wayne Workman]

@treyw00 Looks like DHCP is set up for WDS instead of FOG. I think that options 066 and 067 are not correctly set for your site/building for use with FOG. Please tell your network team that you need your site/building’s subnet’s DHCP scope to have option 066 set to 10.81.231.11 and option 067 set to undionly.kkpxe

[treyw00]

@Wayne-Workman They have confirmed the settings on their end as well…

[Wayne Workman]

@treyw00 But look at your photo - Somewhere in your DHCP setup, option 066 is set to 10.65.224.104 which I assume is your WDS server, and option 067 is set to smsboot\x64\pxeboot.com

This could be a global setting that is overriding lower settings in DHCP. I’ve seen this happen before when I was helping another organization get going with FOG.

[treyw00]

@Wayne-Workman Oh I understand what you’re saying…tried telling the AD Admin that was setting this for me, but he wasn’t so much helpful as going off on a tangent about we should’ve tested this first, even though we couldn’t because lower level IT doesn’t exactly have spare DHCP servers laying around (long story for another day).

But none the less they’re seeing this as it’s done on their end, showing me the settings and saying it’s on our end. So I wanted to be sure it wasn’t something I was doing wrong.

[Wayne Workman]

@treyw00 I messaged you (top right corner, talk bubble).

[Sebastian Roth]

The picture is interesting. Thanks for sharing this. So after the initial PXE boot the client is booting WDS (message: “Downloaded WDSNBP…”) probably from 10.65.224.63 but I am not sure. From there it is chained to download the next PXE binary from 10.65.224.104… Well I am not absolutely sure but it looks like it to me.

Will be interesting what you guys come up with. Hope that Wayne can help you on this. Please let us know.

[treyw00]

Quick update since we’re going into the weekend. Network team has confirmed the need for a IP helper to reach the separate VLAN. Will update further on Monday when the change is made. Thanks again for the assist @Wayne-Workman