VMware PowerCLI

The most striking example is the New-AdvancedSetting cmdlet which doesn't allow to create a new advanced settings for an ESXi node.You get the message "VMHosts do not support adding new advanced settings" when you try.And you are forced to use the...

Customer Request: Is it possible to add to New-VM cmdlet ability to define SDRS Automation level (as we are able to do with DRS Automation level via DrsAutomationLevel parameter)? Maybe add another parameter SDrsAutomationLevel or via AdvancedOp...

Currently, to fully standup a SRM Stack, the creation and configuration is done through GUI which prevents us from automating the deployment. There are some SRM cmdlets, but they expect the SRM server to be already deployed. Also, the cmdlets do...

It’d be useful for Service Providers and customers using vCD. I regularly get customers who are familiar with PowerCLI and try to apply the same mindset from Set-VM for vCenter and they’re saddened from it being missing. Easiest way I’ve found to ...

Get HBA Firmware details from Powercli without execute shh to esxi and parsing /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -a.

It seems like currently the only supported way to export/import host customization files in .csv format is through the GUI. It would be nice to have a way to update host customizations programmatically. Being able to export and import these woul...

Currently, Set-DRSClusterGroup does not appear to allow setting the name/label of a DRS VM/Host Group. Something like the following should work to modify the group name:$currentGroupObj = Get-DRSClusterGroup -Name "MyCurrentGroupName"$updatedGroup...

In the PowerCLI Reference add a line that says to which PowerCLI module a cmdlet belongs.

I have read the Customer Experience Improvement Program info that is published. But that documentation doesn't specify in detail what specifically, and at which intervals, is collected in the case of the PowerCLI CEIP. Due to internal security rul...