G
Guest
Is there any way of stopping the DUA script file (.dup) from being deleted
from the media.
My scenario is this.
We have a number of machines on a site running XPe with the DUA stopped.
We've configured the settings of the DUA so that it only looks for and
executes the DUP when the service starts. the .dup file is expected to be on
a USB key plugged into the unit.
Our intention is that when required a service technician can go around to
each of the machines with a USB key containing the update script (.dup) and
the relevent files. He goes around to each machine, logs on as
administrator, plugs in his USB key, runs a batch file to start the DUA and
waits whilst the updates (both the the operating system and our application)
are updated then re-boots the machine, which automatically logs on as the
default user and runs our application.
The problem we have is that the DUA service deletes the script file when it
has finished (or at some point during the procesing of the script) so once
one machine has been updated he can't do any more without replacing the
script file.
This means that our service engineer has to return to his lap-top or similar
to replace the file on the USB stick. As some of our customers sites are
classified we're not allowed to take lap-tops on site so theoretically he
would have to keep leaving the site to put vthe file back on his USB stick.
To update say 10 machines could take all day.
Is there any way of stopping the dup file from being deleted. OR does
anyone know WHEN in the sequence the file is deleted. If it were deleted at
the beginning of the script execution then it's feasible to have a seond copy
of the dup on elsewhere on the memory stick and copy it into the directory
that the DUA expects it to be at the end of the script. Effectively a self
replicating mechanism.
Any suggestions would be appreciated.
from the media.
My scenario is this.
We have a number of machines on a site running XPe with the DUA stopped.
We've configured the settings of the DUA so that it only looks for and
executes the DUP when the service starts. the .dup file is expected to be on
a USB key plugged into the unit.
Our intention is that when required a service technician can go around to
each of the machines with a USB key containing the update script (.dup) and
the relevent files. He goes around to each machine, logs on as
administrator, plugs in his USB key, runs a batch file to start the DUA and
waits whilst the updates (both the the operating system and our application)
are updated then re-boots the machine, which automatically logs on as the
default user and runs our application.
The problem we have is that the DUA service deletes the script file when it
has finished (or at some point during the procesing of the script) so once
one machine has been updated he can't do any more without replacing the
script file.
This means that our service engineer has to return to his lap-top or similar
to replace the file on the USB stick. As some of our customers sites are
classified we're not allowed to take lap-tops on site so theoretically he
would have to keep leaving the site to put vthe file back on his USB stick.
To update say 10 machines could take all day.
Is there any way of stopping the dup file from being deleted. OR does
anyone know WHEN in the sequence the file is deleted. If it were deleted at
the beginning of the script execution then it's feasible to have a seond copy
of the dup on elsewhere on the memory stick and copy it into the directory
that the DUA expects it to be at the end of the script. Effectively a self
replicating mechanism.
Any suggestions would be appreciated.