<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>bbambalova Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>bbambalova Tracker</description>
    <pubDate>Wed, 15 Nov 2023 14:39:53 GMT</pubDate>
    <dc:date>2023-11-15T14:39:53Z</dc:date>
    <item>
      <title>Configure Update Manager Settings</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Configure-Update-Manager-Settings/ta-p/2776955</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This script configures the Update Manager settings for network connectivity and patch and notification download.Use corresponding versions of the script according to Update Manager PowerCLI version you have installed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 1&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;SPAN&gt;The following example updates the shared repository setting of Update Manager server to '&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://myrepo.com/"&gt;http://myrepo.com/&lt;/A&gt;&lt;SPAN&gt;'&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Connect to the vSphere server that has an Update Manager server installed on it.&lt;UL&gt;&lt;LI&gt;$vSphereServer = Connect-VIServer &amp;lt;ip_address_of_the_vSphere_Server&amp;gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Execute the script.&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;.\SetUpdateManagerSettings41.ps1 -Servers $vSphereServer&amp;nbsp; -EnableSharedRepository $true -NewSharedRepositoryUrl&amp;nbsp; "&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://myrepo.com/"&gt;http://myrepo.com/&lt;/A&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Example 2&lt;/P&gt;&lt;P class="MsoNormal"&gt;The following example configures Update Manager to download patches from the Internet using a proxy server.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Connect to the vSphere server that has an Update Manager server installed on it.&lt;UL&gt;&lt;LI&gt;$vSphereServer = Connect-VIServer &amp;lt;ip_address_of_the_vSphere_Server&amp;gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Execute the script.&lt;UL&gt;&lt;LI&gt;&lt;P&gt;.\SetUpdateManagerSettings41.ps1 -Servers $vSphereServer&amp;nbsp; -EnableSharedRepository $false -EnableProxy $true -ProxyAddress&amp;nbsp; "updatemanager.proxy.com" -ProxyPort 896 -ProxyUserName "myUser"&amp;nbsp; -ProxyPassword "myPass"&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 May 2011 13:06:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Configure-Update-Manager-Settings/ta-p/2776955</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2011-05-20T13:06:14Z</dc:date>
    </item>
    <item>
      <title>Import host upgrade into Update Manager</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-host-upgrade-into-Update-Manager/ta-p/2792703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoNormal"&gt;This script imports a host upgrade iso or zip file into Update Manager 4.1 and creates host upgrade baseline that&lt;/P&gt;&lt;P class="MsoNormal"&gt;includes it if a baseline name is specified.If you have vSphere Update Manager 5.0 and vSphere Update Manager PowerCLI 5.0 installed use ImportESXiImage50.ps1.&lt;/P&gt;&lt;P class="MsoNormal"&gt;To use the script:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Copy the file that contains the host upgrade to the machine, where the Update Manager is installed.&lt;/LI&gt;&lt;LI&gt;Connect to the vSphere server that has this Update Manager server installed on it.&lt;UL&gt;&lt;LI&gt;$vSphereServer = Connect-VIServer &amp;lt;ip_address_of_the_vSphere_Server&amp;gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Execute the script&lt;UL&gt;&lt;LI&gt;.\ImportUpgradeRelease41.ps1 $vSphereServer "C:\UpgradeReleases\myUpgradeRelease.iso" "MyHostUpgradeBaseline"&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: The path to the file must be a local path for Update Manager Service. Providing a network share is not supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 May 2011 12:51:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-host-upgrade-into-Update-Manager/ta-p/2792703</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2011-05-20T12:51:45Z</dc:date>
    </item>
    <item>
      <title>Import host patches into Update Manager</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-host-patches-into-Update-Manager/ta-p/2793573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoNormal"&gt;This script imports zip file that contains host patches into Update Manager 4.1.&lt;/P&gt;&lt;P class="MsoNormal"&gt;To use the script:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Copy the file that contains the patches to the machine, where the Update Manager is installed.&lt;/LI&gt;&lt;LI&gt;Connect to the vSphere server that has this Update Manager server installed on it.&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt; $vSphereServer = Connect-VIServer &amp;lt;ip_address_of_the_vSphere_Server&amp;gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoListParagraphCxSpMiddle" style="text-indent: -18pt;"&gt;3.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3. Execute the script.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;.\ImportPatches41.ps1 $vSphereServer "C:\Patches\myPatches.zip"&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;Note: The path to zip file must be a local path for Update Manager Service. Providing a network share is not supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 May 2011 12:42:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-host-patches-into-Update-Manager/ta-p/2793573</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2011-05-20T12:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why is Get-Compliance so slow</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Why-is-Get-Compliance-so-slow/m-p/2060965#M462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi harkamal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoListParagraphCxSpFirst"&gt;If this is the first Update Manager PowerCLI cmdlet you are executing for the current session, at first some initialization steps are performed, connection to the Update Manager server and after that the compliance information is retrieved.&lt;/P&gt;&lt;P class="MsoListParagraphCxSpMiddle"&gt;The objects, which Get-Compliance returns, contain these fields: entity, status and baselines. If you have attached host patch baselines to your hosts, the baselines will be retrieved from the server. In addition all information for patches included in these baselines also will be retrieved from the server. So as many patches baselines include, the slower get-compliance is. I suppose that is the reason why Get-Compliance working too slow for you.&lt;/P&gt;&lt;P class="MsoListParagraphCxSpLast"&gt;About this command Get-Compliance (Get-Folder -noRecurssion). If you have virtual machines and templates in your inventory, the compliance information for them will be also retrieved. Not only for the 8 hosts.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Biliana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jan 2011 09:11:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Why-is-Get-Compliance-so-slow/m-p/2060965#M462</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2011-01-12T09:11:18Z</dc:date>
    </item>
    <item>
      <title>Retrieve inventory items to which baselines are attached</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Retrieve-inventory-items-to-which-baselines-are-attached/ta-p/2773532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This script returns the inventory items to which baselines are attached. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To use the script: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI level="1" type="ol"&gt;&lt;P&gt;Connect to the vSphere server that has a vCenter Update Manager server installed on it.&lt;/P&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;Connect-VIServer &amp;amp;lt;ip_address&amp;amp;gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;LI level="1" type="ol"&gt;&lt;P&gt;Retrieve the baseline(s) you are interested&lt;/P&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;$baseline = Get-Baseline "Critical Host Patches"&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;LI level="1" type="ol"&gt;&lt;P&gt;Supply it when executing the script&lt;/P&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;GetEntitesForBaseline.ps1 $baseline&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Dec 2010 09:21:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Retrieve-inventory-items-to-which-baselines-are-attached/ta-p/2773532</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-12-03T09:21:33Z</dc:date>
    </item>
    <item>
      <title>Export compliance information to CSV files</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-compliance-information-to-CSV-files/ta-p/2791048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The script exports compliance status details for inventory items, against attached baselines, to CSV files. To use the script, make sure that you have vSphere PowerCLI 4.1 and vCenter Update Manager PowerCLI 4.1 installed on your machine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To use the script &lt;/P&gt;&lt;OL&gt;&lt;LI level="1" type="ol"&gt;&lt;P&gt;Retrieve the inventory items you are interested&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ol"&gt;&lt;P&gt;Supply the absolute path where the generated CSV files to be saved&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Separate CSV files will be created for different types of attached baselines. &lt;/P&gt;&lt;P&gt;Feedback welcome! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Dec 2010 08:34:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-compliance-information-to-CSV-files/ta-p/2791048</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-12-03T08:34:09Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import patch baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/tac-p/2781368#M13</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you sure that you are using the original script? There is no such variable &lt;/P&gt;&lt;P&gt;$targetType = ....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Nov 2010 15:48:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/tac-p/2781368#M13</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-11-24T15:48:55Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import patch baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/tac-p/2781366#M11</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The script doesn’t have parameter for source server, because baseline contains info for the sever it comes from. &lt;/P&gt;&lt;P&gt;You receive this error because the declarations of $destinationServer, $sourceServer and $baselines are before the beginning of the script. They should be after the line: Param([……&lt;/P&gt;&lt;P&gt;Note that this way, you should change a little the example. You should use $destinationServers instead of $destinationServer:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$destinationServers = Connect-VIServer &lt;/P&gt;&lt;P&gt;$baselines = Get-PatchBaseline MyBaseline -Server $sourceServer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Nov 2010 13:19:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/tac-p/2781366#M11</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-11-19T13:19:04Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import patch baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/tac-p/2781364#M9</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This type is not changed. Could you check that the Update Manager Power CLI snap-in is added to the current console? Please, run Get-PSSnapin. The VMware.VumAutomation snap-in should be listed. &lt;/P&gt;&lt;P&gt;If it is not there, run Add-PSSnapin "VMware.VumAutomation" and try to execute the script again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Nov 2010 15:48:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/tac-p/2781364#M9</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-11-10T15:48:55Z</dc:date>
    </item>
    <item>
      <title>Re: Scan-Inventory Question</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Scan-Inventory-Question/m-p/2113313#M471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can pipe to the Scan-Inventory the objects returned by Get-VMHost cmdlet.&lt;/P&gt;&lt;BLOCKQUOTE level="1"&gt;&lt;P&gt;Get-VMHost | Scan-Inventory&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any specific reason, because you want to pass the entity's name to the Scan-Inventory?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 19:35:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Scan-Inventory-Question/m-p/2113313#M471</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-04-09T19:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: Welcome to the new vCenter Update Manager PowerCLI forum!</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Welcome-to-the-new-vCenter-Update-Manager-PowerCLI-forum/m-p/756491#M124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here on the community you can find two scripts for this purpose. The first one works with the first version of Update Manager – PowerShell Library.&lt;/P&gt;&lt;P&gt;&lt;A href="http://communities.vmware.com/docs/DOC-9471" target="test_blank"&gt;http://communities.vmware.com/docs/DOC-9471&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And the newer version of the same script can be found here:&lt;/P&gt;&lt;P&gt;&lt;A href="http://communities.vmware.com/docs/DOC-11973" target="test_blank"&gt;http://communities.vmware.com/docs/DOC-11973&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It works with Update Manager PowerCLI 4.0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For what Update Manager version you are looking a script? Did you try with them? Could you give more details about the script you need?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Apr 2010 13:02:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Welcome-to-the-new-vCenter-Update-Manager-PowerCLI-forum/m-p/756491#M124</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-04-07T13:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Compliance for a host</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Patch-Compliance-for-a-host/m-p/1165094#M309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frank,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All patches are grouped in properties(lists of patches) according to their compliance status. You can see these properties by running:&lt;/P&gt;&lt;P&gt; $complianceStatus | gm -MemberType property *patches&lt;/P&gt;&lt;P&gt;I suppose that the patches you are looking for are not with NotCompliant status, therefore the $complianceStatus.NotCompliantPatches list is empty. They should be represented in some of the other properties (patch lists). Could you check this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One more thing, I presume that the $complianceStatus in your case is a single object. If it is an array you have to explore each element of the array. Each element represents an association between &lt;/P&gt;&lt;P&gt;inventory item - baseline - patches included in the baseline, devided by their status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Biliana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Mar 2010 11:50:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Patch-Compliance-for-a-host/m-p/1165094#M309</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-03-29T11:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Compliance for a host</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Patch-Compliance-for-a-host/m-p/1165092#M307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, Alan you are right. This is to speed things up. It is similar to the way the Get-View provides the ability to specify the level of detail through –Property parameter, but in opposite direction. The default behavior of Get-View cmdlet is to return a VIObject with its full details/properties, while the Get-Compliance returns the possible smallest level of detail, until the -Detailed parameter is not used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Biliana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Mar 2010 14:55:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Patch-Compliance-for-a-host/m-p/1165092#M307</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-03-11T14:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Compliance for a host</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Patch-Compliance-for-a-host/m-p/1165090#M305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the positive feedback!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must use the –Detailed parameter. The returned detailed compliance status contains lists of patches per each of the compliance statuses. You can retrieve the missing patches this way:&lt;/P&gt;&lt;P&gt;$complianceStatus = Get-Compliance -Entity $VMHostObj –Detailed&lt;/P&gt;&lt;P&gt;$complianceStatus.NotCompliantPatches&lt;/P&gt;&lt;P&gt;The NotCompliantPatches contains a list of the patches with NotCompliant/Missing status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Biliana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Mar 2010 10:55:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Patch-Compliance-for-a-host/m-p/1165090#M305</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-03-10T10:55:01Z</dc:date>
    </item>
    <item>
      <title>Export/import patch baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/ta-p/2781359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This script exports and imports patch baselines from one Update Manager server to another.&lt;/P&gt;&lt;P&gt;Before running the script, make sure that you have vSphere PowerCLI 4.0 U1 and vCenter Update Manager PowerCLI 4.0 U1 installed on your machine. If you have vCenter Update Manager PowerCLI 4.1 installed use ExportImportBaselines_41.ps1. If you have vSphere Update Manager PowerCLI 5.0 installed use ExportImportBaselines_50.ps1.&lt;/P&gt;&lt;P&gt;To use the script&lt;/P&gt;&lt;P&gt;1. Run the Get-PatchBaseline cmdlet to retrieve the patch baselines you want to import.&lt;/P&gt;&lt;P&gt;2. Supply the retrieved baselines and one or more destination vCenter Server(s) for the script parameters and run the script.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On each destination server, the script creates duplicates of the provided baselines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Feedback welcome!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Feb 2010 15:05:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Export-import-patch-baselines-from-one-Update-Manager-server-to/ta-p/2781359</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2010-02-15T15:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779077#M115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think that the problem is you are running U3. It seems that the included updates in this baseline, missed on the destination server. Could you try to redownload all the updates on your vum destination server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 May 2009 14:21:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779077#M115</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2009-05-12T14:21:34Z</dc:date>
    </item>
    <item>
      <title>Re: VMware Update Manager Permissions</title>
      <link>https://communities.vmware.com/t5/Update-Manager-Discussions/VMware-Update-Manager-Permissions/m-p/693537#M982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you assign permission(your user - Template Admin role) to the root folder?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Mar 2009 14:36:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Update-Manager-Discussions/VMware-Update-Manager-Permissions/m-p/693537#M982</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2009-03-30T14:36:33Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779075#M113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's a good point, but i think this is not feasible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 15:07:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779075#M113</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2009-03-27T15:07:26Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779073#M111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks LucD:)&lt;/P&gt;&lt;P&gt;I'm not sure I understand you correctly. Do you want to move all software updates, or you want to avoid vum installation for each VCs?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2009 15:36:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779073#M111</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2009-03-26T15:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: Export/import baselines from one Update Manager server to another</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779071#M109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi strigl,&lt;/P&gt;&lt;P&gt;This is how I use the script:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$destinationServer = Connect-VIServer &lt;/P&gt;&lt;P&gt;$baselines = Get-Baseline test*&lt;/P&gt;&lt;P&gt;c:\ps\ExportImportBaselines_VUMU2.ps1 $baselines $destinationServer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure why the script file can't accept parameters by pipeline, but i will research.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Biliana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2009 12:46:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Export-import-baselines-from-one-Update-Manager-server-to/tac-p/2779071#M109</guid>
      <dc:creator>bbambalova</dc:creator>
      <dc:date>2009-03-26T12:46:04Z</dc:date>
    </item>
  </channel>
</rss>

