I have PowerCLI installed (and I haven't used Import-Module or Install-Module to install the VMware modules into PowerShell directly).
When I try and use Default (the manual says it should run the command PowerCLI Open-VMConsoleWindow but I see this flash up briefly;
Connect-VIServer is not recognized as the name of a cmdlet, ...
The title of the popup window is 'Windows PowerShell', and not 'VMware PowerCLI 6.5 ...' as it normally is when PowerCLI is loaded.
My 'VMware Console' works - and I believe that uses PowerCLI to do its work.
It just seems that this VM Remote Console | Default is not using PowerCLI like the manual suggests.
Hello Michael,
This is interesting that your VMware Console work, so this mean the integration between RDM and PowerCLI should work properly.
VMware remote console is a bit different, this is the client VMRC of VMware. Do you have the application installed?
What version of RDM are you using?
Are you starting RDM with specific options ? (32-64 bits run as administrator or standard)
Best regards,
David Grandolfo
I installed RDM Enterprise yesterday. So. The latest one; 13.6.7.0 64 bit. I haven't set any specific 'options'.
If I set the VMware Console Type to VMWare VMRC 8.0 it opens the Remote Console fine (I just need to work out the vm-xxx ID for it to work). VMRC is installed and working fine.
But if I set the VMware Console Type to Default (which according to the Help says it will use PowerCLI to initiate the connection), it actually loads a PowerShell window - not a PowerCLI window. And as I haven't installed the VMWare modules into PowerShell, the Connect-VIServer cmdlet isn't found.
I manually loaded PowerCLI and did a Connect-VIServer, and then a Open-VMConsoleWindow and it loads the VMRC application fine.
Hi Michael,
Thanks,
If you open PowerShell outside of RDM you could also confirm that the PowerCLI module are load automaticly.
The Get-Module command help you whit this:
You could also upgrade to the latest version of PowerCLI which is V10. This version is totally integrated in PowerShell.
Best regards,
David Grandolfo
GEt-Module.jpg
Cheers. Well... awkward. I downloaded PowerCLI 6.5.1 assuming that was the latest because it matches the version of my VM software.
I download the 10.2 zip file, and unzipped them into the System32\PowerShell\1.0\Modules directory. My $env:PSModulePath has;
C:\Users\<username>\Documents\WindowsPowerShell\Modules
C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\
C:\Program Files\Veeam\Backup and Replication\ExchangeExplorer\
Upon starting PowerShell, I was able to use the Connect-VIServer command.
Get-Module still only shows;
Manifest Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Content...}
So I'm not sure why the VMware/PowerCLI modules aren't showing up.
It gets further now. But I get this error;
Capture.PNG
I updated VMRC from 8.0 to the latest 10, and now I get this error;
Capture.PNG
Hi Michael,
This error is received from VMRC.exe directly not from RDM. Base on this information I did some Google Search and might find that if you have VMRC and VMware Workstation installed on your computer this might be the issue. Some version isn't compatible together.
I also found information about a corrupt dll.
Could you try to totally uninstall VMRC and reinstalling it. If it doesn't work do you have, VMware Workstation installed on your computer?
Best regards,
David Grandolfo
I don't have Workstation installed, only vSphere Client. Attached screenshot of vSphere applications.
I think I'll just leave it calling the VM ID directly. I think it'll be slightly quicker anyway because it doesn't have to call the PowerCLI command first before opening VMRC. Now it just opens VMRC directly.
Thanks anyway.
Capture.PNG
Thanks,
But I will try to reproduce the error you had. If I'm able to do something we will inform you.
Best regards,
David Grandolfo