VITK 1.5: Disconnect-VIServer fails in PowerGUI

[MrSpock77]

Since upgrading to VITK 1.5 i get this error when executing Disconnect-VIServer in PowerGUI:

The method or operation is not implemented. At :line:121 char:19 + Disconnect-VIServer <<<< -Confirm:$false

It did not occur in VITK 1.0. According to this post in the PowerGUI forums there is a problem with the error handling in VITK.

Which version of the VMware Toolkit for Windows are you using? If you are using version 1.0 or 1.0U1 from VMware,

you should not see any errors regarding Window Title. If you are using the Beta release of the 1.5 Toolkit, VMware

had included a method of changing the Window title in the standard PowerShell Window when a Connect-VIServer

or Disconnect-VIServer command is issued. I don't know why this would appear in standard mode vs. Debug. I will

test this further tomorrow morning and report back.

If you are using a 1.5 Beta release, this will also need to be reported to VMware, as their Try-Catch method for

standalone IDE editors may not be working as we are both anticipating for unsupported functions (Which would impact

more than PowerGUI).

Scott

[halr9000]

I've notified Quest. They should respond quickly, they always do.

[PowerShell MVP|https://mvp.support.microsoft.com/profile=5547F213-A069-45F8-B5D1-17E5BD3F362F], VI Toolkit forum moderator

Author of the upcoming book: Managing VMware Infrastructure with PowerShell

Co-Host, PowerScripting Podcast (http://powerscripting.net)

Need general, non-VMware-related PowerShell Help? Try the forums at PowerShellCommunity.org

[ykalchev]

Hi,

Thanks for reporting this issue. As powerGUI guys described it's caused by the new feature we've added to change console title on connect/disconnect. The problem with the PowerGui (and other apps that implement ps host) is that they do not implement the console title set method and the attempt to change title fails with described exception.

It's the last thing that Disconnect-ViServer does so the workaround here is to simply catch this exception - the disconnect operation is already done successfully at this point.

Regards,

Yasen

[Poshoholic]

Hi there,

I already have this fixed locally in the VMware PowerPack and I will be posting that fix with some other updates tomorrow on the PowerGUI site. Also this issue will also go away in an upcoming release of PowerGUI, whether you are using the VMware PowerPack or not. Anyhow, I'll reply back here again once I've posted the update with the fix.

--

Kirk Munro

Poshoholic

http://poshoholic.com