<?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>UberGeek1 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>UberGeek1 Tracker</description>
    <pubDate>Wed, 15 Nov 2023 14:32:42 GMT</pubDate>
    <dc:date>2023-11-15T14:32:42Z</dc:date>
    <item>
      <title>Re: Migrate Host and VMKernel Adapters to vSS from vDS</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Migrate-Host-and-VMKernel-Adapters-to-vSS-from-vDS/m-p/2236665#M75639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It definitely does look like it's the same thing William addresses and never would've thought of using Add-VirtualSwitchPhysicalNetworkAdapter for this.&amp;nbsp; I'm surprised that it doesn't bomb out with the pNICs assigned to the vDS already, but then again if I would've just RTFM then I would've seen the critical piece:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"This cmdlet adds a host physical NIC to a standard virtual switch. If VMHost virtual network adapters are specified, &lt;STRONG&gt;the cmdlet &lt;SPAN style="text-decoration-line: underline;"&gt;migrates&lt;/SPAN&gt; them to the virtual switch as well&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Note: If VMHost virtual network adapters are specified, &lt;STRONG&gt;the cmdlet &lt;SPAN style="text-decoration: underline;"&gt;migrates&lt;/SPAN&gt; them to the respective port groups&lt;/STRONG&gt; or creates new ones if VirtualNicPortgroup is not specified."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it seems that there's more hidden features in the cmdlet than one would assume with it using the ADD verb.&amp;nbsp; Lesson learned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the response!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Sep 2019 02:23:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Migrate-Host-and-VMKernel-Adapters-to-vSS-from-vDS/m-p/2236665#M75639</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-09-25T02:23:32Z</dc:date>
    </item>
    <item>
      <title>Migrate Host and VMKernel Adapters to vSS from vDS</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Migrate-Host-and-VMKernel-Adapters-to-vSS-from-vDS/m-p/2236663#M75637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm having a brain fart here.&amp;nbsp; I need to move a host from one vCenter to another, and to do this I have to move the vmk interfaces back to vSS so I can unjoin the host from the "source" vCenter and join to the "destination" vCenter and then migrate them to the new vDS.&amp;nbsp; My brain fart is what is the command to move the vmk0 (management) back to vSS from vDS?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The flow I'm planning on is create vSwitch0 if it doesn't exist, create the Standard PG in the correct VLAN for Management, then move one pNIC from the vDS to the vSS, then move the vmk0, and finally move the second pNIC to the vSS, then unjoin from the "source" vCenter.&amp;nbsp; I will then rinse and repeat for the destination vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For background, I have a vCenter that the web client has completely borked itself, and the only option is to migrate to a new vCenter.&amp;nbsp; Doing this manually isn't bad for one or two, or even 10 hosts, but I have almost 200 hosts I need to do this process.&amp;nbsp; So I plan to evacuate a couple hosts, move them to the "destination" vCenter, then use Cross vCenter vMotion to move the VMs to these hosts until I get a chunk moved, move a bunch more hosts, and repeat until complete.&amp;nbsp; Oh, and it's a couple thousand VMs on these hosts, so the more scripted I can make this the better.&amp;nbsp; I already have the Cross vCenter vMotion stuff scripted and such, it's this scripting/automation of moving the host that is alluding me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I figure this out before it's answered, I will post here as I'm hearing a lot of folks are having issues with vCenter Appliance 6.0 U3e having certificate issues internally that breaks inventory service and web client, which is the issue I have that engineering at VMware can't figure out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Sep 2019 21:31:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Migrate-Host-and-VMKernel-Adapters-to-vSS-from-vDS/m-p/2236663#M75637</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-09-24T21:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: VROPS 6.7 : Unable to do capacity planning anymore</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/VROPS-6-7-Unable-to-do-capacity-planning-anymore/m-p/1840424#M11402</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So bypassing the argument about HA Admission Control, because I agree that when I loose a host it's fine, when I loos two hosts, then I would rather have swapping and ballooning than VMs hard down because they can't start.&amp;nbsp; When you have a cluster with 100+ hosts, having multiple host failures is a reality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, if my understanding is correct, you don't need to have HA Admission Control actually enabled for vROps to read the settings, so changing the settings and leaving it disabled will allow vROps to use those numbers to perform it's calculations.&amp;nbsp; If you use capacity calculation based on actual available resources in the cluster, minus some buffer and your largest host, you probably want a PowerCLI script running nightly to automate this calculation and setting.&amp;nbsp; Of course, this is also based on my environment where a cluster of 100+ hosts will not always be the exact same, heck, most aren't even the same generation, but that's how it goes sometimes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either way, I've always found it arrogant that the typical answer from VMware is "You should be running HA Admission Control", and when I ask why, I basically get the "Because the cool kids do" type of answer, not an actual answer based in reality.&amp;nbsp; I do see some edge cases where it would be nice, but for most cases, good capacity planning and watching it is more key than trying to deploy a VM a customer requests only to find out you don't have capacity under HA Admission Control and now have to tell the user "Sorry, you're going to have to wait now".&amp;nbsp; I would rather do that up-front instead of after the fact.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, I relinquish the soap box...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 May 2019 02:43:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/VROPS-6-7-Unable-to-do-capacity-planning-anymore/m-p/1840424#M11402</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-05-14T02:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: Setting RebootRequired Flag using PowerCLI</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-RebootRequired-Flag-using-PowerCLI/m-p/2221269#M74296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was really hoping you wouldn't say that...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 May 2019 21:20:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-RebootRequired-Flag-using-PowerCLI/m-p/2221269#M74296</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-05-13T21:20:48Z</dc:date>
    </item>
    <item>
      <title>Setting RebootRequired Flag using PowerCLI</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-RebootRequired-Flag-using-PowerCLI/m-p/2221267#M74294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What I'm looking to do is set the ExtensionData.Summary.RebootRequired of a VMHost object to true on demand.&amp;nbsp; The reason is then I can have a script that makes a setting change and trigger this flag, then I can have a generic script just look for hosts with the flag, instead of having to be very specific about this host or that host.&amp;nbsp; It seems in some cases, like pushing firmware and drivers from HPe's SPP application this flag get's set, but I cannot figure out for the life of me how to do that.&amp;nbsp; I would even use something ESXCLI based if needbe, but I'm hoping it's not some hidden, partner only API.&amp;nbsp; I also need this backwards compatible back to vSphere 6.0, up through 6.7.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 May 2019 20:06:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Setting-RebootRequired-Flag-using-PowerCLI/m-p/2221267#M74294</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-05-13T20:06:27Z</dc:date>
    </item>
    <item>
      <title>vSphere Update Manager Host Upgrade Images and Baselines - PowerCLI</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Update-Manager-Host-Upgrade-Images-and-Baselines/m-p/457462#M1691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have multiple vCenters, 17 to be exact, and I'm trying to find a way to automate the process of importing an ESXi image into VUM then creating the Host Upgrade baseline.&amp;nbsp; So the added part is I run hardware from multiple vendors, so I have to upload 3 ESXi images to each VUM and create the baselines, so that what, 52 operations across multiple vCenters that I have to do manually.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the answer is not simply "Run one vCenter" or "Use one hardware vendor", the size of the environment and location dictates the architecture and use of multiple vendors.&amp;nbsp; I have a script to create a Host Patch or Host Extension baseline based on an XML file that I export from my "golden master" vCenter, and the script also has the logic to know which baseline to add to each host, on a host by host basis, depending on the hardware so that each host get's the proper baselines and we aren't cross installing stuff that can have issues, like installing the HPe AMS Agent on a Cisco blade, that causes a PSOD every time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My ask here is if anyone knows of a way I can incorporate those manual 52 steps into the logic of my script so that it can also import the ESXi images and create the Host Upgrade baselines.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Mar 2019 19:53:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Update-Manager-Host-Upgrade-Images-and-Baselines/m-p/457462#M1691</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-03-08T19:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: Import Patches to Repository by PowerShell Script</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-Patches-to-Repository-by-PowerShell-Script/m-p/397667#M27</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I can say that this still is missing. &amp;nbsp;My workaround is to use a Shared Repository and manually hack the xml files. &amp;nbsp;What a pain! &amp;nbsp;Just need to be able to easily import a zip file that is a patch, in my case, the Cisco drivers for UCS. &amp;nbsp;Urggghhhhhhh&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Feb 2019 20:01:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-Patches-to-Repository-by-PowerShell-Script/m-p/397667#M27</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-02-18T20:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: Import ISO to VUM</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-ISO-to-VUM/m-p/2244124#M562</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;So anyone know if this is coming? &amp;nbsp;Would be nice to incorporate this into a script for 17 vCenters instead of one by one...&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Feb 2019 19:52:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Import-ISO-to-VUM/m-p/2244124#M562</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2019-02-18T19:52:38Z</dc:date>
    </item>
    <item>
      <title>vROps Multiprocess Monitor PTQL</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-Multiprocess-Monitor-PTQL/m-p/470524#M2352</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anyone know of a good primer for writing PTQL queries? &amp;nbsp;I'm looking for somethign that will tell me what the class and attributes are. &amp;nbsp;For instance, I see that for Windows I can use `Exe.Name.ct` which means look for a process that contains this text in the executable, I think anyway. &amp;nbsp;Using that, is `Exe.Name.eq`? &amp;nbsp;What other options do I have? &amp;nbsp;Can I look for a console host that is being fired by a specific executable?&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I wish there was more documentation on this type of stuff, it's very advanced but very useful and makes vROps really stand apart from other solutions like SCOM and SolarWinds.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2018 18:41:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-Multiprocess-Monitor-PTQL/m-p/470524#M2352</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-11-19T18:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Remove Datastore Non-Distructively</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392406#M45094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Never even thought of that, I will ahve to give that a try in the morning.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 20:59:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392406#M45094</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-09-18T20:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: Remove Datastore Non-Distructively</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392404#M45092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok, so now I'm getting something that I can work with, an error.&amp;nbsp; [Exception calling "DetachScsiLun" with "1" argument(s): "The operation is not allowed in the current state."]&amp;nbsp; So, now I can at least look at logs, hopefully that is.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 19:25:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392404#M45092</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-09-18T19:25:19Z</dc:date>
    </item>
    <item>
      <title>Re: Remove Datastore Non-Distructively</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392402#M45090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes sir, even rebooted several of the hosts.&amp;nbsp; I'm a little baffled to be honest.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 18:56:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392402#M45090</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-09-18T18:56:54Z</dc:date>
    </item>
    <item>
      <title>Re: Remove Datastore Non-Distructively</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392400#M45088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was thinking along those lines and shamelessly used your code to perform the detach on every host in the Datacenter-B, but even with no errors returned the datastore did not detach.&amp;nbsp; That's where my confusion is coming in, so I will review my code but here's what I have.&amp;nbsp; I added in an optional Datacenter parameter so that I can ensure only hosts in a perticular datacenter are detached instead of everything, that could be interesting to do in production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="c#" __jive_macro_name="code" class="jive_macro_code _jivemacro_uid_15372810140968980 jive_text_macro" data-renderedposition="92_8_1232_784" jivemacro_uid="_15372810140968980"&gt;&lt;P&gt;function Remove-SANDatastore&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; [CmdletBinding()]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; param&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; (&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Param(ValueFromPipeline = $true, Mandatory = $true)]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [VMware.VimAutomation.ViCore.Types.V1.DatastoreManagement.Datastore]$Datastore,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Param(Mandatory = $false)]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [string]$Datacenter&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; foreach($ds in $Datastore)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; $hostviewDSDiskName = $ds.ExtensionData.Info.vmfs.extent[0].Diskname&lt;/P&gt;&lt;P&gt;&amp;nbsp; if($ds.ExtensionData.Host)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; $attachedHosts = $ds.ExtensionData.host&lt;/P&gt;&lt;P&gt;&amp;nbsp; foreach($VMHost in $attachedHosts)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; $dataCenterObj = get-vmhost -Id ("HostSystem-$($VMHost.key.value)") | Get-Datacenter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; [bool]$Proceed = $true&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; if($Datacenter)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; if($dataCenterObj.Name -ne $Datacenter)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; $Proceed = $false&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; if($Proceed)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; $hostView = Get-View $vmHost.Key&lt;/P&gt;&lt;P&gt;&amp;nbsp; $StorageSys = Get-View $hostView.ConfigManager.StorageSystem&lt;/P&gt;&lt;P&gt;&amp;nbsp; $devices = $StorageSys.StorageDeviceInfo.ScsiLun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; foreach($device in $devices)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; if($device.canonicalName -eq $hostviewDSDiskName)&lt;/P&gt;&lt;P&gt;&amp;nbsp; {&lt;/P&gt;&lt;P&gt;&amp;nbsp; $LunUUID = $Device.Uuid&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Write-Verbose "Detaching LUN $($Device.canonicalName) from host $($hostview.Name)..."&lt;/P&gt;&lt;P&gt;&amp;nbsp; $StorageSys.DetachScsiLun($LunUUID);&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 14:30:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392400#M45088</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-09-18T14:30:34Z</dc:date>
    </item>
    <item>
      <title>Remove Datastore Non-Distructively</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392398#M45086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have an interesting situation where I have several datastores that are mounted to hosts in different datacenters, but only Datacenter-A is actually running the VMs, Datacenter-B is not executing anything.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; I've tried using the ConfigManager.StorageSystem.DetachScsiLun to no avail.&amp;nbsp; What I need to do is remove the LUNs from Datacenter-B without destroying any VM that is running on Datacenter-A.&amp;nbsp; Maybe there's some API call I'm missing, but I can't seem to figure it out using PowerCLI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2018 21:10:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Remove-Datastore-Non-Distructively/m-p/1392398#M45086</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-09-17T21:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script for vSphere capacity planning</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-for-vSphere-capacity-planning/m-p/2141256#M69586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a bit older of a thread but I figured I would throw my 2 cents in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I ended up doing is creating a new VIProperty on the Cluster object that did all of this and presented it as part of the Cluster object, so I could do a Get-Cluster and have the capacity info there, updated in real-time, whenever I wanted it.&amp;nbsp; This is handy to check capacity before deploying a new VM.&amp;nbsp; Now this does add a couple of seconds to large clusters, but my 61 host cluster takes about 2 seconds to gather all the information required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The other reason I do this is because we use a custom algorithm to calculate capacity, and having it built in this way and always available helps to have the data available whenever we need it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Aug 2018 21:21:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCLI-script-for-vSphere-capacity-planning/m-p/2141256#M69586</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-08-13T21:21:45Z</dc:date>
    </item>
    <item>
      <title>Re: Configuration ESXi via Script</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Configuration-ESXi-via-Script/m-p/449351#M10368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may want to look at using a Kickstart script to perform these actions at install time.&amp;nbsp; That's really the only option I can think of without vCenter because you probably don't have licensing for PowerCLI either.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Aug 2018 20:59:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Configuration-ESXi-via-Script/m-p/449351#M10368</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-08-13T20:59:45Z</dc:date>
    </item>
    <item>
      <title>Create and Configure StorageDRS Cluster Completely in Code</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Create-and-Configure-StorageDRS-Cluster-Completely-in-Code/m-p/1848712#M62204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So I'm racking my brain on this one.&amp;nbsp; I'm trying to create the StorageDRS cluster and perform all of the config via code, and because not everything is in CmdLets yet, I still have to use ConfigSpecs and StorageResourceManager.&amp;nbsp; So what I'm fighting is I keep running into this error everytime I try to perform the &lt;STRONG&gt;ConfigureStorageDrsForPod&lt;/STRONG&gt; action:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exception calling "ConfigureStorageDrsForPod" with "3" argument(s): "The object has already been deleted or has not been completely created"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will put the code at the bottom, but I can confirm that the Datastore Cluster does in fact exist and that this code does something because I can see the reconfigure event in vCenter, but sure trying to figure out where the failure is here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For reference, $dCenter is set to a valid Datacenter object in my vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$dscName = "$($dCenter.Name)_DSC1"&lt;BR /&gt;$dsc = New-DatastoreCluster -Name $dscName -Location $dCenter&lt;BR /&gt;$dsc = $dsc | Set-DatastoreCluster -SdrsAutomationLevel FullyAutomated&lt;/P&gt;&lt;P&gt;$SRMan = Get-View StorageResourceManager&lt;/P&gt;&lt;P&gt;$spec = New-Object VMware.Vim.StorageDrsConfigSpec&lt;BR /&gt;$spec.PodConfigSpec = New-Object VMware.Vim.StorageDrsPodConfigSpec&lt;BR /&gt;$lbSpec = New-Object VMware.Vim.StorageDrsSpaceLoadBalanceConfig&lt;BR /&gt;$ioSpec = new-object VMware.Vim.StorageDrsIoLoadBalanceConfig&lt;/P&gt;&lt;P&gt;$spec.PodConfigSpec.DefaultIntraVmAffinity = $true&lt;BR /&gt;$spec.PodConfigSpec.LoadBalanceInterval = 480&lt;BR /&gt;$spec.PodConfigSpec.Enabled = $true&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;$lbSpec.MinSpaceUtilizationDifference = 10&lt;BR /&gt;$lbSpec.SpaceUtilizationThreshold = 89&lt;/P&gt;&lt;P&gt;$spec.PodConfigSpec.SpaceLoadBalanceConfig = $lbSpec&lt;/P&gt;&lt;P&gt;$ioSpec.IoLatencyThreshold = 10&lt;BR /&gt;$ioSpec.IoLoadImbalanceThreshold = 10&lt;BR /&gt;$ioSpec.ReservablePercentThreshold = 60&lt;BR /&gt;$ioSpec.ReservableThresholdMode = "automated"&lt;/P&gt;&lt;P&gt;$spec.PodConfigSpec.IoLoadBalanceConfig = $ioSpec&lt;BR /&gt;$spec.PodConfigSpec.IoLoadBalanceEnabled = $true&lt;/P&gt;&lt;P&gt;$SRMan.ConfigureStorageDrsForPod($dsc.ExtensionData.MoRef, $spec, $true)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Aug 2018 20:55:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Create-and-Configure-StorageDRS-Cluster-Completely-in-Code/m-p/1848712#M62204</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-08-13T20:55:17Z</dc:date>
    </item>
    <item>
      <title>Re:Pulling all "no data receiving" EPOPS agents</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Pulling-all-quot-no-data-receiving-quot-EPOPS-agents/m-p/2745817#M17823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://vropsserver/suite-api/api/resources?resourceKind=EP%20Ops%20Agent&amp;amp;adapterKind=EP%20Ops%20Adapter&amp;amp;resourceStatus=NO_DATA_RECEIVING" rel="nofollow"&gt;https://vropsserver/suite-api/api/resources?resourceKind=EP%20Ops%20Agent&amp;amp;adapterKind=EP%20Ops%20Adapter&amp;amp;resourceStatus=NO_DATA_RECEIVING&lt;/A&gt;&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;This will pull all EP Ops adapters that are in the NO_DATA_RECEIVING state.&amp;nbsp; You can also do NONE as the resourceStatus.&amp;nbsp; Also, add on &amp;amp;resourceState=STARTED to only show things that have been started, otherwise you will get some returns of adapters that are stopped as well, which may be extra unneeded data.&amp;nbsp; The API docs are pretty good on this,&amp;nbsp;&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://vropsserver/suite-api/docs/rest/index.html" rel="nofollow"&gt;https://vropsserver/suite-api/docs/rest/index.html&lt;/A&gt;&lt;SPAN&gt;, and look for getResources in the index on the left.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2018 21:16:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Pulling-all-quot-no-data-receiving-quot-EPOPS-agents/m-p/2745817#M17823</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2018-04-25T21:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Scheduling in ESXi 6</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/CPU-Scheduling-in-ESXi-6/m-p/2693031#M262708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would lean toward the vendor documentation more than a blog post honestly.&amp;nbsp; Relaxed Co-Scheduling does allow the idle CPU's to have a greater skew by not requiring there always be enough pCPU to schedule every vCPU.&amp;nbsp; The drawback is if you have vCPU's that are always idle, then the skew between the leading vCPU and the trailing vCPU get's to a point where the leading vCPU must be co-stopped to allow the trailing vCPU to catch up.&amp;nbsp; This is important as most operating systems run a tick on each CPU to keep system time and also gauge CPU utilization.&amp;nbsp; When you have vCPU's that are always idle, thanks to Relaxed Co-Scheduling the tick is not scheduled, so the time of return of the tick to the kernel is large, and thus the kernel has no choice but to assume the CPU is being heavily used because these ticks are background priority tasks.&amp;nbsp; Similarly the leading CPU that has to Co-Stop also causes the tick to take a long time to respond, once again making the kernel think the CPU is heavily used.&lt;/P&gt;&lt;P&gt;So while Relaxed Co-Scheduling does allow the vCPU's to become skewed by not requiring every vCPU be scheduled on the host at once, this can lead to both performance increase in some cases but also lead to severe performance degradation because too many vCPU's get assigned to a VM, and the majority of them are idle.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2017 15:39:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/CPU-Scheduling-in-ESXi-6/m-p/2693031#M262708</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2017-11-14T15:39:45Z</dc:date>
    </item>
    <item>
      <title>Re: Balloon Driver Active without Host Contention</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Driver-Active-without-Host-Contention/m-p/2728323#M268993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah that does clear it up, which I would expect, so does restarting tool service.&amp;nbsp; My question is more around why would we see ballooning if the host is not under contention...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jun 2017 19:23:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Balloon-Driver-Active-without-Host-Contention/m-p/2728323#M268993</guid>
      <dc:creator>UberGeek1</dc:creator>
      <dc:date>2017-06-26T19:23:15Z</dc:date>
    </item>
  </channel>
</rss>

