wsus 3 local publishing tools

Hello,

the new wsus API supports local publishing.
According to the documentation at
http://msdn.microsoft.com/en-us/libr...70(VS.85).aspx
it is possible to add certificates and create packages to distribute.
The strange thing is that microsoft create no tools to do this jobs. I
am not a .net programmer so I can't compile the samples myself.

Are there free tools available to do the job ?

Thanks
Andreas

[[ Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]

Andreas Moroder wrote:
> Hello,
>
> the new wsus API supports local publishing.
> According to the documentation at
> http://msdn.microsoft.com/en-us/libr...70(VS.85).aspx
> it is possible to add certificates and create packages to distribute.
> The strange thing is that microsoft create no tools to do this jobs. I
> am not a .net programmer so I can't compile the samples myself.
>
> Are there free tools available to do the job ?
>
> Thanks
> Andreas

> Andreas Moroder wrote:

>> the new wsus API supports local publishing.

>> According to the documentation at
>> http://msdn.microsoft.com/en-us/libr...70(VS.85).aspx
>> it is possible to add certificates and create packages to distribute.
>> The strange thing is that microsoft create no tools to do this jobs.

Well, actually it does. And it's free.... sort of.

Microsoft publishes a freely downloadable tool called "System Center Updates
Publisher", which is used to create packages for distribution. However,
strictly speaking, the licensing of the tool requires that the user also
have a licensed instance of System Center Configuration Manager or System
Center Essentials.

>> I am not a .net programmer so I can't compile the samples myself.

Correct.. and this would be the other way, and really was the way in which
Microsoft intended this capability to be used. The publishing features were
built into the API, but not the WSUS console, with the expectation that
=vendors= of products would build catalogs of their own updates that could
be published to WSUS for distribution. Of course, this would have also
required them to build a UI to manage those updates, since the WSUS console
cannot even see them if they are published.

There is a third-party product, not free, that provides the capability to
manage and deploy locally published updates, but creation of those packages
is still a limiting factor.
See http://www.eminentware.com




--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin