DUA

  • Thread starter Thread starter Tim Houle
  • Start date Start date
T

Tim Houle

Hi,

We are just starting to release our product in the field
with XPE boxes. I have not implemented DUA into these
images. Most of these systems will not be on networks but
possibly in the future. Would anyone recommend that I
implement DUA into these images?

Thanks,
Tim
 
Thanks Sid.

Tim

-----Original Message-----
Tim:
Well certainly..either have DUA or Desktop QFE Installer on all of the
images bcoz at one time or another they will need upgrade and patches. Even
if they are not on network I would recommend DUA in these images just to save
you a lot of trouble in future..refer my thread Windows Security Patches...:0)
Good luck..and lemme know if I can help
Thanks
Sid
(e-mail address removed)


.
Click to expand...
 
Sid,

What if I just create a new image and blast new images
that have the fix up to my XPe boxes?
 
If you're asking if reimaging the entire device with an updated runtime
with the patch included is viable, then yes that is one solution some
OEMs use. If in doubt, add DUA or any other servicing mechanism that
you think applies.

In SP2, you will also have SUS components in the DB that you can
leverage as well for an additional method of servicing.
 
It wouldn't hurt to put both DUA and Desktop QFE Installer in your image.
They don't take up much space. That way, you can use them in conjunction
with eachother by creating a simple DUA script that executes the Desktop QFE
executable.
 
Hi James,

Uhhh, never say with such certainty that adding some components that will not be needed can't hurt you.
There is always slight possibility that someone can find a hole in DUA implementation and use it against us, and what then?

Unlikely but still there is possibility.

Best regards,
Slobodan
 
Especially considering HTTP stack that comes with the DUA.
It needs to be patched once in a while itself :-)

Btw, both components may not take much space on Winlogon images. But with Minlogon where footprint is reduced adding the components
may double the image size.
 
I suppose I should've been more specific about these things in my post.
Thanks for pointing that out to me. :-)



KM said:
Especially considering HTTP stack that comes with the DUA.
It needs to be patched once in a while itself :-)

Btw, both components may not take much space on Winlogon images. But with
Click to expand...
Minlogon where footprint is reduced adding the components
 
Basically, you can configure DUA settings to poll a directory, either
locally on the device or on a web server, and check for DUA updates. This
tells how to use DUA:
http://msdn.microsoft.com/library/d...n-us/xpehelp/html/xecondeviceupdateagent3.asp

What I was trying to say earlier was that you can build both DUA and Desktop
QFE Installer into your image and then write a DUA script that tells DUA to
launch the XP Pro QFE installation executable. You can specify the QFE
installation executable to be launched with the "/Q" flag, which will run it
in "quiet mode". If you have some other convenient way to get a desktop QFE
installation executable onto the device and have another way to launch the
executable, then you wouldn't need to use DUA. I'm sure the possibilities
are endless and there are many things to consider with any approach, but
these are just ideas.

Just make sure that you don't try to install any patches for components that
are not built in your XPe image; it could be catastrophic (for example,
don't install IE patches onto an XPe system that doesn't have IE built into
it).
 
Back
Top