@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?