The tale of two client programs

It would be nice to have a server-agnostic heartbeat client that could be pre-installed to an image, instead of the full-blown server-tied client.

Then the FOG server on that subnet would pick up that ping and list those machines that don’t have the full client installed. This would then allow the technician to be able to push the client on to those machines via the web interface at their convenience.

Nope. If it was server agnostic then what we have created is a rootkit capable of being hijacked by anyone.

What would be better is if you setup your certificate heirachy. In an ideal world (I.e. fog 2.0) storage nodes would receive a key from the server that allows clients to connect directly to it. For 1.3.0 you would need to manually set it up so all storage nodes have the same root CA keg and then call the SSL regen command. You could also setup intermediate CA keys for the storage nodes if you wanted to do it properly and remove some of the security issues of the desribed method above.

Lead FOG Client developer.
Before posting a client issue or question, see the FOG Client Wiki.
For FOG Client progress, see our Kanban Board.