I have that much done already and am now working on modifier keys. The plan is to use short notation for keys, ie L_WIN for left windows, CTRL, F1, etc and parse the parameter to accept any modifier combination, WINDOWS+R for instance. The parameter
should also accept any hex codes input to allow reserved and unspecified keys.
Once I have worked out the key modifier parameters, I'll update the code. Feel free to use anything you think would help.
Some more details about the project I am working on:
Using either SQL or an XML config, pull OS properties and initiate a run of OS builds against an imaging host's VMs through this module.
Build the OS, configure it via script for prerequisites, then capture the image through our own imaging iso.
The next part of the automation package will utilize an OCR scan of the VM's thumbnails for status updates. MODI is an option, but as it was deprecated in Office 2010, not viable in the long term.
The whole process will be wrapped inside a job list that I intend to get a WPK framework built for starting jobs, monitoring, etc.
Here's the major hurdle I haven't yet vaulted:
In our environment, we test across 22 languages, which has added a layer of complexity, that being how to type a setup script with full UNC paths without writing language specific commands. I have not been successful researching this yet, and although
it is possible to control the mouse via code to change it via the language bar, that's quite likely going to be time consuming to get reproduceable results or downright impossible.