jeMachineManager

Well… thought I’d post a status update about my freeware software projects. It’s a curious thing, I never seem to have time to finish them. Development of jeSokobanSolver 3 has been halted due to a memory bug (corruption, of unknown causes, I now think I know why but haven’t gotten around to fixing it yet). Nothing is being done on jeTMS, been doing some work on the new jeDebug but really need to put in a full week of coding to get it up and running. And today I find myself in the rare situation that I have a few spare hours and a burning desire to do some coding, so I will…. start a new project! 🙂 Going to get jeMachineManager up and running FAST.

jeMachineManager (previously jeServerManager) or jeMM for short, is Systems Management software that I spec’ed years ago… It keeps inventory of hardware and software, monitors uptime and health, and notifies the admin of any problems on any of the machines. There are lots of other SM software like System Center Configuration Manager from Microsoft or the open-source Nagios, but they are all bloated and complicated to setup and manage (no offense), requiring a bunch of intrusive pre-requisites, special user accounts and hogs vast resources.

jeMachineManager is a minimal light-weight solution, requiring only the installation of a small client (service) on the client machines. It communicates via HTTP with a cgi (or webservice) on the server. The cgi talks to a MS SQL database. There’s also an administration web interface and an admin client that handles notifications etc.

The client –> server HTTP communication means there’s no hardware or software to configure for the network access, and you’ll be able to add machines that are outside of the intranet, or in an another intranet.

In its most basic mode the client just polls the server with “I’m alive!”-messages, reporting ID and IP. That’s why I’ll be able to get it up and running quickly. All further functionality is provided with an addon-system yet to be designed.

The admin can group machines together in any way he wants, and he has access to the web interface that provides an overview of all the machines and their status, including a list of warnings… machines that are down, services that don’t reply, excessive cpu loads, disks that are near full, software that needs updating, security issues, failing fans etc etc.

The client-client does not need the server though, it can operate in a stand-alone mode where it only notifies, and advices, the user of any computer health concerns.

Starting development… hmm.. NOW!

No I didn’t, the spare time disappeared. Ok maybe thursday.