SUS and XP-E SP2

[JC]

if you are referring to WUS - Windows Update Service, then no. You can
deploy QFE's that are also posted there using the Desktop QFE Installer, but
you cannot download them using the "automatic updates" features like XPP
does. This violates licensing agreements. SUS can deploy XPP updates just
fine. Basically you are taking the functionality of WUS, and bringing it in
house to your systems, and you manage the deployment.

HTH,
JC

 

[Phil]

I have read the "Using SUS with Windows XP Embedded Service Pack 2" article,
http://msdn.microsoft.com/library/d...UsingSUSWithWindowsXPEmbeddedServicePack2.asp

but I am still confused about what kind of updates are supported.

1) Do you need to load just XP-Embedded specific updates using SUS onto your
XP-Embedded clients? Or are the XP-Professional updates now compatible?
The SUS specific documentation I have read does not list XP-Embedded
specifically.

2) Is WUS better than SUS to update XP-Embedded clients?

TIA
Phil D

 

[Phil]

Thanks JC
So we should use SUS to distribute XPP updates to XPE clients, is that it?
Phil

if you are referring to WUS - Windows Update Service, then no. You can
deploy QFE's that are also posted there using the Desktop QFE Installer, but
you cannot download them using the "automatic updates" features like XPP
does. This violates licensing agreements. SUS can deploy XPP updates just
fine. Basically you are taking the functionality of WUS, and bringing it in
house to your systems, and you manage the deployment.

HTH,
JC

____________________________________________________________________________
__

I have read the "Using SUS with Windows XP Embedded Service Pack 2"
article,
http://msdn.microsoft.com/library/d...UsingSUSWithWindowsXPEmbeddedServicePack2.asp

but I am still confused about what kind of updates are supported.

1) Do you need to load just XP-Embedded specific updates using SUS onto
your
XP-Embedded clients? Or are the XP-Professional updates now compatible?
The SUS specific documentation I have read does not list XP-Embedded
specifically.

2) Is WUS better than SUS to update XP-Embedded clients?

TIA
Phil D

[/QUOTE]

 

[KM]

Phil,

To distribute XPP updates to XPe clients your friends could be:

- DUA. You will have to either include Desktop Installer component to be able to run Desktop QFEs directly at runtime or, if you
don't resolve the Desktop Installer component's dependencies you can unwrap each QFE and create DUA create for each of them to
deploy the QFE's files&registry entries on the target.

- SUS. Will require SUS 2.0 server on your network (kinda a proxy between your clients and MS WU server).

- SMS. More complex, flexible and managable solution but your image footprint will grow much. Also requires SMS server on your
network.

- Your own custom deployment option. After all, the XPP QFEs are nothing more than just files and registry entries.

Read more and compare yourself from here:
http://msdn.microsoft.com/library/d...UsingSUSWithWindowsXPEmbeddedServicePack2.asp

KM

Thanks JC
So we should use SUS to distribute XPP updates to XPE clients, is that it?
Phil


____________________________________________________________________________
__

[/QUOTE]

 

[Daniel Simpson \(MS\)]

Hi Phil,

I will take a look at the SUS article and see if I can't make it a little
more clear as to how SUS relates to Windows Update.

JC and KM are correct. You set up your own intranet server that
communicates with Microsoft's Windows Update public site. Your intranet
server downloads updates, and an administartor must examine each and every
update to see if it applies to your embedded devices. If it does, you can
flag that update to be downloaded by your devices.

Hope this helps,
Dan

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

Phil,

To distribute XPP updates to XPe clients your friends could be:

- DUA. You will have to either include Desktop Installer component to
be able to run Desktop QFEs directly at runtime or, if you don't resolve
the Desktop Installer component's dependencies you can unwrap each QFE and
create DUA create for each of them to deploy the QFE's files&registry
entries on the target.

- SUS. Will require SUS 2.0 server on your network (kinda a proxy
between your clients and MS WU server).

- SMS. More complex, flexible and managable solution but your image
footprint will grow much. Also requires SMS server on your network.

- Your own custom deployment option. After all, the XPP QFEs are nothing
more than just files and registry entries.

Read more and compare yourself from here:
http://msdn.microsoft.com/library/d...UsingSUSWithWindowsXPEmbeddedServicePack2.asp

KM

[/QUOTE]