Identify and transfer patches over WAN via PowerCLI

[toemk]

Hi,

my goal is to query VUM via PowerCLI and get to know which patches are missing for my hosts which are connected via WAN with low bandwidth.

Then I want to transfer the identified patches manually i.e. with scp and limit the used bandwidth.

All I managed so far ist an output like this:

Name                 Product         Release Date    Severity   Vendor Id
----                 -------         ------------    --------   ---------
Updates udev         {esx 4.0.0}     09.07.2009 1... HostSec... ESX400-200906411-SG
Updates VMware ES... {esx 4.0.0}     19.11.2009 0... Critical   ESX400-200911201-UG
Updates the VMwar... {esx 4.0.0}     19.11.2009 0... HostGen... ESX400-200911209-UG

etc...

How can I translate the vendor ID string to the actual files (vib-files?) which I would have to transfer over?

Thanks in advance for any hints...

regards,

toemk

[LucD]

That mapping information i, afaik, only available in the Update Manager's database.

This is not exposed by the Update Manager cmdlets, I'm afraid.

But why would you want to scp the patches ?

You can achieve the same result with the Stage-Patch cmdlet.

Controlling the bandwidth can still be achieved I assume.

[toemk]

But why would you want to scp the patches ?

To be able limit the used bandwidth since there's lots of other traffic on the line with higher priority.

You can achieve the same result with the Stage-Patch cmdlet.

Controlling the bandwidth can still be achieved I assume.

How?

That mapping information i, afaik, only available in the Update Manager's database.

This is not exposed by the Update Manager cmdlets, I'm afraid.

One possible solution I founds is to parse the meta data xml file on the VUM server to find that out. But it's quite a hack und I would prefer a more clean way for sure

thanks

t.

[LucD]

In KB1004543 the ports used by Update Manager are well documented.

That should allow you to set up your packet shaping rules.

Good luck with the XML files hacking