Hi,
I've found several issues with the VSC PowerShell module. In the interest of sharing, here are the issues and their solutions:
Issue 1:
The Module fails to import with error 0x80131515 EG:
PS C:\> Import-Module VSC
Import-Module : Could not load file or assembly
'file:///C:\Windows\system32\WindowsPowerShell\v1.0\Modules\VSC\VSC.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
At line:1 char:1
+ Import-Module VSC
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], FileLoadException
+ FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.ImportModuleCommand
Solution:
Extract the “vsc-cmdlets.zip” file to a temporary location. For each file in the extracted VSC folder and subfolers, right click on the file and select properties. Click “Unblock”, “Apply” and “OK” for each file.
Copy the extracted “VSC” folder to the Windows PowerShell module directory (See https://technet.microsoft.com/en-us/library/dd878350%28v=vs.85%29.aspx to determine the appropriate Windows PowerShell Module directory location for your environment)
Issue 2:
The “VSC.dll.config” file may contain the developers IP Address (10.60.170.210)
Solution:
Logon to the VSC server, open a command prompt and run an “ipconfig”.
Open the “VSC.dll.config” file and replace “10.60.170.210” with your VSC servers IP Address. EG
C:\>ipconfig | find /i "ipv4"
IPv4 Address. . . . . . . . . . . : 192.168.100.12
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
</configSections>
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="VscWsApiImplPortBinding"/>
</basicHttpBinding>
</bindings>
<client>
<endpoint address="https://192.168.100.12:9060/wsapi/v1/vscWSApi"
binding="basicHttpBinding" bindingConfiguration="VscWsApiImplPortBinding"
contract="VscAPIs.VscWsApi" name="VscWsApiImplPort" />
</client>
</system.serviceModel>
</configuration>Note: I would recommend creating a DNS Cname alias called “vsc” and update the “VSC.dll.config” file to use the CName alias FQDN rather than hard coding an IP Address. EG
C:\>nslookup vsc Server: testdc01.testlab.local Address: 192.168.100.10 Name: testvc01.testlab.local Address: 192.168.100.12 Aliases: vsc.testlab.local
Issue 3:
The VSC PowerShell modules has system requirement that may not work on older windows operating systems and PowerShell Versions.
Solution:
Check the PowerShell Manifest file included with the VSC module note that the minimum PowerShell version is 3.0 and the .NET framework 4.5 must be installed.
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\VSC\VSC>type VSC.psd1
@@{
ModuleToProcess = ''
ModuleVersion = '1.0'
GUID = '7784ba43-c2d6-44df-a071-5ac409a2cbb7'
Author = 'NetApp'
CompanyName = 'NetApp'
Copyright = 'Copyright (c) 2015 NetApp, Inc. All rights reserved.'
Description = 'Virtual Storage Console PowerShell Toolkit'
PowerShellVersion = '3.0'
DotNetFrameworkVersion = '4.5'
RequiredAssemblies = ''
NestedModules = 'VSC.dll'
FunctionsToExport = '*'
CmdletsToExport = '*'
VariablesToExport = '*'
AliasesToExport = '*'}Verify that the .NET framework 4.5 is installed before attempting to import the VSC PowerShell module.
Open a PowerShell prompt and type the following command:
PS C:\> Get-WindowsFeature | Where-Object {$_.Name -Match "NET-Framework" -And $_.InstallState -eq "installed"}
Display Name Name Install State
------------ ---- -------------
[X] .NET Framework 3.5 Features NET-Framework-Features Installed
[X] .NET Framework 3.5 (includes .NET 2.0 and 3.0) NET-Framework-Core Installed
[X] .NET Framework 4.5 Features NET-Framework-45-Fea... Installed
[X] .NET Framework 4.5 NET-Framework-45-Core InstalledNote: The .NET 4.5 framework is installed by default on Windows Server 2012 R2
Once you've ensured a compatible version of the .NET framework is installed before attempting to import the VSC PowerShell Module then open a PowerShell prompt and type “$PSVersionTable” and press enter, verify that PowerShell version 3.0 is listed in the “PSCompatibleVsersions” property
PS C:\> $PSVersionTable
Name Value
---- -----
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.34014
BuildVersion 6.3.9600.16394
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2
Using these instructions you should be able to import the VSC PowerShell module and connect to the VSC. EG
PS C:\> import-module VSC
PS C:\> Get-Command -Module VSC
CommandType Name ModuleName
----------- ---- ----------
Cmdlet Add-VscDatastore VSC
Cmdlet Add-VscStorageSystem VSC
Cmdlet Connect-VscServer VSC
Cmdlet Disconnect-VscServer VSC
Cmdlet Get-VscConnectionBroker VSC
Cmdlet Get-VscDatastore VSC
Cmdlet Get-VscHostList VSC
Cmdlet Get-VscNasDetails VSC
Cmdlet Get-VscProvisionableStorageSystem VSC
Cmdlet Get-VscProvisioningPolicyNames VSC
Cmdlet Get-VscSanDetails VSC
Cmdlet Get-VscStorageSystem VSC
Cmdlet Get-VscStorageSystemId VSC
Cmdlet Get-VscStorageSystemPrivileges VSC
Cmdlet Get-VscTask VSC
Cmdlet Invoke-VscSpaceReclaim VSC
Cmdlet Mount-VscDatastore VSC
Cmdlet New-VscClone VSC
Cmdlet Remove-VscConnectionBroker VSC
Cmdlet Remove-VscDatastore VSC
Cmdlet Remove-VscStorageSystem VSC
Cmdlet Set-VscDatastoreSize VSC
Cmdlet Set-VscDefaultCredentials VSC
Cmdlet Test-VscDatastoreName VSC
Cmdlet Test-VscPolicyBasedProvisioning VSC
Cmdlet Update-VscConnectionBroker VSC
Cmdlet Update-VscStorageSystem VSC
Cmdlet Wait-VscTime VSC
PS C:\> $vsc = "vsc.testlab.local"
PS C:\> $username = "srv_vmware@testlab.local"
PS C:\> $credentials = $host.ui.PromptForCredential("Connect to ""$vsc""", "Please enter the user name and password", $userName, "")
PS C:\> Connect-VscServer -Server $vsc -Credential $credentials
Connected
Hope this helps!
/Matt
Meet Explore, NetApp’s digital sales platform
Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.
