Would like the ability to create user-defined variables within a deployment definition (Scripted Installations, or System Images) that are valid for the entire process of deployment. These variables would be held by the K2000, not by the box being imaged.

Example:
As a pre-install task, I could determine the BIOS version of the box being imaged, and store it in the variable FIRMWAREVER, and then at any point subsequent, in a later pre-install task, or a post-install task, I could call %FIRMWAREVER% and have that information. This way I don't have to store it on a temp RAM drive (X:) or the petemp share, etc, having to worry about those drives being unavailable later, etc.

These variable should be user-defined, so that if I want to uselessly store the info MYEYECOLOR=Hazel, I can do so. I don't want to be limited to just the variables the K2000 programmers think I might need.

If those variables were visible on the Progress screen, showing live changes, this capability could also be an awesome debugging utility.

Once the deployment is complete, those variables disappear.