Fix: "Import-Module : module cannot be imported because its manifest contains one or more members that are not valid"
If your version of PowerShell is too old, then you may not be able to import the CloudPower module using Import-Module command.
Description of Problem:
Upon running the command "Import-Module CloudPower" you may receive the following error:
The 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\CloudPower\CloudPower.psd1' module cannot be imported because its manifest contains one or more members that are not valid. The valid manifest members are ('ModuleToProcess', 'NestedModules', 'GUID', 'Author', 'CompanyName', 'Copyright', 'ModuleVersion', 'Description', 'PowerShellVersion', 'PowerShellHostName', 'PowerShellHostVersion', 'CLRVersion', 'DotNetFrameworkVersion', 'ProcessorArchitecture', 'RequiredModules', 'TypesToProcess', 'FormatsToProcess', 'ScriptsToProcess', 'PrivateData', 'RequiredAssemblies', 'ModuleList', 'FileList', 'FunctionsToExport', 'VariablesToExport', 'AliasesToExport', 'CmdletsToExport'). Remove the members that are not valid ('RootModule'), then try to import the module again.
This issue can be resolved by installing Windows Management Framework which will upgrade you to PowerShell 3.0.
The error above is noteworthy in that the modules are being installed to the PowerShell folder under C:\Windows and not to the <My Documents>\WindowsPowerShell\Modules folder. The latest version of CloudPower setup package installs the modules in the latter location.
This is known to be an issue with PowerShell v1.0 but we have not tested it on PowerShell v2.0 to see if that's a problem. It is currently assumed that PowerShell v2.0 is the minimum version that will run the CloudPower module.