@Sebastian-Roth Thanks so much for the detailed explanation. It worked like a charm!

@Sebastian-Roth I think both of these solutions could definitely work for this application. I just have a few questions before selecting one over the other:

1. For consistencies sake, I’ve configured the FOG servers in different locations to run off the same IP as they are isolated from each other. If I were to copy the CA certs from the Master server over to the server in the second location, would I still need to re-create the keys? Or would the keys already be set to match the IP?
2. There are 3 files in /opt/fog/snapins/ssl/CA/: .fogCA.key, .fogCA.pem, and .fogCA.srl. Are all these files necessary when copying over the certs to another server?
3. Regarding your second route, would I be able to reverse this and export the CA cert from the location A server and import that into the Windows certificate store on the host in location B?

Thanks for the help!

Hi there,

I’ve set up a “golden” group of machines that consists of a FOG server and 2 hosts that I’m using to test/capture new images. This group of machines always has the most up-to-date images and is in location A. When these images are ready to be deployed, I’ll export the image and CSV files and transfer them via external hard drive to another FOG server that has been set up in location B. I’ll use that FOG server to deploy the new image to a particular group of machines in location B.

The issue I’m having is that after I deploy the latest image to the machines in location B, the FOG Client Service (which is pre-installed on that new image) can’t communicate to this new FOG server. Instead, I need to remove and reinstall the FOG Client Service on all hosts in location B.

My guess is that when the FOG Client Service is installed on the hosts in location A, it takes note of the FOG server that those hosts are connected to. If this assumption is correct, is there a way I can reconfigure the FOG Client Service to communicate with a new FOG server rather than reinstalling the service? If my guess is way off, can you tell me why I need to reinstall the service before it can function as normal and how I can avoid the reinstallation?

Thanks!