KACE Product Support

You could certainly write VBS to pop open boxes and create variables referenced by other tasks. For the Windows-y items like networking, system name, etc. you could likely leverage the unattend files to create some behaviors like this. Meaning set up the unattend files to show the UI on errors, and intentionally leave out the info you want to hand-enter; computer name for example.

Note that the overall intent of a system like this is hands-OFF installations, but you can make it do something different with a bit of scripting.

great, i will let a colleague take care of some scripting

Is there a particular reason you need to hand enter the computer names? Do y'all use a standard naming scheme at your org? I would highly recommend using WSName for naming your computers, it's a fantastically easy program to use, and can be used in conjunction with a tiered script to name the computer, restart, join the domain and restart again. If that is something that interests you check out: http://itninja.com/question/rename-the-computer-and-join-it-to-domain

If not, then you can work through the unattend.xml to get it to prompt for certain info.

Also remember that, to get interaction in a script, you usually need to run in the user context (one of the "Run as User..." choices), not the system context. The LocalSystem account just never seems to respond when I ask it a question... ;-)

Check out the Get/Set Computer name job Corey and myself wrote for just this link out for downloading the app.

http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=1125&artlang=en