VMware PowerCLI

Unable to capture events of a datastore, it is required specially to monitor any kinda Backup Jobs configured on Datastore only.

Not all cmdlets have the -Server attribute and only function if there is a VIServer connection in the $DefaultVIServers variable. An example New-SpbmRuleSet does not have the -Server attribute and throws an error if there is not a VIServer connect...

If i upload software depots via Webclient I´m currently not able to manage them via PowerCLI. I always have to connect a local depot (.zip) to build a new deploy rule. I just want to have a single point to store my depots.

We need the ability to add shared disks to clustered VMs using vvols. The New-HardDisk doesn't allow defining the UnitID, nor disabling CBT, and enabling the Multi-writer setting, so we have to do this in two API calls. The first is to use New-Har...

Hi, I find it very annoying that you cannot handle a connection failure if Passthrough authentication does not work. Connect-VIServer will ALWAYS ask for credentials if it cannot connect to vCenter and you did not specify the credentials parameter...

Right now we need to use plain tekst username & password for the connect-hvserver This needs to be more secure with a hvcredentialstoreitem for example or using the current users logged on user credentials.

Would it be possible for you to strong-name dlls that are distributed in the VMware PowerCLI package? We would like to distribute them alongside our .NET application, and the lack of strong-naming of your dlls prevents us from strong-naming ours.

In vSphere 6.5 the Cluster default was changed to use Cluster Resource Percentage instead of Slot Size. This only takes effect when you create a cluster using the GUI. If you use New-Cluster it still defaults to Slot Size.

When attempting to reset the status of a ESXi host from disconnected to connected, if the root password has been updated since the host was added to the vCenter, the Set-VMHost command will fail with a login failure. Give us the option to specify ...

Everything is in the title, why does the Get-VIApplianceService cmdlet not return the same information as "service-control --status" from vCSA? In my opinion, the actual cmdlet Get-VIApplianceService don't seem to relevant.