Categories

• Announcements

  Get the latest news on what's happening.
  171
  Topics
  726
  Posts

  M

  @Sebastian-Roth Ok, thank you.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  2001
  Topics
  16111
  Posts

  K

  Hi everybody, It’s just for say thank you! Fog is absolutly awesome! Thank you to all fog team!
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9718
  Topics
  96028
  Posts

  L

  @george1421 “At this time the problem is infrastructure related and not FOG.” I agree. I don’t understand the boot dhcp response on vlan 10. The ip configuration is good when loaded !
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2091
  Topics
  19622
  Posts

  S

  @mckay Now that I look at this again I can see this has a few flaws. The user will see the FOG dialog twice if you run it yourself because the fog-client definitely calls it and I cannot see a way to prevent from this. As mentioned before it won’t be easy to grab the user input (postpone, …) as this is being sent back over a local connection instead of returned as exit code by the FOGShutdownGUI.exe. We have the plan to only add features to the FOG branch working-1.6 which is intended to be the next major FOG version 1.6… Though it’s still some work before this is ready to go and developers are scarce. So if you are keen to push this forward I would ask you to setup a testing FOG server instance in your network and install working-1.6 on that. We can work on adding this feature to that and you’ll be testing things alongside. What do you think?