Get-VMGuestNetworkInterface question

[mal_michael]

Hi, I have a problem with this cmdlet.

Does it (and Set-VMGuestNetworkInterface) should work with Windows Server 2008 guests? I tried win2008 standard 32 and 64 bit, 2008 R2 enterprise.

I allways get "Unable to parse script output." error. With win2003 guests cmdlets work as expected.

Thanks.

[LucD]

Afaik that should work.

Have a look at to check if you're using the correct syntax.

____________

Blog: LucD notes

Twitter: lucd22

[mal_michael]

Thanks, but it is definitely not a syntax issue, cause when i'm running the same command against windows 2003 guest it does work.

[LucD]

I can confirm, I see the same problem.

I suspect, like it said in the other thread, due to the different format of the ipconfig output.

On 2K8 servers the output includes IPv4 and IPv6 entries.

You could try to update the BAT file GetVmGuestNetworkInterface_WindowsGuest.bat that is used yourself

____________

Blog: LucD notes

Twitter: lucd22

[mal_michael]

At least now I know that it is not something spesific to my environment.

I noticed that these cmdlets are experimental as stated in their description. Do you know when they will be fully supported?

I was planning to use them for changing IP addresses in our DR solution. Apparently it is not a good idea (for now).

[LucD]

Perhaps someone from VMW can answer that.

There are other ways to change the IP address of a guest.

____________

Blog: LucD notes

Twitter: lucd22

[mal_michael]

I have some other alternatives to change an IP, but this one looks the most generic and the easiest way.

[nnedev]

Hi,

Currenlty we support only Windows XP/2003 and linux RH 5. We are planning to add more OSs in a future release.

Thanks,

Nedko

Updated: Sorry. It's Windows 2003.

[mal_michael]

Thanks.

1. on XP/ 2000/ RH5 it is fully supported (not experimental), right?

2. What about win2003 ?

3. This is not documented neither in Release notes, nor in cmdlets reference guide.

[nnedev · Accepted solution]

1. The guest network cmdlets are expiremental. If you experience any issues please help us improve the quality by reporting them.

2. I've updated my comment above. The supported OS is 2003 (not 2000).

3. You're right. We have a filed a bug that this should be documented.

Thanks,

Nedko

[mal_michael]

Thanks.

Do you plan to make these cmdlets fully supported in near release?

As I mentioned before, I was planning to use them in our DR solution.

[nnedev]

The parse error is caused by default script for windows OS : GetVmGuestNetworkInterface_WindowsGuest.bat.

The guest cmdlets support implementing custom scripts for the unsupported OSs.

To implement custom script:

1. Go to "Scripts" folder in the PowerCLI installation directory.

2. Create script named <ScriptName>_<OS_Identifier>.bat

<ScriptName> is the name of the cmdlet. ("GetVMGuestNetworkInterface" for example).

<OS_Identifier> is the guest family or the guest ID (as returned by Get-VMGuest).

Look at the already implemented scripts in the folder. They have some information about the expected input/output.

There is a good chance that you can fix the error by just adding getter script for windows 2008. If this doesn't help you should add and setter script.

Thanks.

P.S. If you experience any issues while creating custom script don't hesitate to write in the PowerCLI community.

[admin]

Hello,

We will be adding support for 2k8 as a target guest but not in the next release. You should expect to see the release that supports it toward the end of 2010.

=====

Carter Shanklin

Read the PowerCLI Blog
[Follow me on Twitter|http://twitter.com/cshanklin]

[LucD]

Now you spilled the beans that we will see at least 2 releases in 2010

____________

Blog: LucD notes

Twitter: lucd22

[admin]

Current strategy is to release about every 6 months or so. This isn't a secret.

=====

Carter Shanklin

Read the PowerCLI Blog
[Follow me on Twitter|http://twitter.com/cshanklin]

[mal_michael]

Carter, thanks for the info.

[picou]

Hi,

Is there anything new on this front? We've implemented DR scripts based on this cmdlet and we can't use them with Win2K8 guests.

Tks. René

[Jawdat]

Yeh, are there any updates yet! This is now nearly 9 months later and there don't seem to be support for Windows 2008. I still get the error: [Unable to parse script output.] when I use this cmdlet on 2008 GOS.

Thanks.

[RvdNieuwendijk]

Have you upgraded to vSphere PowerCLI 5.0 yet? According to the VMware vSphere PowerCLI Change Log the VMGuestNetworkInterface cmdlets now support Windows Server 2008 and Windows 7.

I did a little test and it works for me.

Regards, Robert

[Jawdat]

Not yet, I will be doing so later and will tell you how these Guest cmdlets are behaving.

Thank you Robert for your valuable input.

Jawdat