Bug report:
The reason I ask, it was in the announcement demos, but it's not found in the source code demos, and doesn't appear to be working. But I hope it is, and I'm just missing something.
Try and manually load any PowerCLI module with Import-Module and it fails...
The module would be loaded and I can go on my way connecting with Connect-VIServer etc.
Import-Module : The required module 'VMware.VimAutomation.Sdk' is not loaded. Load the module or remove the module from 'RequiredModules' in the file '/root/.local/share/powershell/Modules/VMware.VimAutomation.Common/VMware.VimAutomation.Common.psd1'.
At line:1 char:1
PS /> echo $PSVersionTable
Name Value
PSVersion 6.0.0-alpha
PSEdition Core
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 3.0.0.0
GitCommitId v6.0.0-alpha.9
CLRVersion
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Can you add the output from this command:
Get-Module -ListAvailable
@TryTryAgain what files and folders of PowerCLI do you copy?
@KevinMarquette
PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
PS /root> Get-Module -ListAvailable
Directory: /root/.local/share/powershell/Modules
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Binary 6.0.0.0 VMware.VimAutomation.Cis.Core
Binary 6.3.0.0 VMware.VimAutomation.Cloud
Manifest 6.3.0.0 VMware.VimAutomation.Common
Manifest 6.3.0.0 VMware.VimAutomation.Core HookGetViewAutoCompleter
Binary 6.0.0.0 VMware.VimAutomation.HA
Binary 1.0.0.0 VMware.VimAutomation.License
Binary 6.0.0.0 VMware.VimAutomation.PCloud
Binary 6.0.0.0 VMware.VimAutomation.Storage
Binary 6.3.0.0 VMware.VimAutomation.Vds
Binary 6.3.0.0 VMware.VimAutomation.vROps
Binary 6.0.0.0 VMware.VumAutomation
Directory: /opt/microsoft/powershell/6.0.0-alpha.9/Modules
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Manifest 1.0.1.0 Microsoft.PowerShell.Archive {Compress-Archive, Expand-Archive}
Manifest 3.0.0.0 Microsoft.PowerShell.Host {Start-Transcript, Stop-Transcript}
Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Content, Clear-Content, Clear-ItemProperty, Join-Path...}
Manifest 3.0.0.0 Microsoft.PowerShell.Security {Get-Credential, Get-ExecutionPolicy, Set-ExecutionPolicy, ConvertFrom-SecureString...}
Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Format-List, Format-Custom, Format-Table, Format-Wide...}
Binary 1.0.0.1 PackageManagement {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script 3.3.9 Pester {Describe, Context, It, Should...}
Script 1.0.0.1 PowerShellGet {Install-Module, Find-Module, Save-Module, Update-Module...}
Script 0.0 PSDesiredStateConfiguration {StrongConnect, IsHiddenResource, Write-MetaConfigFile, Get-InnerMostErrorRecord...}
Script 1.2 PSReadLine {Get-PSReadlineKeyHandler, Set-PSReadlineKeyHandler, Remove-PSReadlineKeyHandler, Get-PSReadlineOption...}
@verdel
I only copied the Modules folder from a Windows PowerCLI Infrastructure folder to the /root/.local/share/powershell/Modules folder.
@TryTryAgain - I believe the PowerCLI modules are being reworked atm and will be working in a future release of them.
Like a number of the things demo'd they will have been items that are works in progress
The PowerCLI version that was demoed is still not publicly available.
@alanrenouf
Correct, as stated here we currently do not have a publicly PowerCLI Core available module for you to use with PowerShell Core, the existing modules will not work.
Stay tuned as we will announce this on the PowerCLI blog when available.
@alanrenouf Thank you for the confirmation. I look forward to the release/announcement. Great work, very exciting stuff!
Agreed, very exciting :)
Question appears to be answered, closing as resolved. Please let me know if reopening the issue is necessary.