Use FOG in both isolated network and integrated in main network
-
I am new to FOG and I would like to know if the following scenario is possible and how to implement it.
First, I would like to use FOG for isolated network deployment. I understand how to do this, I found the tutorial so no issues here.
But between deployments, I would also like to use the same server for Windows (and Linux) client management, using the FOG client app installed on each machine.
How do I configure the FOG server for this? I have to disable DHCP (obviously) and change the FOG server NIC ip to one from our internal network. Any other things I have to set on the server?
What about on the clients? How do clients find the server? By IP? By name? -
Add another nic, configure it for your production network, add a new storage node for the new ip and put it in the same storage group as the other. You can configure dhcp on the fog server to not serve to the prod network by creating a blank subnet definition.
I can help/explain a lot more when I’m home, I’m on lunch right now.
-
Right the simple answer is as Wayne posted. Just add a second NIC as a management interface. Just ensure that dhcp is not bound to that interface and only the imaging interface. Beyond that just setup your imaging lan first, then install fog, and lastly add the second nic on your business network.
Slightly off topic, but… when you image your target computers, don’t they connect to your domain controllers to register in AD? If so how will they do this on an isolated network? You will need some kind of gateway/router to pass traffic from your imaging network to your business network.
-
Thank you very much for your answer. No need to explain further. I got the idea.
-
@george1421
As odd as this sounds, we don’t use active directory. Not really needed in our environment. -
@andreiv Cool. If you hit any humps just come back to this thread. Also please report back with success/failure and even documentation if possible.
-
Of course. I’ll keep you updated with my progress.