PowerCLI 4.1.1 and Win 2K8

[YevB]

Grretings,
Does anyone know if PowerCLI 4.1.1 support Win 2K8,

Because I tried to use "Get-VMGuestNetworkInterface",
and I'm gettin' "Unable to parse the command output"
I searched for more inforamtion, I've found some people says,
it's problem with the PowerCLI, Also in the Description of the command,
Says "Supports only Win XP, 2003, and RHEL 5"
Is it true? and hasn't been changed in 4.1.1?
if so it there any other way to set Network configuration for 2K8,
and is there any prediction when PowerCLI will support 2K8,

Best Regards,

Yev Berman.

[LucD]

The Release Notes state W2K8 is supported.

[RvdNieuwendijk · Accepted solution]

Hi Yev,

although PowerCLI is supported on Windows Server 2008, the Get-VMGuestNetworkInterface cmdlet isn't. The problem is that the output of the "ipconfig /all" command has changed with Windows server 2008. This cmdlet uses the "ipconfig /all" command to retrieve the information. What has changed in the "ipconfig /all" output is that the line "IP Address. . . . . . . . . . . . :" has changed into "IPv4 Address. . . . . . . . . . . :". Therefore the cmdlet can't retrieve the IP address anymore.

The file GetVmGuestNetworkInterface_WindowsGuest.bat in the scripts folder of your PowerCLI installation is used to retrieve the information. I'm trying to find out how to change this file to make it work with Windows Server 2008 also.

Regards, Robert

[RvdNieuwendijk]

For the PowerCLI team, this is the error message:

[vSphere PowerCLI] C:\users\robert> get-vm scomp0799 | get-vmguestnetworkinterface -guestcred $gc -hostcred $hc
Get-VMGuestNetworkInterface : 3-3-2011 12:17:39    Get-VMGuestNetworkInterface        Unable to parse script output.
At line:1 char:47
+ get-vm scomp0799 | get-vmguestnetworkinterface <<<<  -guestcred $gc -hostcred $hc
    + CategoryInfo          : InvalidArgument: (:) [Get-VMGuestNetworkInterface], ViError
    + FullyQualifiedErrorId : Client20_VmHostServiceImpl_GetVmGuestNetworkInterface_UnableToParse,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVmGuestNetwo
   rkInterface

[vSphere PowerCLI] C:\users\robert> $error[0].Exception | select *

ErrorId           : Client20_VmHostServiceImpl_GetVmGuestNetworkInterface_UnableToParse
ErrorCategory     : InvalidArgument
TargetObject      :
RecommendedAction :
SessionId         :
ConnectionId      : /VIServer=domain\account@vCenter:443/
Severity          : Error
Message           : 3-3-2011 12:17:39    Get-VMGuestNetworkInterface        Unable to parse script output.
Data              : {ParameterValues}
InnerException    : System.ArgumentOutOfRangeException: Het opgegeven argument ligt buiten het bereik van geldige waarden.
                    Parameternaam: i
                       bij System.Text.RegularExpressions.CaptureCollection.GetCapture(Int32 i)
                       bij System.Text.RegularExpressions.CaptureCollection.get_Item(Int32 i)
                       bij VMware.VimAutomation.ViCore.Impl.V1.Service.VmGuestServiceImpl.GetVmGuestNetworkInterface(VirtualMachineInterop vm, VixLoginInfoInte
                    rop vixLoginInfo)
TargetSite        : VMware.VimAutomation.ViCore.Interop.V1.VM.Guest.VMGuestNetworkInterfaceInterop[] GetVmGuestNetworkInterface(VMware.VimAutomation.ViCore.Int
                    erop.V1.Inventory.VirtualMachineInterop, VMware.VimAutomation.ViCore.Interop.V1.VM.Guest.VixLoginInfoInterop)
StackTrace        :    bij VMware.VimAutomation.ViCore.Impl.V1.Service.VmGuestServiceImpl.GetVmGuestNetworkInterface(VirtualMachineInterop vm, VixLoginInfoInte
                    rop vixLoginInfo)
                       bij VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVmGuestNetworkInterface.DoWork(VIAutomation client, List`1 moList)
HelpLink          :
Source            : VMware.VimAutomation.ViCore.Impl

[vSphere PowerCLI] C:\users\robert> $error[0].Exception.InnerException | select *

Message        : Het opgegeven argument ligt buiten het bereik van geldige waarden.
                 Parameternaam: i
ActualValue    :
ParamName      : i
Data           : {}
InnerException :
TargetSite     : System.Text.RegularExpressions.Capture GetCapture(Int32)
StackTrace     :    bij System.Text.RegularExpressions.CaptureCollection.GetCapture(Int32 i)
                    bij System.Text.RegularExpressions.CaptureCollection.get_Item(Int32 i)
                    bij VMware.VimAutomation.ViCore.Impl.V1.Service.VmGuestServiceImpl.GetVmGuestNetworkInterface(VirtualMachineInterop vm, VixLoginInfoInterop
                  vixLoginInfo)
HelpLink       :
Source         : System

[vSphere PowerCLI] C:\users\robert>

"Het opgegeven argument ligt buiten het bereik van geldige waarden" is Dutch for "The specified argument is outside the range of valid values".

[RvdNieuwendijk]

Another change in the "ipconfig /all" output for Windows Server 2008 is that there is now "(Preferred)" behind the IPv4 Address. Like in:

IPv4 Address. . . . . . . . . . . : 10.90.3.55(Preferred)

[YevB]

Thanks a lot,
We'll try to see if we can  edit the script files,
else we'll wait for the next version of PowerCLI.

[admin]

Hi YevB,

PowerCLI supports Win 2K8. However guest OS related cmdlets New-VMGuestRoute, Get-VMGuestRoute, Remove-VMGuestRoute, Get-VMGuestNetworkInterface and Set-VMGuestNetworkInterface work only against Windows XP, Windows Server 2003, and Linux RedHat Enterprise 5. This behavior is described in the vSphere PowerCLI Cmdlets Reference available online.

We have plans to extend the matrix of currently supported guest operating systems in the next PowerCLI release with Windows 7 64 bit and Windows 2008 Standard 64 bit.

Hope this helps you plan appropriately.

\Vladimir