<?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>Tocano Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Tocano Tracker</description>
    <pubDate>Wed, 15 Nov 2023 10:23:45 GMT</pubDate>
    <dc:date>2023-11-15T10:23:45Z</dc:date>
    <item>
      <title>HowTo: Alter Deployment Constraint Tags in a pre-provisioning subscription</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/HowTo-Alter-Deployment-Constraint-Tags-in-a-pre-provisioning/m-p/2981998#M25269</link>
      <description>&lt;P&gt;We have a CloudTemplate catalog item with a pre-provisioning subscription (EventTopic: Deployment Requested) which kicks off an Orchestrator workflow where we run some business logic before the VM is created. In certain circumstances, we want to change/override/modify the resource constraint tags that AA uses for the provisioning.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have the workflow kicking off where I want. I have the logic in the workflow working as desired. It catches the condition case we're looking for. But I haven't been able to figure out how to modify the constraint tags so that it provisions as we want it to.&lt;/P&gt;&lt;P&gt;Any help or nudge in the right direction would be appreciated.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2023 19:23:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/HowTo-Alter-Deployment-Constraint-Tags-in-a-pre-provisioning/m-p/2981998#M25269</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-08-11T19:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: What is required in order to have Get-Log -Bundle to work for an ESXi host?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976843#M112595</link>
      <description>&lt;P&gt;I mean, the system generated bundle is certainly more than just the zip of those 4 log files.&lt;/P&gt;&lt;P&gt;The bundle contains lots of additional config files, settings, system files, VM logs, and even the contents of entire system folders.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get 4 individual logs from your approach.&lt;/P&gt;&lt;PRE&gt;&amp;gt; Get-ChildItem -Recurse&lt;BR /&gt;&lt;BR /&gt;Directory: E:\Downloads\logFetchMethods\lucD_Approach&lt;BR /&gt;&lt;BR /&gt;Mode LastWriteTime Length Name&lt;BR /&gt;---- ------------- ------ ----&lt;BR /&gt;-a--- 7/11/2023 4:50 PM 1402258 log-________________________-fdm-20230711-1550.log&lt;BR /&gt;-a--- 7/11/2023 4:50 PM 303708 log-________________________-hostd-20230711-1550.log&lt;BR /&gt;-a--- 7/11/2023 4:50 PM 4695792 log-________________________-vmkernel-20230711-1550.log&lt;BR /&gt;-a--- 7/11/2023 4:50 PM 5034728 log-________________________-vpxa-20230711-1550.log&lt;/PRE&gt;&lt;P&gt;When I extract a system generated log bundle:&lt;/P&gt;&lt;PRE&gt;E:\Downloads\logFetchMethods\systemGeneratedBundleApproach&amp;gt; (Get-ChildItem -Recurse).Count&lt;BR /&gt;3854&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 21:23:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976843#M112595</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-07-11T21:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: What is required in order to have Get-Log -Bundle to work for an ESXi host?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976819#M112590</link>
      <description>&lt;P&gt;Yeah, passing the VMHost parameter both directly or via the pipeline result in the same behavior: It begins to process, I get a Progress bar, then just nothing happens, no file created, and it returns to prompt.&lt;/P&gt;&lt;P&gt;I've also tried, as I showed, using Connect-VIServer directly to the ESXi host, but that's when I hit the actual error.&lt;/P&gt;&lt;P&gt;I'm starting to even play around with trying to use Invoke-RestMethod to pull from the &lt;A href="https://[esxiHostnameFQDN/cgi-bin/vm-support.cgi" target="_blank" rel="noopener"&gt;https://[esxiHostnameFQDN/cgi-bin/vm-support.cgi&lt;/A&gt;&amp;nbsp;endpoint. But not having much luck with that yet either.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I KNOW there's a way to fetch the log bundle created by an ESXi host (or at least there used to be). I swear I used to do it. I just haven't for several years and it felt I was hitting some kind of configuration issue on my end. Just trying to figure out what (and hoping that this hasn't been deprecated and removed)&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 18:58:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976819#M112590</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-07-11T18:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: What is required in order to have Get-Log -Bundle to work for an ESXi host?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976818#M112589</link>
      <description>&lt;P&gt;They'll tell me to log into each UI and click the 'Get Support Bundle' button. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which as you know works fine for one or two hosts. But when I need to pull from all 40 hosts in our largest cluster or the over 100 we have across our entire production vCenter, automation is the way to go.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 18:51:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976818#M112589</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-07-11T18:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: What is required in order to have Get-Log -Bundle to work for an ESXi host?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976813#M112586</link>
      <description>&lt;P&gt;I see. And I recognize that the description says a vCenter Server. However, the very &lt;A href="https://developer.vmware.com/docs/powercli/latest/vmware.vimautomation.core/commands/get-log/#logBundleSet" target="_self"&gt;Get-Log documentation&lt;/A&gt; you shared in your first response appears to show that VMHost is a valid parameter of that set.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Tocano_0-1689099698071.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102542i0920D94A0B6E271F/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Tocano_0-1689099698071.png" alt="Tocano_0-1689099698071.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I'm not trying to be difficult. I just swear that this used to work - and the Help example and the parameterset documentation seem to reaffirm my memory. And I tend to exhaust trying the more straightforward approach before I adopt more complicated alternatives.&lt;BR /&gt;&lt;BR /&gt;I have no problem taking your recommended approach - as long as zipping the resulting individual log files would satisfy VMware Support as the same as the support bundle generated by the system.&amp;nbsp; Edit: Your approach returns just 4 specific log files, whereas the log bundle created by the host returns dozens of different logs, plus configuration and state files.&lt;BR /&gt;&lt;BR /&gt;Thanks again.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 18:44:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976813#M112586</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-07-11T18:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: What is required in order to have Get-Log -Bundle to work for an ESXi host?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976803#M112581</link>
      <description>&lt;P&gt;I appreciate the prompt response. However, I'm confused:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;&amp;gt; Get-Help Get-Log -Examples&lt;BR /&gt;&lt;BR /&gt;NAME&lt;BR /&gt;Get-Log&lt;BR /&gt;&lt;BR /&gt;SYNOPSIS&lt;BR /&gt;This cmdlet retrieves entries from vSphere logs.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-------------------------- Example 1 --------------------------&lt;BR /&gt;&lt;BR /&gt;$keys = Get-LogType&lt;BR /&gt;&lt;BR /&gt;Get-Log -Key $keys[0]&lt;BR /&gt;&lt;BR /&gt;Obtain the available keys. Obtains the first log file from the currently connected vCenter Server system.&lt;BR /&gt;-------------------------- Example 2 --------------------------&lt;BR /&gt;&lt;BR /&gt;$vmhost = Get-VMHost Host&lt;BR /&gt;&lt;BR /&gt;$keyList = Get-LogType -VMHost $vmhost&lt;BR /&gt;&lt;BR /&gt;$vmhost | Get-Log -Key $keyList[0] -StartLineNum 1 -NumLines 100&lt;BR /&gt;&lt;BR /&gt;Retrieve the first one hundred log lines for the specified host and key.&lt;BR /&gt;-------------------------- Example 3 --------------------------&lt;BR /&gt;&lt;BR /&gt;Get-VMHost Host | Get-Log -Bundle -DestinationPath "D:\VMHostBundeLog"&lt;BR /&gt;&lt;BR /&gt;Retrieve a bundle log for the specified host.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;(see Example 3)&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 17:56:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976803#M112581</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-07-11T17:56:43Z</dc:date>
    </item>
    <item>
      <title>What is required in order to have Get-Log -Bundle to work for an ESXi host?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976790#M112574</link>
      <description>&lt;P&gt;I can connect to a vCenter and fetch a log bundle for the vCenter itself:&lt;/P&gt;&lt;PRE&gt;&amp;gt; Connect-VIServer -Server vCenterFQDN -Credential (Get-Credential)&lt;BR /&gt;...&lt;BR /&gt;&amp;gt; Get-Log -Bundle -DestinationPath E:\Downloads\&lt;BR /&gt;VERBOSE: 7/11/2023 11:11:07 AM Get-Log Finished execution&lt;BR /&gt;Data&lt;BR /&gt;----&lt;BR /&gt;E:\Downloads\vcsupport-[guid].tgz&lt;/PRE&gt;&lt;P&gt;This works fine.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;However, when I attempt to download a log bundle from an ESXi host, nothing happens.&lt;/P&gt;&lt;PRE&gt;&amp;gt; $vmHost = Get-VMHost esxiHostnameFQDN&lt;BR /&gt;&amp;gt; $vmHost | Get-Log -Bundle -DestinationPath E:\Downloads\&lt;BR /&gt;VERBOSE: 7/11/2023 11:32:35 AM Get-Log Finished execution&lt;BR /&gt;&amp;gt;&amp;nbsp;&lt;/PRE&gt;&lt;P&gt;At which point, nothing happens. No error that I can see. No empty file created. No verbose lines indicating an issue or other information whatsoever. It just returns next prompt and doesn't do anything.&lt;BR /&gt;&lt;BR /&gt;So while it is less than ideal, I decided I'd directly connect to the various ESXi hosts I want to get log bundles from and get the logs individually that way.&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&amp;gt; Connect-VIServer -Server esxiHostnameFQDN -Credential (Get-Credential) # root&lt;BR /&gt;...&lt;BR /&gt;&amp;gt; Get-Log -Bundle -DestinationPath E:\Downloads\&lt;BR /&gt;VERBOSE: 7/11/2023 12:13:39 PM Get-Log Finished execution&lt;BR /&gt;Get-Log: 7/11/2023 12:13:41 PM Get-Log The operation for the entity "[esxiHostnameFQDN]" failed with the following message: "A general system error occurred: Internal error"&lt;BR /&gt;Get-Log: 7/11/2023 12:13:41 PM Get-Log 7/11/2023 12:13:41 PM Get-Log The operation for the entity "[esxiHostnameFQDN]" failed with the following message: "A general system error occurred: Internal error"&lt;/PRE&gt;&lt;P&gt;Well that's not a very helpful error message. And I'm kind of hitting a roadblock.&lt;/P&gt;&lt;P&gt;Perhaps something with permissions? I mean, I'm using an admin (though not &lt;A href="mailto:administrator@vsphere.local" target="_blank"&gt;administrator@vsphere.local&lt;/A&gt;) when connecting to the vCenter. And I'm connecting as root to the ESXi directly. So that doesn't feel like the problem.&lt;/P&gt;&lt;P&gt;I started feeling this might be something like firewall blocking needed ports or some issue with a self-signed certificate or something. However, if - from the same host I'm running the PSConsole - I hit the UI for the host (&lt;A href="https://[esxiHostnameFQDN]/ui" target="_blank" rel="noopener"&gt;https://[esxiHostnameFQDN]/ui&lt;/A&gt;) I can download the log bundle through the&amp;nbsp;/cgi-bin/vm-support.cgi endpoint. So I have the necessary ports open for https and whatever PowerCLI/Connect-VIServer uses to connect to the host. Plus, I'm neither getting any warnings about certificates when I hit that host via PowerCLI nor through the https UI.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I'm at a bit of a loss and am trying to understand what might be going on here.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Any help would be appreciated.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;EnvInfo:&lt;/P&gt;&lt;PRE&gt;&amp;gt; $PSVersionTable&lt;BR /&gt;&lt;BR /&gt;Name Value&lt;BR /&gt;---- -----&lt;BR /&gt;PSVersion 7.3.4&lt;BR /&gt;PSEdition Core&lt;BR /&gt;GitCommitId 7.3.4&lt;BR /&gt;OS Microsoft Windows 10.0.17763&lt;BR /&gt;Platform Win32NT&lt;BR /&gt;PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}&lt;BR /&gt;PSRemotingProtocolVersion 2.3&lt;BR /&gt;SerializationVersion 1.1.0.1&lt;BR /&gt;WSManStackVersion 3.0&lt;/PRE&gt;&lt;PRE&gt;&amp;gt; Get-PowerCLIVersion&lt;BR /&gt;PowerCLI Version&lt;BR /&gt;----------------&lt;BR /&gt;VMware.PowerCLI 13.1.0 build 21624340&lt;BR /&gt;---------------&lt;BR /&gt;Component Versions&lt;BR /&gt;---------------&lt;BR /&gt;VMware Common PowerCLI Component 13.1 build 21605386&lt;BR /&gt;VMware Cis Core PowerCLI Component PowerCLI Component 13.1 build 21605976&lt;BR /&gt;VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 13.1 build 21606170&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;PRE&gt;&amp;gt; $global:DefaultVIServer | Select Version,Build&lt;BR /&gt;&lt;BR /&gt;Version Build&lt;BR /&gt;------- -----&lt;BR /&gt;8.0.1 21860503&lt;/PRE&gt;&lt;PRE&gt;&amp;gt; $vmHost | Select Version,Build&lt;BR /&gt;&lt;BR /&gt;Version Build&lt;BR /&gt;------- -----&lt;BR /&gt;8.0.1 21495797&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 16:56:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/What-is-required-in-order-to-have-Get-Log-Bundle-to-work-for-an/m-p/2976790#M112574</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-07-11T16:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2958401#M111079</link>
      <description>&lt;P&gt;I completely agree. I would love to remove this from our profile.ps1 file. However, as the only workaround we've found to prevent premature transcript termination, it's the only way I've come up with to ensure that logs continue to populate properly until this issue is actually solved.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2023 21:15:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2958401#M111079</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-03-08T21:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2958386#M111077</link>
      <description>&lt;P&gt;Just wanted to clarify that we are able to avoid the premature Stop-Transcript behavior by only pre-importing:&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;&amp;gt; Import-Module VMware.VimAutomation.Common&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;Now, that doesn't mean that other packages don't have the same issue. However, we don't use a great many of the various packages. For example, we do not use anything in the Horizon, NSX, or Cloud packages.&lt;BR /&gt;&lt;BR /&gt;Your mileage may vary, but you may be able to avoid the 4+ minute module loading by identifying the specific packages that you need and seeing if they need to be pre-loaded or not.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Again, this is just a workaround, not a real solution which I think still needs investigated and identified.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2023 19:40:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2958386#M111077</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-03-08T19:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2957439#M111004</link>
      <description>&lt;P&gt;While it doesn't fix the issue, we have found a workaround by adding the &lt;FONT face="courier new,courier"&gt;Import-Module VMware.PowerCLI&lt;/FONT&gt; line to the PS Profile.&lt;BR /&gt;&lt;BR /&gt;This delays the kickoff of scripts a bit and takes more memory than auto-loading only the portions needed by the script, but it allows whatever the piece(s) that stop the transcript to load early, then when the script starts a transcript, the module is already loaded and so doesn't execute whatever it is that stops it.&lt;BR /&gt;&lt;BR /&gt;Again, not ideal, but worked sufficiently for our case. However, I do still think this is a problem that needs to be investigated and resolved.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 15:10:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2957439#M111004</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2023-03-02T15:10:20Z</dc:date>
    </item>
    <item>
      <title>LCM Content Management Change Tracking</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Discussions/LCM-Content-Management-Change-Tracking/m-p/2934803#M386</link>
      <description>&lt;P&gt;Not sure if this is the right place for this, so feel free to direct me elsewhere if it makes sense.&lt;/P&gt;&lt;P&gt;I'm using the LCM Content Management to capture changes to our Automation/Orchestrator content - like cloud templates, resource actions, and vRO packages. However, I'm struggling to find a good, reliable method for keeping track of what has changed. Right now we're just having everyone add stuff to a central list that when we feel we have a solid foundation and we're ready to perform testing, we can go down the list and capture/deploy the modified content. However, this approach has already proven quite fallible to human error and omission. Surely there's a better approach.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is it possible to get an auto-generated list of "here's everything from the capture endpoint that is new/different than the captured content? Same thing with a report on what is different between what's in the captured content vs what's deployed to the various environments.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any suggestions are welcome. I'm certain there has to be something better than just keeping track of a manual list and HOPING we got everything until we deploy and realize we forgot something when we find something breaks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;RR&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 19:24:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Discussions/LCM-Content-Management-Change-Tracking/m-p/2934803#M386</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-10-21T19:24:45Z</dc:date>
    </item>
    <item>
      <title>REST Endpoint for virtual disk uuid</title>
      <link>https://communities.vmware.com/t5/Automation-Tools-Discussions/REST-Endpoint-for-virtual-disk-uuid/m-p/2926964#M1628</link>
      <description>&lt;P&gt;I use PowerCLI and &lt;FONT face="courier new,courier"&gt;$virtualDiskManager.queryvirtualdiskuuid()&lt;/FONT&gt; to fetch a disk's UUID. However, I need to perform this fetch in an environment that cannot run PowerCLI but already has a REST API connection to vSphere. So I'm looking for a vSphere REST API endpoint that provides this data, but I'm struggling to find it.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is there a vSphere REST API endpoint that returns a VM disk UUID?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2022 17:15:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Automation-Tools-Discussions/REST-Endpoint-for-virtual-disk-uuid/m-p/2926964#M1628</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-09-01T17:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2922518#M107690</link>
      <description>&lt;P&gt;That does appear to have a difference.&lt;/P&gt;&lt;P&gt;PS5 stops and closes the transcript.&lt;/P&gt;&lt;P&gt;PS7 does not and works as expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's unfortunate that PS7 isn't a viable option for us in this environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 18:18:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2922518#M107690</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-08-05T18:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921065#M107572</link>
      <description>&lt;P&gt;That's strange.&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;PS &amp;gt; (Get-WmiObject -class Win32_OperatingSystem).Caption&lt;BR /&gt;Microsoft Windows Server 2019 Datacenter&lt;BR /&gt;&lt;BR /&gt;PS &amp;gt; [System.Environment]::OSVersion.Version&lt;BR /&gt;&lt;BR /&gt;Major Minor Build Revision&lt;BR /&gt;----- ----- ----- --------&lt;BR /&gt;10 0 17763 0&lt;BR /&gt;&lt;BR /&gt;PS &amp;gt; $PSVersionTable&lt;BR /&gt;&lt;BR /&gt;Name Value&lt;BR /&gt;---- -----&lt;BR /&gt;PSVersion 5.1.17763.2931&lt;BR /&gt;PSEdition Desktop&lt;BR /&gt;PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}&lt;BR /&gt;BuildVersion 10.0.17763.2931&lt;BR /&gt;CLRVersion 4.0.30319.42000&lt;BR /&gt;WSManStackVersion 3.0&lt;BR /&gt;PSRemotingProtocolVersion 2.3&lt;BR /&gt;SerializationVersion 1.1.0.1&lt;BR /&gt;&lt;BR /&gt;PS &amp;gt; Get-Module -ListAvailable VMware.PowerCLI |ft -AutoSize&lt;BR /&gt;VERBOSE: Populating RepositorySourceLocation property for module VMware.PowerCLI.&lt;BR /&gt;VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCLI\12.7.0.20091289\VMware.PowerCLI.ps1'.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Directory: C:\Program Files\WindowsPowerShell\Modules&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ModuleType Version Name ExportedCommands&lt;BR /&gt;---------- ------- ---- ----------------&lt;BR /&gt;Manifest 12.7.0.20091289 VMware.PowerCLI&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All of our servers experience this behavior.&amp;nbsp;I'll have to try some wider testing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2022 12:52:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921065#M107572</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-07-28T12:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2920920#M107559</link>
      <description>&lt;P&gt;Thank you for the follow up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Steps to reproduce:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Launch powershell 5.1 console with empty profile (no autoloading modules)&lt;/LI&gt;&lt;LI&gt;&amp;gt; $VerbosePreference = "Continue"&lt;/LI&gt;&lt;LI&gt;&amp;gt; Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log&lt;/LI&gt;&lt;LI&gt;&amp;gt; Get-Process&lt;/LI&gt;&lt;LI&gt;&amp;gt; Import-Module VMware.PowerCLI&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;If you open the transcript file, you'll notice that it begins logging lines, but at some point during the middle of that import process, it stops logging and closes the transcript file properly with a&amp;nbsp;Windows PowerShell transcript end and an End time.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As for your troubleshooting suggestion, that was a good idea. And initially, when I opened VMware.VimAutomation.Common.ps1 and commented out the content, and relaunched a new console, the transcript would progress, but still end - just this time at like VMware.VimAutomation.Cis.Core.ps1.&amp;nbsp; When I edited that file and commented out the content, it would progress to VMware.VimAutomation.Core.ps1. And commenting that one resulted in the transcript ending at VMware.VimAutomation.ViCore.Cmdlets.dll - and since I don't know how to edit a dll, that's where I stalled.&lt;/P&gt;&lt;P&gt;This is starting to feel like a line involving ending a running debugging transcript was accidentally left in a function of the compiled code and is getting called at the conclusion of each (or at least many) modules.&lt;/P&gt;&lt;P&gt;Thanks again for your suggestions. I'm still open to any troubleshooting recommendations.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit: Easier steps:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Launch powershell 5.1 console with empty profile (no autoloading modules)&lt;/LI&gt;&lt;LI&gt;&amp;gt; $VerbosePreference = "Continue"&lt;/LI&gt;&lt;LI&gt;&amp;gt; Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log&lt;/LI&gt;&lt;LI&gt;&amp;gt; Measure-Command {Get-VM}&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This will end in an error, but will import less modules and you'll still be able to see the log be stopped and closed prematurely.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 18:15:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2920920#M107559</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-08-05T18:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2919346#M107450</link>
      <description>&lt;P&gt;Just to confirm, this still appears to be an issue in 12.7&lt;/P&gt;&lt;P&gt;We just upgraded from 12.3 and have begun to encounter this very issue.&lt;/P&gt;&lt;P&gt;Right after the line:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\12.7.0.20067789\net45\VMware.VimAutomation.Common.ps1'.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;**********************&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Windows PowerShell transcript end&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;End time: 20220719084406&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;**********************&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;We are now explicitly loading the &lt;FONT face="courier new,courier"&gt;VMware.VimAutomation.Common&lt;/FONT&gt; module in the profile, before we start our script transcript, in order to avoid this issue.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jul 2022 15:08:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2919346#M107450</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-07-19T15:08:11Z</dc:date>
    </item>
    <item>
      <title>Get Project Zone Resource Usage</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/Get-Project-Zone-Resource-Usage/m-p/2821581#M22889</link>
      <description>&lt;P&gt;Is there a way, either through the REST API or through a vRO action, to access a Project's &lt;STRONG&gt;&lt;U&gt;usage&lt;/U&gt;&lt;/STRONG&gt; of a zone resource limits? I understand I can use the /iaas/api/projects/{id} endpoint to fetch a specific Project and get the zones configured for that project, along with the assigned resources limits.&lt;/P&gt;&lt;P&gt;We have a Day2 operation that requires confirming that their resource usage hasn't passed the defined limits. However, while I can fetch the quotas themselves, I'm struggling to identify what the active allocation/usage numbers are.&lt;/P&gt;&lt;P&gt;Any guidance would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jan 2021 15:53:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/Get-Project-Zone-Resource-Usage/m-p/2821581#M22889</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2021-01-08T15:53:33Z</dc:date>
    </item>
    <item>
      <title>vRO 8.2 Call other actions from Powershell action</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-8-2-Call-other-actions-from-Powershell-action/m-p/2815701#M24942</link>
      <description>&lt;P&gt;In a Javascript action, I can call another action with:&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;System.getModule("[moduleName]").[actionName]()&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Is it possible to do similar in a Powershell action?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Dec 2020 04:33:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-8-2-Call-other-actions-from-Powershell-action/m-p/2815701#M24942</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2020-12-09T04:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: Can you add a custom Powershell module to the vRO8 PSCore instance?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-you-add-a-custom-Powershell-module-to-the-vRO8-PSCore/m-p/2291514#M20429</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I see. Thank you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So then it would seem that anytime the code for the PS module(s) gets updated, I would have to repackage and re-import a new version of the action. Is that correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so, that seems ... cumbersome for environments like ours where our set of modules get updated every week or so. Is there a better way I'm not considering? Like maybe Bind Mounts or something? Which would allow us to easily update a folder on the host that gets utilized within the container.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm really trying to figure out how to avoid thinking that the architecture move to containers, which should allow the flexibility to create customized environments with self-contained instances of the code, configurations, and other libraries/modules that a system needs, would actually be MORE difficult than a static appliance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry if it sounds like I'm being critical of you. &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&amp;nbsp; Certainly not my intent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again, I appreciate the help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2020 21:13:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-you-add-a-custom-Powershell-module-to-the-vRO8-PSCore/m-p/2291514#M20429</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2020-10-08T21:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: Can you add a custom Powershell module to the vRO8 PSCore instance?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-you-add-a-custom-Powershell-module-to-the-vRO8-PSCore/m-p/2291512#M20427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So I've been working on this and am a little confused. So I create a folder, add a handler.ps1 script, add whatever module(s) I want to a .\Modules subfolder, and make sure it gets imported by the handler function. Then I zip the whole thing up and upload to an action.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that mean that I need to run this action as effectively an Import-Module step whenever I want to use something from the module?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Sep 2020 16:50:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-you-add-a-custom-Powershell-module-to-the-vRO8-PSCore/m-p/2291512#M20427</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2020-09-04T16:50:20Z</dc:date>
    </item>
  </channel>
</rss>

