Contents

New fling:PowerCLI for VMware Cloud on AWS

Contents

Summary:

This fling provides a community preview of the upcoming PowerCLI commands for managing VMware Cloud on AWS. It comes in the form of a single PowerCLI module and integrates with existing PowerCLI modules.

All commands have been automatically generated. They are still in development, contain known issues, and will change in the future.

https://labs.vmware.com/flings/files/uploads/0/0/0/0/2/2/9/screenshotpowershell.jpg

Also see this detailed blog post: New Release: PowerCLI Preview for VMware Cloud on AWS

Requirements:

Requires PowerCLI 11.0.0 (specifically, the VMware.VimAutomation.Vmc module) and Microsoft Windows.

Instructions:

Step 1 - Installing the module
    Option A - automatic installation from PowerShell Gallery
        Execute:
Install-Module -Name VMware.VimAutomation.VmcPreview -RequiredVersion 1.1.0.12022238

    Option B - manual installation through download from labs.vmware.com
        Unzip the contents of the archive directly into one of PowerShell’s module directories.

       Notes:
           - The PowerShell module directories are listed in the PSModulePath environment variable ($env:PSModulePath).
           - Do not create a subdirectory for the archive’s contents. Unzip directly into the module directory. If the module directory you selected is e.g. ‘C:\Program Files\WindowsPowerShell\Modules’, the resulting path would look like:
C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.VmcPreview\EULA.rtf
           …and not:
C:\Program Files\WindowsPowerShell\Modules\SomeExtraSubdirectoryYouCreatedForTheArchive\VMware.VimAutomation.VmcPreview\EULA.rtf

Step 2 - Running the module
    Execute:
Import-Module -Name VMware.VimAutomation.VmcPreview
    At this point, you can call Connect-VmcServer to connect to VMware Cloud on AWS. 

    Note:
    At this step, if you see an error message about missing required modules, make sure you have PowerCLI already installed and available in one directories listed under $PSModulePath.