DeployStudios, FOG, and Server 2008 DHCP

[synical]

[INDENT]Currently our network is running DeployStudios to image Macs using netboot, we are wanting to add a FOG server into the mix for imaging PCs, but we are running a Windows Server 2008 for DHCP and DNS. What would need to be done to keep the 2 servers from conflicting? I have found the documentation for making the FOG server netboot but those instructions are for a Linux DHCP server [FONT=Cambria][URL='http://www.fogproject.org/wiki/index.php?title=How_to_get_Macintosh’s_Netboot_working_with_your_FOG_server’]http://www.fogproject.org/wiki/inde...intosh’s_Netboot_working_with_your_FOG_server[/URL][/FONT][/INDENT]

[Raff]

I recommend you continue using DeployStudio for the macs and FOG for Windows/Linux. Also continue using your existing Microsoft DHCP sever, you need to setup options 66 & 67 on DHCP server for FOG.

[bcsctech]

Anyone figure out what the solution is to this? I have everything setup the way the wiki says, just can’t make the dhcp changes because we use a windows DHCP server. Just need to know what changes to make to windows dhcp server to make the mac’s boot. Do not have the option of putting our Mac computers on seperate vlans.

[Kylejb007]

The Real question is what does Deploy Studio use in DHCP to boot or if anything?

FOG needs option 66 and 67, which in a short explanation when a PXE Client boot and Contacts DHCP, it provides the PXE Clients that the TFT server address is and what boot file… If the MACs also use PXE, they will Get this information and try to boot to FOG. If MAC uses a different technique, or still uses PXE then Separate VLANs would be the ideal solution.

or the other solution is what we did for a while (We have VoIP Phones that need Option 66), anytime we wanted FOG we changed the 66 to the FOG server, and filled in 67… When we were done imaging, we Removed Option 67, and changed Option 66 to our VoIP server.

So in your situation if you want to Image mac and it doesnt use the options, Delete 66/67… When you want to Image PCs, put them in. You may even be able to write a BAT File that does it automatically.

[Raff]

We have been using gpexe bootable CDs to boot intel based mac computers into FOG for imaging.

There is a post about this in linux/mac section:- [url]http://fogproject.org/forum/threads/fog-pxe-and-intel-based-apple.856/[/url]

[JBurgin]

[quote=“synical, post: 2560, member: 819”]
[INDENT=1]Currently our network is running DeployStudios to image Macs using netboot, we are wanting to add a FOG server into the mix for imaging PCs, but we are running a Windows Server 2008 for DHCP and DNS. What would need to be done to keep the 2 servers from conflicting? I have found the documentation for making the FOG server netboot but those instructions are for a Linux DHCP server [FONT=Cambria][URL='http://www.fogproject.org/wiki/index.php?title=How_to_get_Macintosh’s_Netboot_working_with_your_FOG_server’]http://www.fogproject.org/wiki/inde...intosh’s_Netboot_working_with_your_FOG_server[/URL][/FONT][/INDENT]
[/quote]

It would seem like this would still work. You’re essentially adding the DeployStudio images to your fog servers tftpboot folder and then telling your “dhcp” server on fog, (which I believe it just handing out bootP addresses if you’re not using the FOG as a DHCP server as well) that any devices with a particular mac address asking for pxelinux.0 would be redirected to the proper mac image bootfiles.

This is all in theory. I don’t have the mac infrastructure to test all this, but have you attempted the instructions that you linked to?

[David Ekstrom]

We are running something similar here and trying to make it work…

We have a school that has both Macs and PCs. Right now there is an XServe there to handle DHCP, Deploystudio, and Netboot for the Mac machines. We’d like to add a FOG server to image the PCs. How can we make both Netboot and PXE work together? Unfortunately separate VLANs is not really viable.

At other sites, we have DHCP running on a Windows 2003 box, so modifying option 66& 67 is easy. These work fine.

[chad-bisd]

ProxyDHCP and dhcp-relay for your router if you have separate subsets that need dhcp services. We have a central fiber switch that routes for our subnets and two dhcp-relay entries in for each vlan interface, one for standard dhcp services and one to forward dhcp broadcasts to the fog server.