Thank you so much for your response. At the time I asked, my brain was hurting from trying to figure out issues with installing the new version. Plus I had the switch connected to the wrong network…

I did the VLAN option as you suggested. Now I do have the fog server on an “Imaging” vlan and then an uplink on the same switch in “Production” Vlan. I have set it up that you can boot to fog over the Production network as well though, which means I have the DHCP entries…though I still have DHCP being provided by FOG to the Imaging vlan. This is fine right?

Also, I have some new laptops that don’t like the undionly.kxpe bootfile name that I set in the DHCP scope. Weird eh? haha

First and foremost I want to thank the creator and community for FOG. Great platform that I’ve been using for a couple years now at various jobs.

I recently upgraded my 1.2.0 server to the latest revision as well as put it onto 16.04. Loving it, great work, after I got the php thing solved with php_ver='7.0' php_verAdds='-7.0' ./installfog.sh -y… Anyways, I was wondering how to accomplish keeping my FOG server and all the imaging duties on an “Isolated” network while still having access with the same computer to the production network. I would assume bridging the two connections in some way would work, but my networking knowledge isn’t quite there yet. My want is to be able to sit at my desktop (not the server) and access the web UI to issue commands etc etc but without bogging the production network down with imaging.

Possible or no?

Side note, is there a way to throttle FOG’s imaging speeds?