Yep, that solved it. Routing was the whole problem. Option 3 on the DHCP server for Vlan 300 was indeed outside of the subnet for that scope. I pointed it to the SVI on the routing stack and everything is great. We now have FOG with vlans! Thanks guys.
I ended up getting it to work. The issue was that instead of keeping the new certificate and key files in a separate place, i copied them in and replaced the old private key with my new one. This set off all kinds of issues. I ended up recreating the keys and CA, and then left my certificate files in a separate folder, just for the web server to access. Then you also need to make sure that the fog client is installed using the https switch.
For reference, setting master node to a group should reset all nodes to the group to no longer be master and define the chosen item. That said, when paired with the Location Plugin, there’s a hook to “trick” the nodes in a location to believe they are also master nodes to enable multicast to happen, maybe this is what made the GUI appear to have two master nodes in a single group?
@Sebastian-Roth Thanks Sebastian. You are right! I was not sure if I should post here or create a new topic. I felt bad just to create another post while this was related to the same (kindda) issue.
I have followed the instructions in the link but still have problems. I will create a new topic and post dubug info there
@guilherme.lima As Bob said, FOG is an imaging tool, you need/want a vdi (virtual desktop interface) environment.
You can diskless boot linux. That has been available for years. You just connect the user’s home drive to a server so all of their profiles info is saves between diskless boots. Its more trouble diskless booting MS Windows.
Instead of VDI, have you ever considered using a terminal server (both windows and linux)? Maybe explaining why you are trying to do this or what goal do you hope to achieve, can give me an idea how to answer you better.