Windowsupdate and DUAgent.

  • Thread starter Thread starter Andy Izsak
  • Start date Start date
A

Andy Izsak

I'm trying to find out if Windowsupdate should work at all or not?

I have included the DUagent in the build and the crypto service is running
yet I get an error every time complaining about the service.

If it does work, can anyone tell me step by step how to check my run time to
make sure it's setup right.

With the recent news announcements, our product is not even out yet everyone
(CNN, ESPN, etc.) is asking us about this already.


A<.
 
Andy,

WindowsUpdate is a feature of XP Pro and does not run on Embedded. Device
Update Agent is the Embedded feature that allows you to apply fixes to you
runtimes in the field (but does not have scanning functionality in the same
way that WindowsUpdate does).

There are numerous posts in this newsgroup as well as documents on
www.microsoft.com\embedded related to applying fixes using DUA, for example:
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.*
OR
http://www.microsoft.com/windows/Embedded/xp/evaluation/features/dua.asp
--
Hope this helps,

Lynda

"This posting is provided "AS IS" with no warranties, and confers no rights"
 
Lynda,.

This is certainly a feature that would make things liife easy.
Let me explain, my product is basically on line 24 hours a day, and the
operators of my products are not able to run any updates themselves. And
there is no way I would wan't to send new image disks to these clients
weekly.

So perhaps in a future release????


A<.
 
To clarify, the operator does not need to have any knowledge of or
interaction with Device Update Agent. This is a feature that you (as the
dev) get to configure when you are building your images. Part of configuing
DUA involves you choosing how often DUA will poll your server for updates.
You choose what updates get pulled down by the client.

Thanks,

Lynda

"This posting is provided "AS IS" with no warranties, and confers no rights"
 
My applications are NEVER going to be distributed on line. The mission
critical nature of our products, simply doesn't allow for it.

However, I do have many clients on networks with our product, so they can
backup their system.

All and all, windows update for this installation is absolutley
essential!!!!
So much so, that becouse of these recent heavly PUBLICIZED noise about Ms
Bugs, I MAY HAVE TO MOVE TO XP Pro Just to satisfy our customer
requirements!

HOWEVER I can't really do that either! Becouse I don't have 100 tech that
can install and configure XP pro.

A<.
 
Andy,
If the machines already have access to the net to get to the WU site then
that means you have access to the net to get to your DUA server. So what's
the difference here WRT to where your customer's devices get their fixes?

You post the QFE to your DUA server, and on its regularly scheduled polling
interval, the DUA service on your client connects to your server, sees the
QFE up on the server and automatically downloads.installs it.

So I'm not understanding where the disconnect is with your issue of DUA
versus WU. Their both on the net, they both have the QFEs, the fact is, with
DUA you have control over which QFEs get installed and at what time.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================
 
Ok, so you are saying that I have to setup my own server to do what windows
update already does?
This is a bit silly, but I guess if there is no other way.
Is there a white paper on the mechanism and what's needed to make this work?

A<.
 
The documentation supplied with SP1 and available on MSDN includes a step by
step tutorial on deploying an Internet Explorer QFE to a client, that also
includes how to setup the Remote Server for the client to connect to:
http://msdn.microsoft.com/library/d...fredistributingdeviceupdatescriptcompiler.asp

I understand your concerns about WU. I agree that it would be ideal if
future releases of Windows Embedded allow WU to recognize the embedded
platform, determine if the dependencies for the update already exist on the
device and then deploy it.

Good luck,
Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


Andy Izsak said:
Ok, so you are saying that I have to setup my own server to do what windows
update already does?
This is a bit silly, but I guess if there is no other way.
Is there a white paper on the mechanism and what's needed to make this work?

A<.

Andy Allred said:
Andy,
If the machines already have access to the net to get to the WU site then
that means you have access to the net to get to your DUA server. So what's
the difference here WRT to where your customer's devices get their fixes?

You post the QFE to your DUA server, and on its regularly scheduled polling
interval, the DUA service on your client connects to your server, sees the
QFE up on the server and automatically downloads.installs it.

So I'm not understanding where the disconnect is with your issue of DUA
versus WU. Their both on the net, they both have the QFEs, the fact is, with
DUA you have control over which QFEs get installed and at what time.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


and
the themselves.
And fixes in
the
Click to expand...
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.* confers
no
Click to expand...
service
is my
run out
yet
Click to expand...
Click to expand...
 
Back
Top