Device Update Agent Script Generator (DUAScriptGen) Beta – Try it out today…

While working on a demo for a conference I wanted to show Device Update Agent running, configuring the Windows XP Embedded operating system image seemed easy enough, getting the list of files and registry entries I needed was also very easy - then came the task of building the DUA Script file - the documentation for DUA Script is excellent, and is somewhat close to 140 pages in length... I really wanted to build the script on stage to show people how the whole process hooked together, but didn't want to write the script by hand, so I started working on a C# application that would automatically generate the script, drop some files onto the app, import a .REG file, click and “Shazzam!!”, one DUA Script file created and ready for distribution... I had enough of the application to demo up and running in a couple of days, to get the application completed I worked with Aaron Stebner

<drumroll> It's now time to introduce DUAScriptGen </drumroll>

Note that this utility is being released as a PowerToy, this means you don't get any support for the application (beyond Aaron and I on the eBlogs)...

This release of the tool has the following features

  1. Import QFE .RTF files to auto-generate script file

  2. Drag/Drop files onto the application (or use the import button) to add files to the script

  3. Location setting for files - set individual files to specific folders on the target device (folders will be created if they don't exist)

  4. Optional Reboot on update

  5. Import .REG files

  6. Add specific .REG key through DUAScriptGen UI

And I'm sure there's something else, perhaps Aaron will add the list to his blog...

Click the link below to download and start playing... any/all feedback is welcome - note that this is a .NET Framework 1.1 application, so if you don't have the framework installed (shame on you) now's the time to go get it...

it's here


Comments (5)

  1. Brad Combs says:


    I think the DUA tool is doing something odd with REGSETVALUE commands. It’s adding an extra "," for the size parameter to values that don’t require a size parameter (sz). This was discussed here…

    I apologize if someone has already mentioned this!

    Other than this the tools works as expected.


    Brad Combs

    Imago Technologies, LLC

  2. Mike says:

    Hi Brad,

    Thanks for the feedback, we will take a look over the next few days and post an update when we have this fixed.


    – Mike (and Aaron)

  3. Bill Pierson says:

    1. Double comma syndrome as mentioned already.

    2. REGSETVALUE: when the type is Binary, the script compiler looks for a size in decimal and also for comma separated bytes in DECIMAL.

    3. It appears that the script compiler cannot handle CREATEDIRECTORY directory names with spaces (Program Files) unless the whole path is enclosed in double quotes. i.e. "C:Program FilesNetmeeting". Other commands like MOVEFILE do not have this problem, however.

    4. As advertised, "5. Specify commands to execute as part of a script " I cannot see how to do this with the tool. I would not complain, but the Execute and ExecuteProcess commands are pretty intimidating.

    Other than this, I used the tool to convert Q835732 from the AdditInfo and it worked great.

  4. NickViz says:


    in the Execute file command there is an error in the command line parameter substitution.


    Optional. String that represents any command-line arguments to be passed to the executable file. <b>Include the module name as the first token</b>"

    i.e. you did

    EXECUTEPROCESS,,,,C:app.exe,, /param, bla bla

    instead of

    EXECUTEPROCESS,,,,C:app.exe,, C:app.exe /param, bla bla

    Please fix.

  5. Mike says:

    Hi Nick,

    I will take a look at this today and see if I can reproduce the problem – if so, this should be a simple fix.

    – Mike

Skip to main content