client/server program to send command to client from server program

we have an esxi 4.1 environment where you cannot use the PowerCLI to sent direct commands (batch, visualbasic scripting) to individual VMMachines and automate tasks. We are looking for a clients+server program to easily send commands to multiple vmwares quickly (startup .bat file, sent key-stroke, open xxx program etc) All vmwares are installed with Windows XP SP2 running in a local LAN Host is running Windows 7 within the same local LAN all clients/server have TCP/IP with local lan settings (IP4) used. [login to view URL] etc What client program should do: - when XP is started up, client should start and try to connect to host - if a command is received from host this should be executed (several commands should be available: execute bat/program/vbs or send a keystroke) - if XP is shutdown the client should disconnect from server program - if a command is executed properly give feedback to server program (logging in db on the server side?) - client needs to very light-weight no heavy CPU usage (it's only a simple TCP client that needs to connect and execute commands) - installation: if possible no 3rd parties installation libraries. Just a .exe file and .ini file to store the settings settings: name of client + ip address of server; the name of client will be in this shape: 001 vmwaremachine1 002 vmwaremachine 2 this makes it easy to sort all the vmware machines on numeric base What should server program do: - accept connections of clients - have a database grid of all connected clients - this grid must be able to be sorted on name of client / online|offline - it must be easy to select multiple clients and sent a command to the client. SHIFT + key to select multiple in a row; CTRL+mouse to select multiple clients - several command options need to be available, execute bat/vbs, sent key stroke etc etc - all known clients need to be seen in the grid. If client offline show as offline. Also option to remove a client, in case the vmware machine would be removed - logging of executed commands by client in local database the overall of the both programs needs to be robustly setup to be extended with more functions in the future if needed