- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Just installed PowerCLI 6.0 on Windows 10 and when I run get-module it doesn't show any of the PowerCLI modules. get-vicommand does show the cmdlets from DeployAutomation and ImageBuilder but none of the vmdlets from core module. Am I missing something here.. Thanks in advance..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
PowerCLI is implemented as a powershell snapin not a module, try Get-PSSnapIn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That is before 6.0. In 6.0, VMware.VimAutomation.Core is also implemented and distributed as module (both snapin and module), in fact only core, imagebuilder,and autodeploy are stil dll-based in 6.0. This is why I'm trying to try to 6.0. Been using Powercli since 1.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi birdylarry,
I have recently installed PowerCLI 6.0 R3 and I just executed "Get-Module" command and it shows all the modules we have as follows:
PowerCLI C:\> Get-Module
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Script 0.0 Initialize-VMware.VimAutomation....
Script 0.0 Initialize-VMware.VimAutomation....
Script 0.0 Initialize-VMware_VimAutomation_Cis
Script 0.0 Initialize-VMware_VimAutomation_Vds
Script 0.0 Initialize-VMware_VumAutomation
Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Content...}
Manifest 3.0.0.0 Microsoft.PowerShell.Security {ConvertFrom-SecureString, ConvertTo-SecureString, Get-Acl, Get-Auth
Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-Variable, Compare-Object...}
Manifest 3.0.0.0 Microsoft.WSMan.Management {Connect-WSMan, Disable-WSManCredSSP, Disconnect-WSMan, Enable-WSMan
Binary 6.0.0.0 VMware.VimAutomation.Cis.Core {Connect-CisServer, Disconnect-CisServer, Get-CisService}
Binary 6.0.0.0 VMware.VimAutomation.Cloud {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, Get-Catalog
Script 6.0.0.0 VMware.VimAutomation.Core
Binary 6.0.0.0 VMware.VimAutomation.HA Get-DrmInfo
Binary 1.0.0.0 VMware.VimAutomation.License Get-LicenseDataManager
Binary 6.0.0.0 VMware.VimAutomation.PCloud {Connect-PIServer, Disconnect-PIServer, Get-PIComputeInstance, Get-P
Manifest 6.0.0.0 VMware.VimAutomation.Sdk
Binary 6.0.0.0 VMware.VimAutomation.Storage {Export-SpbmStoragePolicy, Get-NfsUser, Get-SpbmCapability, Get-Spbm
Binary 6.0.0.0 VMware.VimAutomation.Vds {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, Export-VDPo
Binary 1.0.0.0 VMware.VimAutomation.vROps {Connect-OMServer, Disconnect-OMServer, Get-OMAlert, Get-OMAlertDefi
Binary 6.0.0.0 VMware.VumAutomation {Add-EntityBaseline, Copy-Patch, Get-Baseline, Get-Compliance...}
See if your installation has some issues. I am running PowerCLI on Windows 7.
Also, look for this :
Local Operating System Support
You can install VMware vSphere PowerCLI 6.0 Release 3 on the following operating systems:
| OS Type | 64-Bit |
| Server |
|
| Workstation |
Refer: Compatibility Matrixes for vSphere PowerCLI 6.0 Release 3 |
----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Vikas,
Thanks. Could be because I'm running Windows 10 and Powershell v5.0. Neither are listed in compatibility matrix for PowerCLI 6.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, this seems to be a compatibility issue with Powershell 5. Tried installing PowerCLI 6.0 R3 on Win7 running Powershell 4.0 and it works, able to see all the modules. Upgrading from PowerCLI 5.x to 6.0 on Powershell 5.0 doesn't work either. Hope VMware look into this and add support for Powershell 5.0