Nutanix 4.0 PowerShell goes GA

I'm pretty sure that provided command cannot produce that output. :(

Why are the first commands using nutanix instead of ntnx? Otherwise you could just use: Get-Command *ntnx*

Yes, 'Get-Command *ntnx*' will work.

I pasted a command-line I used for the Beta version that did not have NTNX in the name.
If you still want to use the original command-lie, add $_.ModuleName

'get-module | ForEach-Object {Get-Command -Module $_} | ForEach-Object {$_.Name,$_.ModuleName}'

That command doesn't work either.
First, Get-Module returns all imported modules. That's not what you want, right?

If all commands had the same prefix (which they don't right now):

Get-Command -Noun NTNX* | Format-Table Name,ModuleName

Here is partial output in freshly started PowerShell session:

PS C:\> get-module | ForEach-Object {Get-Command -Module $_} | ForEach-Object {$_.Name,$_.ModuleName}
Get-IseSnippet
ISE
Import-IseSnippet
ISE
New-IseSnippet
ISE
Add-Computer
Microsoft.PowerShell.Management
Add-Content
Microsoft.PowerShell.Management
Checkpoint-Computer
Microsoft.PowerShell.Management

I really don't understand how can you get info only about Nutinix cmdlets when you don't filter based on their names or module.

No, I don't have them installed on my computer. However, that doesn't change anything. I'm just looking at your command and don't understand how can you get output about Nutanix cmdlets only.

Guys I think I can clear up some confusion, hopefully. :-)

They way Nutanix decided to implement POSH support involves providing a desktop shortcut that launches a batch file to start a new powershell host session. (Similar to PowerCLI). It then runs a set of nested POSH scripts that, among other things like checking some prerequisites, imports all of the Nutanix modules. (There are 21 based on my count).

By like most POSH scripters, I prefer to have all of my modules, both third party and my own, in my existing powershell host configuration. Usually, I add these import steps to my profile. However, it turns out that Nutanix modifies the cmdlet names on import using the –prefix parameter of the ‘Import-Module’ cmdlet. So the snippets of their code look like this:

[string] $nounPrefix = "NTNX"
Import-Module $currFile -WarningAction silentlyContinue -Prefix $nounPrefix

Just before they loop through importing all their modules, they import one set of cmdlets which they consider “common” first that they do NOT put the “NTNX” on.
So to get all of the Nutanix related cmdlets in their “custom” POSH session, you could run the following command:

gcm | ? implementingtype -like "Nutanix*" | ft Name,Modulename

Again, I prefer to import modules in my profile, so I added these two lines which do the trick.

Import-Module "C:\Program Files (x86)\Nutanix Inc\NutanixCmdlets\Modules\Common\Common.dll"
Get-ChildItem -Path 'C:\Program Files (x86)\Nutanix Inc\NutanixCmdlets\Modules' *.dll -recurse | ForEach-Object {Import-Module -Name $_.FullName -WarningAction silentlyContinue -Prefix "NTNX"}

It imports the common module twice, but the second time it modifies it with the “NTNX” prefix. Then as Bjorn and Alexandar mention, you can simply run Get-Command *ntnx* (I get 193 cmdlets).

My request is for Nutanix to fix the cmdlet naming convention natively and to consolidate the modules if possible.