Apps and tools built by our engineers that are intended to be played with and explored.

PowerCLI Extensions

PowerCLI Extensions


Note: The functionality of this Fling has been integrated into a release of PowerCLI and due to this, this Fling has been retired. This means that this Fling will not be updated in the future and comments will not be responded to. However, you can still download this Fling if you are using earlier versions of PowerCLI. Whenever possible, use the latest supported version of PowerCLI, which can be downloaded here.

VMware PowerCLI is one of the most successful command line tools for managing your VMware products. With the many existing cmdlets designed for the system administrator or vSphere Admin, PowerCLI is the easiest and most powerful tool for managing your environment.

PowerCLI Extensions gives PowerCLI users access to early access functionality by extending the core PowerCLI cmdlets to include new experimental features and gives PowerCLI customers the ability to provide early feedback.



System Requirements

The following is a list of prerequisites needed for using PowerCLI Extensions, please ensure you meet these requirements as other versions may not have been tested and cannot be guaranteed to work.

• VMware vSphere PowerCLI 6.0 R1 or higher
• PowerShell V2 or higher


Please follow the below steps to ensure the PowerCLI Extensions is installed correctly in your environment:
1.  Install PowerCLI (Latest release recommended)
2.  Download the PowerCLI Extensions module from the download button on the left.
3.  Right Click the zip file and go to properties, if you have an Unblock button at the bottom press it to unblock the file to prevent a Security Warning when importing the module.
4.  To install the PowerShell module - extract the downloaded ZIP file to your modules directory, for example (C:\Users\MyUser\Documents\WindowsPowerShell\Modules). For additional information on how to install a PowerShell module, see: Installing Modules
5.  Verify that in the above folder there is a sub-folder called VMware.VimAutomation.Extensions. The full path is: C:\Users\MyUser\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Extensions


Change Log


Andrey Anastasov

Staff Engineer PowerCLI Dev

Atanas Atanasov

MTS PowerCLI Dev

Dimitar Milov

MTS PowerCLI Dev
Add Feedback

10 thoughts on “PowerCLI Extensions

  1. Thanh

    Is there any limitation in what guest vm can be enable as instant clone vm, because I have no problem setup an instant clone of a vCenter server and virtual esxi host (nested esxi host), but I am having trouble enable instant clone on the nsx manager guest vm.

    PowerCLI C:\> $parentVM_nsx = Get-VM lab-nsx7

    PowerCLI C:\> $parentVM_nsx

    Name PowerState Num CPUs MemoryGB
    —- ———- ——– ——–
    lab-nsx7 PoweredOn 4 12.000

    PowerCLI C:\> $parentForkVM_nsx = Enable-InstantCloneVM -VM $parentVM_nsx -guestUser “admin” -GuestPassword “Passw0rd123!” -Confirm:$false
    Enable-InstantCloneVM : 8/18/2015 1:43:12 AM Enable-InstantCloneVM Guest Type and Guest OS Family
    have no values for VM ‘lab-nsx7′
    At line:1 char:21
    + $parentForkVM_nsx = Enable-InstantCloneVM -VM $parentVM_nsx -guestUser “admin” – …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidResult: (:) [Enable-InstantCloneVM], VimException
    + FullyQualifiedErrorId : Fling_InstantClone_GuestOperationsHelper_GetGuestType_UnknwnGuest,VMware.VimAu

    1. Alan Renouf

      I havent tried NSX specifically but it looks like it cant work out what the guest OS is, you may have to specify it to the Enable-InstantClone cmdlet using the GuestType Parameter

      1. Thanh

        Hi Alan,

        I got an error InvalidArgument when I added the GuestType parameter.

        PowerCLI C:\> $parentForkVM_nsx = Enable-InstantCloneVM -VM $parentVM_nsx -guestUser “root” -GuestPassword “Passw0rd123!” -GuestType “SUSE Linux Enterprise 11 (64-bit)” -Confirm:$false
        Enable-InstantCloneVM : A parameter cannot be found that matches parameter name ‘GuestType’.
        At line:1 char:107
        + … d “Apple1995!” -GuestType “SUSE Linux Enterprise 11 (64-bit)” -Confirm:$false
        + ~~~~~~~~~~
        + CategoryInfo : InvalidArgument: (:) [Enable-InstantCloneVM], ParameterBindingException
        + FullyQualifiedErrorId : NamedParameterNotFound,VMware.VimAutomation.Extensions.InstantClone.Commands.E

        PowerCLI C:\>

  2. andrew morgan

    This seems to refuse to work for me sadly.

    There are no errors throughout the powershell process, the VM just doesnt “boot”. By this i mean the console window is black, i can’t interact with the VM and the post script run doesnt seem to change the IP. I can see from the performance graph’s some CPU cycles are occuring on the VM, but nothing on screen.

    I’ve tried windows 7 and 8. Both exhibiting the same outcome.

    1. Alan Renouf

      When the VM has been marked as a parent you will correctly see that the VM has become a live template and you will experience the console being black. Once you then create the children you should be able to access these machines. The parent will stay unavailable until powered off/on.

      1. Andrew Morgan

        interestingly it was the guests i couldnt open the console for. Turns out neither the older vSphere client nor the enhanced console would work, only the web based console would show the contents.

        Any-who, with the web based console i could proceed.

        1. Jose Luis Gomez

          Hi Andrew,

          I had the same issue with the console. It only works through web client.

          About scripts, rpctools didn’t work for me with Windows OS. I changed it for vmtoolsd –cmd and works good.

          Jose Luis Gomez

    1. William Lam

      Please take a look at the documentation (PDF download), it includes several examples on how the new cmdlets work.

      You can also find several more examples in the blog posts below:


Leave a Reply

Your email address will not be published. Required fields are marked *