D
Darren Haigh
I'm puzzled as to the way DUAgent scripts are created and
deployed and how this fits with a system recovery disk.
In short I have a system which is shipped with a recovery
disk, this disk is now 12months old. The recovery disk
isn't used to updgrade our systems in any way, only to
restore them to factory conditions (you know what these
users are like when they stat messing with the systems.!)
From what I can gather the DUAgent looks for a local .dup
file, defined in the registry (can't use HTTP in my
application), then runs the script within at a period
again defined in the registry.
Does it only run this one script ? or any .dup file it
finds ?
If a system is restored using the restore disk, then all
the updates need to be reapplied. Does this imply that the
update.dup script file needs to grow each time an update
is added, and if this is the case wont this have an
adverse effect on the speed at which the update is
applied, if it has to trawl through 15+ updates before it
gets to the one it really needs. I guess under this
condition it would just apply the old patches again.?
I was kinda hoping that I could create a single .dup file
for each MS patch, then just deliver a bunch of .dup
files. Is this not the case.?
deployed and how this fits with a system recovery disk.
In short I have a system which is shipped with a recovery
disk, this disk is now 12months old. The recovery disk
isn't used to updgrade our systems in any way, only to
restore them to factory conditions (you know what these
users are like when they stat messing with the systems.!)
From what I can gather the DUAgent looks for a local .dup
file, defined in the registry (can't use HTTP in my
application), then runs the script within at a period
again defined in the registry.
Does it only run this one script ? or any .dup file it
finds ?
If a system is restored using the restore disk, then all
the updates need to be reapplied. Does this imply that the
update.dup script file needs to grow each time an update
is added, and if this is the case wont this have an
adverse effect on the speed at which the update is
applied, if it has to trawl through 15+ updates before it
gets to the one it really needs. I guess under this
condition it would just apply the old patches again.?
I was kinda hoping that I could create a single .dup file
for each MS patch, then just deliver a bunch of .dup
files. Is this not the case.?