PowerCLI lets me execute VDS commands but if I try running add-pssnapin VMware.VimAutomation.Vds it will still fail (even though it's technically already loaded and not needed)
PS C:\> Get-Module -ListAvailable -Name VMware* Directory: C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Modules ModuleType Version Name ...
See more...
PS C:\> Get-Module -ListAvailable -Name VMware* Directory: C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Modules ModuleType Version Name ExportedCommands ---------- ------- ---- ---------------- Binary 6.0.0.0 VMware.VimAutomation.Cis.Core Manifest 6.0.0.0 VMware.VimAutomation.Core Binary 6.0.0.0 VMware.VimAutomation.HA Manifest 6.0.0.0 VMware.VimAutomation.SDK Binary 6.0.0.0 VMware.VimAutomation.Storage Binary 6.0.0.0 VMware.VimAutomation.Vds it's interesting that VMware.VimAutomation.Core is the only one I can add using the add-pssnapin cmdlet do adding any of those other ones work for you? I'm using two difference systems, one of them a clean install of PowerCLI and they all have this same issue.
I managed to get the user's psmodulepath variable to match the machine's, so if it wasn't correct before it certainly is now and also used your script to take care of the vim.psc1 file but the is...
See more...
I managed to get the user's psmodulepath variable to match the machine's, so if it wasn't correct before it certainly is now and also used your script to take care of the vim.psc1 file but the issue still persists. are you actually able to load the VMware.vimautomation.vds snap-in? I'm not even sure if I need this or not but it still seems like the VDS related cmlets are failing Import-Module VMware.VimAutomation.Vds seems to work as suggested earlier in the thread, maybe I can use it to get by for now thanks anyway
I'm having the same issue on v6.0 R1 and cannot get this to work. Get-Module -Name VMware* returns VMware.VimAutomation.Vds in the list, however add-pssnapin VMware.vimautomation.vds fails w...
See more...
I'm having the same issue on v6.0 R1 and cannot get this to work. Get-Module -Name VMware* returns VMware.VimAutomation.Vds in the list, however add-pssnapin VMware.vimautomation.vds fails with the generic message: add-pssnapin : The Windows PowerShell snap-in 'VMware.vimautomation.vds' is not installed on this computer. I can load VMware.VimAutomation.Core without any issues but not the VDS module and therefore all VDS related commands fail when executed from a .ps1 script or native PowerShell, such as get-vdswitch and export-vdswitch. I'm thinking about trying an older version of PowerCLI, just wanted to find out if anyone else out there has the same issue. I am trying to automate exporting our VDS switch configurations and am currently stuck.
