Lost DUA script setting in registry

[cnevin]

We have many XPe servers deployed and use DUA to keep our software up to date
on them. We specify the script to run via DUA registry setting. When we run
a script successfully, we generate a new script name for the next script in
sequence and write that to the registry. During the next DUA request, the
new script name is retrieved, downloaded and run. We have some servers that
intermittently loose the most recent change to the registry causing an older
script to run. The registry change for the new script was successfully,
since I can see the http requests in the IIS log for the new script. After
some period of time (hours or days) the server will start asking for the
previous script even though no other DUA scripts have run in that period of
time. It looks like the registry persistence of this setting is lost and it
doesn't look like a reboot has occured.

Any ideas would be greatly appreciated.

 

[Sean Liming \(MVP\)]

Do these serves have EWF or FBWF protecting the OS partition? If so a commit
or dissable the system to do the DUA would be required.


Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[cnevin]

Sean -

Thanks for the response. Unfortunately, we don't have either of these
components in the image. I did some further digging though. I checked out
the current and last known good registry settings for dua. The current
script name in the registry is commands14.dup and that's expected. The last
known good setting is commands6.dup. When we loose the registry setting, dua
starts asking for commands13.dup which is the last script that completed.
This happens when the server reboots (reason unknown). Rather than going to
the last known good script it seems to have some knowledge of the last
transaction it completed and reverts back to that script. I tried looking at
the transaction log files for the registry, but they aren't accessible due to
a sharing violation. One other bit of info, the application log is showing a
dua error message "Parameter
SYSTEM\CurrentControlSet\Services\DUAgent\Parameters\Restart was illegal"
after the dua agent start message.

Again, any help would be greatly appreciated with this puzzle.