I am trying to find a way to query and automatically publish only the updates you actually need. As an example, we have only two Dell models, so do not actually need to download the entire catalog, just the relevant ones. Is there a tool to do so, or has anyone done such thing?

Hi, I haven seen a tool for that. The problem is, it's the scanning on the client that determines which updates are missing. Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

thanks Kent Any "best practice" I can use for that? May be something to fix for v.next :-). Anxiously waiting for the LB, CA day.

No there is not tool for that IMO it doesn’t make sense that you don’t download the whole catalog as Kent pointed out, How will client know what they are missing if only part of the catalog is there? Plus the catalog is not all that big in the grand scheme of things. As for deployment, yes you can only deploy those updates that are required. http://www.enhansoft.com/

Garth I get your point, and both and Kent definitely have one, but as a starter, the Dell full catalog actual download is 17 + GB... I do have a query that tells me what each computer has inside for hardware, so my thought was getting only the updates for the specific hardware. as an example, I went to the dell site, and looked at the Optiplex model, matched the updates, flagged, imported and published. assigned to one computer and it went fine. Trying to look forward, I need to determine how to create efficient deployment packages, since the bottom line for me is not having to send 1 GB of updates to PC for it o pick only 200 MB. With 4000+ computers that may become an issue. Just trying to think up loud here, in a hope that someone has more experience than I do with SCUP. All in all, it is a great tool which I found more uses on a daily basis for.

Why not just publish metadata. Based on what's required by client you can publish the full content.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Kent, that is exactly what I am trying to work on now. I did try that first, but when I deployed a test package two of the published updates came up as N/A (not downloaded). trying to sort things out now.

Well, sorry for the rumbling..I missed something in the log when I did the metadata. Looks great now! thanks Kent for sending me down that path again :-).