13.2.0.22746353
This Windows PowerShell module contains VMware.PowerCLI
Minimum PowerShell version
Install-Module -Name VMware.PowerCLI -RequiredVersion 13.2.0.22746353
Install-PSResource -Name VMware.PowerCLI -Version 13.2.0.22746353
Owners
-
VMware
Copyright
Author(s)
- VMware
Dependencies
| Version | Downloads | Last updated |
|---|---|---|
| 13.2.1.22851661 | 1,925,989 | |
| 13.2.0.22746353 (current version) | 70,779 | |
| 13.1.0.21624340 | 607,742 | |
| 13.0.0.20829139 | 411,805 | |
| 12.7.0.20091289 | 479,388 | |
| 12.6.0.19610541 | 334,043 | |
| 12.5.0.19195797 | 288,579 | |
| 12.4.1.18769701 | 266,724 | |
| 12.4.0.18633274 | 105,336 | |
| 12.3.0.17860403 | 2,783,125 | |
| 12.2.0.17538434 | 160,378 | |
| 12.1.0.17009493 | 332,255 | |
| 12.0.0.15947286 | 655,851 | |
| 11.5.0.14912921 | 452,003 | |
| 11.4.0.14413515 | 177,334 | |
| 11.3.0.13990089 | 135,032 | |
| 11.2.0.12780525 | 516,911 | |
| 11.2.0.12483598 | 19,825 | |
| 11.1.0.11289667 | 65,528 | |
| 11.0.0.10380590 | 65,298 | |
| 10.2.0.9372002 | 45,398 | |
| 10.1.1.8827524 | 46,590 | |
| 10.1.0.8403314 | 28,701 | |
| 10.0.0.7895300 | 38,801 | |
| 10.0.0-beta7… | 128 | |
| 6.5.4.7155375 | 89,473 | |
| 6.5.3.6870460 | 80,244 | |
| 6.5.2.6268016 | 26,686 | |
| 6.5.1.5377412 | 34,294 |
13.2.1.22851661
This Windows PowerShell module contains VMware.PowerCLI
Minimum PowerShell version
Install-Module -Name VMware.PowerCLI
Install-PSResource -Name VMware.PowerCLI
Owners
-
VMware
Copyright
Author(s)
- VMware
Dependencies
| Version | Downloads | Last updated |
|---|---|---|
| 13.2.1.22851661 (current version) | 1,925,989 | |
| 13.2.0.22746353 | 70,779 | |
| 13.1.0.21624340 | 607,742 | |
| 13.0.0.20829139 | 411,805 | |
| 12.7.0.20091289 | 479,388 | |
| 12.6.0.19610541 | 334,043 | |
| 12.5.0.19195797 | 288,579 | |
| 12.4.1.18769701 | 266,724 | |
| 12.4.0.18633274 | 105,336 | |
| 12.3.0.17860403 | 2,783,125 | |
| 12.2.0.17538434 | 160,378 | |
| 12.1.0.17009493 | 332,255 | |
| 12.0.0.15947286 | 655,851 | |
| 11.5.0.14912921 | 452,003 | |
| 11.4.0.14413515 | 177,334 | |
| 11.3.0.13990089 | 135,032 | |
| 11.2.0.12780525 | 516,911 | |
| 11.2.0.12483598 | 19,825 | |
| 11.1.0.11289667 | 65,528 | |
| 11.0.0.10380590 | 65,298 | |
| 10.2.0.9372002 | 45,398 | |
| 10.1.1.8827524 | 46,590 | |
| 10.1.0.8403314 | 28,701 | |
| 10.0.0.7895300 | 38,801 | |
| 10.0.0-beta7… | 128 | |
| 6.5.4.7155375 | 89,473 | |
| 6.5.3.6870460 | 80,244 | |
| 6.5.2.6268016 | 26,686 | |
| 6.5.1.5377412 | 34,294 |
The plug-in allows interaction between and Windows . The plug-in workflow library contains workflows that allow you to manage hosts and run custom operations.
You use the plug-in to call scripts and cmdlets from actions and workflows, and to work with the result. In addition to the standard workflows that come with the plug-in, you can also create custom workflows that implement the plug-in API.
You can use the view in the Client to manage the available resources. You can use the scripting API of the plug-in to develop custom workflows.
plug-in components
The plug-in relies on a number of components to function properly.
and Windows provide the platform for the plug-in, and the plug-in provides interaction between those products. The plug-in can also interact with other components, such as and vSphere PowerCLI.
The plug-in communicates with Windows through the WinRM communication protocol. See Configuring WinRM.
Optionally, you can integrate the plug-in with vSphere PowerCLI and . See PowerCLI Integration with the PowerShell Plug-In.
You can install all components on a local host. The usage, functionality, and communication protocol requirements of the plug-in do not change if and Windows are installed on the same machine.
Access the plug-in API
To access the API Explorer from the Client, click in the Client navigation pane.
To access the API Explorer from the tabs of the workflow, policy, and action editors, click on the left.
The plug-in exposes all objects in the connected hosts in the view.
Within the inventory of the plug-in, you can monitor hosts and their snap-ins and cmdlets. Each remote host can contain snap-ins and each snap-in can contain cmdlets.
Automate & Manage
PowerCLI is the tool millions of customers around the world use to manage and automate their VMware environments. Discover what you can achieve with PowerCLI today.
Whats Possible
# To install PowerCLI just open a PowerShell console and run the command below:
Install-Module -Name VMware.PowerCLI
VMware PowerCLI CMDLET References by Product
VMware vSphere and vSAN
VMware Cloud Director
Provides cmdlets for automating vCloud Director features.
vRealize Operations Manager
Provides cmdlets for automating vRealize Operations Manager features.
VMware Cloud Services
Provides cmdlets for managing VMware Cloud Services.
VMware Cloud on AWS
Provides cmdlets for managing VMware Cloud on AWS features.
VMware HCX
Provides cmdlets for managing VMware HCX features.
VMware Horizon
Provides cmdlets for automating VMware Horizon features.
VMware NSX-T Data Center
Provides cmdlets for managing NSX-T servers.
VMware Site Recovery Manager
Provides cmdlets for managing VMware Site Recovery Manager features.
VMWARE POWERCLI CMDLET REFERENCES BY MODULE
If you need to run PowerCLI on non-Windows systems, you an use Powershell Core, an open-source version of PowerShell that is compatible with Powershell scripts and most modules.
Prerequisites
- Install PowerCLI (see the VMware PowerCLI Installation Guide) on a machine that has network connectivity to your SDDC’s vCenter (see Configure a VPN Connection Between Your SDDC and On-Premises Data Center in the VMware Cloud on AWS Networking and Security guide).
- Use the CMDLET References by Product to find the commands required and their syntax.
- Connect to your SDDC’s vCenter (or other management appliance such as HCX Manager or SRM) following the instructions in the relevant product reference.
Procedure
- Verify that the VM is running the latest version of VMware Tools.
- Verify that you can access the Guest Operations API, either directly or via a simple PowerCLI cmdlet.
You could use a cmdlet like this one to test your ability to reach port 443 on the ESXi host with IP address 10.100.1.1.
PS C:\Users\admin>Test-NetConnection -Port 443 -ComputerName 10.100.1.1
A response of
True or
TcpTestSucceeded indicates a successful test.
Example: Using the PowerCLI Invoke-VMScript Cmdlet
After you establish a network connection that allows traffic to port 443 on your hosts, you can use the Guest Operations API directly, or via PowerCLI as shown here. API and cmdlet requests go to port 443 on the host where the subject VM (Win10-Example here) is running. VMware Tools running on the VM handles the requested guest operations.
PS C:\Users\admin> $vm = Get-VM Win10-Example PS C:\Users\admin> Invoke-VMScript -ScriptText "dir C:\" -VM $vm -GuestUser admin -GuestPassword $passwd" ScriptOutput ------------------------------------------------------ | | Directory: C:\ | | ...
