The command get-PowerCliVersion comes from the snapin "". As mentioned previously, adjusting the PsModulePath environmental variable is a valid work around, but the source of the problem lies elsewhere. Running the script as admin is not the solution.
Is this a new feature? needing to run as admin, previous version i didnt need to run elevated If you need more help, visit the PowerCLI community: Get-PowerCLICommunityĬopyright (C) VMware, Inc. Once you've connected, display all virtual machines: Get-VM To show searchable help for all PowerCLI commands: Get-PowerCLIHelp To find out what commands are available, type: Get-VICommand Log in to a vCenter Server or ESX host: Connect-VIServer + FullyQualifiedErrorId : CommandNotFoundException + CategoryInfo : ObjectNotFound: (Get-PowerCLIVersion:String), CommandNotFoundExce PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1:38 char:12 Included, verify that the path is correct and try again.Īt C:\Program Files (x86)\VMware\Infrastructure\vSphere Check the spelling of the name, or if a path was Get-PowerCLIVersion : The term 'Get-PowerCLIVersion' is not recognized as the name of a cmdlet,įunction, script file, or operable program. Not elevated permissions) not all the modules load If I launch PowerCLI as default user (i.e. elevated permissions) all is fine (圆4 and x32) If I launch PowerCLI as administator (i.e. Just installed the 6.0 version of powercli
0 kommentar(er)
