<?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>DavidGriswoldeB Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>DavidGriswoldeB Tracker</description>
    <pubDate>Wed, 15 Nov 2023 14:02:54 GMT</pubDate>
    <dc:date>2023-11-15T14:02:54Z</dc:date>
    <item>
      <title>Re: ESXi 7.0 ssh session logs filling vcsa database</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/ESXi-7-0-ssh-session-logs-filling-vcsa-database/m-p/2865735#M43941</link>
      <description>&lt;P&gt;You can't disable the SSH service on a Nutanix-backed ESXi cluster. SSH is required for the CVM to communicate with ESXi. I am not saying it is a good or bad decision, it is just a fact.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Sep 2021 17:20:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/ESXi-7-0-ssh-session-logs-filling-vcsa-database/m-p/2865735#M43941</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-09-07T17:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: vCLS VMs hidden</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861384#M43782</link>
      <description>&lt;P&gt;After supporting VMware for 12+ years, I never knew there is a difference. I thought if I granted a person or group Administrator permissions Globally it was the same as adding them to the group.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just added my AD account to the&amp;nbsp;Administrator group, logged out/in with my AD account and I can see the vCLS folder and VMs.&lt;BR /&gt;&lt;BR /&gt;I KNOW that I could see these on an earlier version of 7.0 (u1 obviously) using my AD account. So that behavior did change with u2.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Aug 2021 21:15:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861384#M43782</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-08-09T21:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: vCLS VMs hidden</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861380#M43780</link>
      <description>&lt;P&gt;I just saw your question at the end of your reply asking what account I was logging in with. I was using my privileged domain account, but the &lt;A href="mailto:administrator@vsphere.local" target="_blank"&gt;administrator@vsphere.local&lt;/A&gt;. I logged out and back in using the admin account and now I see all the vCLS.&lt;/P&gt;&lt;P&gt;I am not sure why this is happening. We recently changed our vCenters' authentication from Integrated Active Directory (because it kept creating RC4 cipher Kerberos connections to our domain controllers and InfoSec did not like that) to Active Directory over LDAP.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Our admin team security role still has global admin rights on the vCenter, but now we can't see the vCLS folder or VMs. I wonder what else changed.&lt;/P&gt;&lt;P&gt;This is very strange.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Aug 2021 20:37:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861380#M43780</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-08-09T20:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: vCLS VMs hidden</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861375#M43779</link>
      <description>&lt;P&gt;I should have mentioned that I looked for the vCLS folder as well. It only exists on one cluster (out of 47).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, the powerCLI command only returns those three vCLS.&lt;/P&gt;&lt;P&gt;Again, I can only see the vCLS files on the datastore. They all have .lck files and .log files with current timestamps, and I can't delete the files.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Aug 2021 20:24:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861375#M43779</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-08-09T20:24:22Z</dc:date>
    </item>
    <item>
      <title>vCLS VMs hidden</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861373#M43777</link>
      <description>&lt;P&gt;After upgrading to vCenter 7.0 U2a all cluster VMs (vCLS) are hidden from site using either the web client or PowerCLI, like the vCenter API is obfuscating them on purpose. I see no indication they exist other than in the Files view of the datastores they were deployed on.&lt;/P&gt;&lt;P&gt;So, my questions are: was this on purpose in u2? I suspect there were enough stupid people out there messing with them because they didn't know how to use Google to find out they are needed that VMware made the decision to hide them, but it is a pain in the butt.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a datastore I need to decom and the vCLS VMs were deployed on it and since I can't find them I can't migrate their storage (or know if I should be able to). I turned of cluster DRS hoping that would remove the vCLS VMs, but I still cannot delete the files from the datastore.&lt;/P&gt;&lt;P&gt;Any thoughts or ideas would be appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Aug 2021 20:06:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-hidden/m-p/2861373#M43777</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-08-09T20:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to change port group and IP on management port - at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2861371#M102673</link>
      <description>&lt;P&gt;I gave up on this. There appears to be no way to change both the IP of the management vmKernel interface and it's backing port group, on virtual distributed switches, at the same time via any API. You can do it using standard switches, but not vDS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had to make all of the changes manually in the DCUI via remote console. It was a pain and there needs to be a better way to do this.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Aug 2021 19:38:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2861371#M102673</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-08-09T19:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to change port group and IP on management port - at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853352#M101977</link>
      <description>&lt;P&gt;I figured out my mistake and went back to the original script using&amp;nbsp;DistributedVirtualPort, but unfortunately the change timesout and does not seem execute both changes at the same time. Neither the old static IP on the old portgroup or the DHCP assigned IP on the new portgroup are responding.&lt;/P&gt;&lt;P&gt;I will need to go back to my first idea of adding a new vmkernel NIC and removing vmk0. Not ideal, but it will work.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 20:07:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853352#M101977</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-06-17T20:07:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to change port group and IP on management port - at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853344#M101975</link>
      <description>&lt;P&gt;I am getting a new error now: The Specified Parameter was not correct: VirtualNic.Specification.Portgroup&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DavidGriswoldeB_0-1623958298323.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89589i1F5AB5950E71B4DB/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="DavidGriswoldeB_0-1623958298323.png" alt="DavidGriswoldeB_0-1623958298323.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 19:34:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853344#M101975</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-06-17T19:34:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to change port group and IP on management port - at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853313#M101968</link>
      <description>&lt;P&gt;I updated the script using this instead and I am getting a puzzling error, below. If I just run 'New-Object -TypeName VMware.Vim.HostPortgroup' I can see the structure of the object, but when it is added to '$spec', get-method says it is just string, not the HostPortgroup object.&lt;/P&gt;&lt;P&gt;$spec.Portgroup = New-Object -TypeName VMware.Vim.HostPortgroup&lt;BR /&gt;$spec.Portgroup.Key = $pg.ExtensionData.Key&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DavidGriswoldeB_0-1623948806706.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89587i0916FCEDA44CC8A3/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="DavidGriswoldeB_0-1623948806706.png" alt="DavidGriswoldeB_0-1623948806706.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 16:55:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853313#M101968</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-06-17T16:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to change port group and IP on management port - at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853307#M101967</link>
      <description>&lt;P&gt;I gave this a try and I am hitting an error concerning '&lt;SPAN&gt;DistributedVirtualPort'. I did not think it would be as simple as replacing that with 'Portgroup', but I gave it a try and that did not work either. I assume I need to use a different type with this line as well:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="csharp"&gt;$spec.DistributedVirtualPort = New-Object -TypeName VMware.Vim.DistributedVirtualSwitchPortConnection&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can't I just not include 'DistributedVirtualPort' in the spec and instead use the 'portgroup'&amp;nbsp;&lt;SPAN&gt;Property? If so, I don't know what type to&amp;nbsp;instantiate.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DavidGriswoldeB_0-1623947410329.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89585iA1647FDF6D26A24F/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="DavidGriswoldeB_0-1623947410329.png" alt="DavidGriswoldeB_0-1623947410329.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 16:46:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853307#M101967</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-06-17T16:46:00Z</dc:date>
    </item>
    <item>
      <title>How to change port group and IP on management port - at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853097#M101939</link>
      <description>&lt;P&gt;I have gone around in circles on this, but using PowerCLI I cannot find a way to change a vmkernel NIC's port group AND IP at the same time (actually trying to change to DHCP, but same problem. It seems if you need to change the port group the option to change anything about the IP is not available. So, there is no way to fix this without using a IPMI remote console it seems.&lt;/P&gt;&lt;P&gt;Any suggestions would be appreciated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jun 2021 22:28:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-change-port-group-and-IP-on-management-port-at-the-same/m-p/2853097#M101939</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-06-16T22:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: host profile and associated hosts via powercli</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/host-profile-and-associated-hosts-via-powercli/m-p/2843439#M101195</link>
      <description>&lt;P&gt;Sorry about necroing a 3 year old thread, but is there a reference back to Auto Deploy rules? We do not apply Host Profiles directly to clusters or ESXi hosts, so there is not a MoRef to those objects.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I know I can just run Get-DeployRuleSet to see which Host Profiles are referenced to which rules, but looking for a one-liner that will do both for me, if possible.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 20:50:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/host-profile-and-associated-hosts-via-powercli/m-p/2843439#M101195</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-04-22T20:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to lists Windows Drive letter and VM Disk number in Data center ?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842680#M101134</link>
      <description>&lt;P&gt;Crap - my ESXi hosts are still on 6.7 and ESXi 7.0 is required. I didn't find that specific piece of info until I checked out Part II of Cody's post.&lt;/P&gt;&lt;P&gt;I will move forward with my script that will work in both 6.7 and 7.0. It is not perfect because I am depending on the drives returned by Get-HardDrive to have been added in the same order they appear in the Get-VMGuestDisk. I will need to add some additional logic to verify.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 21:00:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842680#M101134</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-04-19T21:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to lists Windows Drive letter and VM Disk number in Data center ?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842639#M101129</link>
      <description>&lt;P&gt;Thank you for the RTFM response, and I am mostly kidding. I thought I had provided all the required info to show that I had already double-checked the prerequisites listed &lt;A href="https://blogs.vmware.com/PowerCLI/2020/04/new-release-powercli-12.html" target="_self"&gt;here&lt;/A&gt;. I did notice that the VM was still on an old version of virtual hardware, and upgraded it to v15. However, I am still getting the same results. I even checked the &lt;A href="https://developer.vmware.com/docs/powercli/latest/vmware.vimautomation.core/commands/get-harddisk/#ByVMGuestDisk" target="_self"&gt;Developer Documentation&lt;/A&gt; on the command and found nothing additional. Any suggestions?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 17:08:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842639#M101129</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-04-19T17:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to lists Windows Drive letter and VM Disk number in Data center ?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842623#M101122</link>
      <description>&lt;P&gt;Thanks for the reply, but it is still not working for me. Here is what I am working with:&lt;/P&gt;&lt;P&gt;PowerCLI 12.2&lt;BR /&gt;VMware Tools 11.2.97 installed on the target VM&lt;BR /&gt;vCenter 7.0.1&lt;/P&gt;&lt;P&gt;when I run the commands, this is what I get:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DavidGriswoldeB_0-1618846797168.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/88263iDCD895F003821E6A/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="DavidGriswoldeB_0-1618846797168.png" alt="DavidGriswoldeB_0-1618846797168.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 15:40:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842623#M101122</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-04-19T15:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to lists Windows Drive letter and VM Disk number in Data center ?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842331#M101099</link>
      <description>&lt;P&gt;It's been a couple of months and I am just getting back to this after getting our vCenters upgraded to 7.0. The command Get-VMGuestDisk is useful, but it does not appear to give the details of SCSI device or the VMDK's location in storage. It does contain a reference back to the VM object (VMGuest), but no&amp;nbsp;clear way to like the GuestDisks to VMDKs, like a UID or objectID.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 21:07:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2842331#M101099</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-04-16T21:07:55Z</dc:date>
    </item>
    <item>
      <title>Re: host profile root password script update</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/host-profile-root-password-script-update/m-p/2836870#M100474</link>
      <description>&lt;P&gt;We were about to head down this road and I found this thread. I am going to assume nothing has changed since 6.5 (we are mostly on 7.0)?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Mar 2021 14:55:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/host-profile-root-password-script-update/m-p/2836870#M100474</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-03-19T14:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to lists Windows Drive letter and VM Disk number in Data center ?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2829245#M99682</link>
      <description>&lt;P&gt;I have PowerCLI 12.0.1 installed, but we are still on vSphere 6.7, so we get this message:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DavidGriswoldeB_0-1613069621173.png" style="width: 1378px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/86750i0FDD491B376C6228/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="DavidGriswoldeB_0-1613069621173.png" alt="DavidGriswoldeB_0-1613069621173.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 18:54:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2829245#M99682</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-02-11T18:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to lists Windows Drive letter and VM Disk number in Data center ?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2829232#M99678</link>
      <description>&lt;P&gt;I know this is an old thread, but I took some snippets from the code included and built something that works with VMware 6.7. The next step is including the process to expand the VMDK and then expand in the OS. I will post that script in a new thread once it is working. Note: I wanted Size, not Lable, but that is an easy change.&lt;/P&gt;&lt;P&gt;$vmName = 'MyVM'&lt;BR /&gt;$user = 'domain\user'&lt;BR /&gt;$pswd = 'password'&lt;/P&gt;&lt;P&gt;$secPswd = ConvertTo-SecureString -String $pswd -AsPlainText -Force&lt;BR /&gt;$cred = New-Object System.Management.Automation.PSCredential ($user, $secPswd)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;$code = @'&lt;BR /&gt;$compName = '.'&lt;BR /&gt;$test = $null&lt;BR /&gt;foreach($disk in (Get-CimInstance -ComputerName $compName -ClassName Win32_DiskDrive)){&lt;BR /&gt;foreach($partition in (Get-CimAssociatedInstance -InputObject $disk -ResultClassName Win32_DiskPartition)){&lt;BR /&gt;Get-CimAssociatedInstance -InputObject $partition -ResultClassName Win32_LogicalDisk | %{&lt;BR /&gt;$test += "$($disk.SCSIBus):$($disk.SCSITargetId)","=",($_.DeviceID),"|",[math]::round($_.size/1024/1024/1024) -join ""&lt;BR /&gt;$test += "`r`n"&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;$test&lt;BR /&gt;'@&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;$vm = Get-VM -Name $vmName&lt;/P&gt;&lt;P&gt;$sInvoke = @{&lt;BR /&gt;VM = $VM&lt;BR /&gt;ScriptType = 'Powershell'&lt;BR /&gt;ScriptText = $code&lt;BR /&gt;GuestCredential = $cred&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;$volTab = @{}&lt;BR /&gt;$volTab = Invoke-VMScript @sInvoke | Select -ExpandProperty ScriptOutput | ConvertFrom-StringData&lt;/P&gt;&lt;P&gt;$vm = Get-VM -Name $vmName&lt;/P&gt;&lt;P&gt;foreach($ctrl in Get-ScsiController -VM $vm){&lt;BR /&gt;foreach($disk in (Get-HardDisk -VM $vm | where{$_.ExtensionData.ControllerKey -eq $ctrl.Key})){&lt;BR /&gt;$obj = [ordered]@{&lt;BR /&gt;VM = $vm.name&lt;BR /&gt;HD = $disk.Name&lt;BR /&gt;VMDK = $disk.Filename&lt;BR /&gt;Device = "$($ctrl.ExtensionData.BusNumber):$($disk.ExtensionData.UnitNumber)"&lt;BR /&gt;Drive = ""&lt;BR /&gt;Size = ""&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;if($volTab.ContainsKey("$($ctrl.ExtensionData.BusNumber):$($disk.ExtensionData.UnitNumber)")){&lt;BR /&gt;$obj.Drive = $volTab["$($ctrl.ExtensionData.BusNumber):$($disk.ExtensionData.UnitNumber)"].Split('|')[0]&lt;BR /&gt;$obj.Size = $volTab["$($ctrl.ExtensionData.BusNumber):$($disk.ExtensionData.UnitNumber)"].Split('|')[1]&lt;BR /&gt;}&lt;BR /&gt;New-Object -TypeName PSObject -Property $obj&lt;BR /&gt;}&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 18:35:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-to-lists-Windows-Drive-letter-and-VM-Disk-number/m-p/2829232#M99678</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2021-02-11T18:35:27Z</dc:date>
    </item>
    <item>
      <title>Re: q depth of iscsi adapter_powercli</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/q-depth-of-iscsi-adapter-powercli/m-p/1409285#M46723</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I know this is an old thread, but how do these commands change if I want to use ESXCLI v2? I cannot seem to find the correct syntax.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2019 17:39:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/q-depth-of-iscsi-adapter-powercli/m-p/1409285#M46723</guid>
      <dc:creator>DavidGriswoldeB</dc:creator>
      <dc:date>2019-07-25T17:39:24Z</dc:date>
    </item>
  </channel>
</rss>

