@george1421 tested with Hyper V 2. everything you said is correct and that is exactly whats happening.

We are assuming this is limitations on the host. Going to try to test with a physical machine.

@george1421 tested with Hyper V 2. everything you said is correct and that is exactly whats happening.

We are assuming this is limitations on the host. Going to try to test with a physical machine.

@george1421 looks like got DHCP figured out. The FW was giving trouble so we moved to to a windows server made sure that 66 and 67 were setup correctly.

Our test vms get an IP and they get whats called a NBP file okay, it sees the ipexe I believe its called and said okay. Then the VM immediately reboots and lands at a REFInd screen that tells me to shutdown or reboot.

The guest in a gen 2 in hyper V and we do get to the FOG console. I was able to hit deploy and see our image and try to deploy but then the same crash I mentioned that it occurring right at boot after typing the fog username and password.

Any ideas on a potential cause?

Hey @george1421 it looks like the images did replicate. I did what you confirmed above.

Now the issue resides with DHCP. Struggling to find where I can modify these settings at. I have a feeling my Vm’s aren’t getting an address from our FW.

@george1421 by fog definitions do you mean under image management in the fog console?

The export images and import images options?

Are those just the definitions?

Hello,

All the documentation and forum post I am seeing in regards to this topic is from 2017-2018 so I do apologize if some things have changed.

So here’s the scope. We have two full fog servers. One at Site A one at Site B.

Site A is our primary and is where all image capturing will be done. I’d simply put (like to copy the one image that we have from Site A to Site B and be able to deploy it from site B.

I believe this refers to a master master setup and at one point (it still may) involve some manual steps. Two of these steps being a manual import and export and a manual copy of the image definitions from the root to the remote server.

What I think we would need to do to complete the above is to add the slave box to the master box as a storage node and enable replication on that image?

What I think needs done based on my research is below:
Make a storage group for each server, make each of them masters of their own storage group, then enable replication on the image I want to share. (just our single image)

I have never done any of this before. Just looking for some assistance and guidance.