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

@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 They have confirmed the settings on their end as well…

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

@ITSolutions No sorry the FOG server is actually 10.81.231.11

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?

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,

@george1421 my apologies. It actually wasn’t the root password but the main user related to FOG. So if i chance it via command line, it breaks the images section in fog (wont show me size on server. TBH not sure what else it does as I changed it back after)

If I update the root password on Ubuntu, what do I need to update in Fog? Needless to say I have attempted and had to revert my changes

I was not…and that worked like a dream!

Thank you so much!