<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vum on The IT Hollow</title>
    <link>https://theithollow.com/tags/vum/</link>
    <description>Recent content in Vum on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 31 May 2012 13:29:08 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vum/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using PowerCLI for VMware Update Manager</title>
      <link>https://theithollow.com/2012/05/31/using-powercli-for-vmware-update-manager/</link>
      <pubDate>Thu, 31 May 2012 13:29:08 +0000</pubDate>
      <guid>https://theithollow.com/2012/05/31/using-powercli-for-vmware-update-manager/</guid>
      <description>&lt;p&gt;You never know when you&amp;rsquo;ll need to script something and PowerCLI gives you the tools to do it.  I decided to see if I could script some of the VMware Update Manager (VUM) tasks while I was reviewing section 5.2 of the VCAP5-DCA Beta Blueprint and found that the procedures were quite easy.  My next thought was, &amp;ldquo;Why would I want to script this when I can use the GUI, and on top of that I can schedule scans and remediation already?&amp;rdquo;  My answer was, &amp;ldquo;You never know.&amp;rdquo;  Who knows when you&amp;rsquo;ll need to use the PowerCLI to accomplish a task.  Maybe, you&amp;rsquo;re scripting something so someone else can run it without really knowing how to perform the task, or you&amp;rsquo;re trying to get a report, or who knows.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
