Comments on: Better console for PowerShell and VITK http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/ Informed Virtualization Criticism Fri, 30 Jul 2010 12:54:25 -0700 http://wordpress.org/?v=2.9.1 hourly 1 By: Tao Yue http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-10983 Tao Yue Wed, 21 Jul 2010 04:26:29 +0000 http://www.vcritical.com/?p=584#comment-10983 The way that Console2 works is that it brings up a standard console window far off-screen, hiding it, then screen-scraping and sending keystrokes to the (real) console window. So if the authentication window sometimes pops up in the background, just be happy that it doesn't pop-up offscreen! The way that Console2 works is that it brings up a standard console window far off-screen, hiding it, then screen-scraping and sending keystrokes to the (real) console window.

So if the authentication window sometimes pops up in the background, just be happy that it doesn’t pop-up offscreen!

]]> By: Eric Gray http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-9731 Eric Gray Sat, 06 Mar 2010 06:20:13 +0000 http://www.vcritical.com/?p=584#comment-9731 Thanks, Tim! Thanks, Tim!

]]> By: TimC http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-9728 TimC Sat, 06 Mar 2010 05:28:20 +0000 http://www.vcritical.com/?p=584#comment-9728 I realize this post is over a year old, but I found it very helpful. With vitk basically being deprecated in favor of powercli, the vi-toolkit line needs to change. Lines 102 and 103 should look like this: <tab title="vSphere PowerCLI" icon="vitk15.ico"> This should all be one line: <console shell="C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" -NoExit -Command ". \"C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-VIToolkitEnvironment.ps1\" "" init_dir="c:\scripts"/> Hopefully someone else that stumbles upon this finds it helpful. I realize this post is over a year old, but I found it very helpful. With vitk basically being deprecated in favor of powercli, the vi-toolkit line needs to change. Lines 102 and 103 should look like this:

<tab title=”vSphere PowerCLI” icon=”vitk15.ico”>

This should all be one line:

<console shell=”C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" -NoExit -Command ". \"C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts\Initialize-VIToolkitEnvironment.ps1\" "” init_dir=”c:\scripts”/>

Hopefully someone else that stumbles upon this finds it helpful.

]]> By: Eric Gray http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-339 Eric Gray Thu, 12 Feb 2009 01:17:30 +0000 http://www.vcritical.com/?p=584#comment-339 Thanks for the updates, guys. Good to hear. Thanks for the updates, guys. Good to hear.

]]> By: Duane Haas http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-338 Duane Haas Wed, 11 Feb 2009 21:21:25 +0000 http://www.vcritical.com/?p=584#comment-338 my issue was i had not downloaded the latest build, probably downloaded the oldest build. got the latest and now all is good my issue was i had not downloaded the latest build, probably downloaded the oldest build. got the latest and now all is good

]]> By: Christian Mohn (h0bbel) http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-337 Christian Mohn (h0bbel) Tue, 10 Feb 2009 08:11:42 +0000 http://www.vcritical.com/?p=584#comment-337 Yay, success! Got it working on 64bit, with the patched Console2 version and edits to the console.xml file! Great stuff! Yay, success! Got it working on 64bit, with the patched Console2 version and edits to the console.xml file! Great stuff!

]]> By: Christian Mohn (h0bbel) http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-336 Christian Mohn (h0bbel) Mon, 09 Feb 2009 21:05:36 +0000 http://www.vcritical.com/?p=584#comment-336 Excellent. I'll try the 64bit build at work tomorrow and revert back. Excellent. I’ll try the 64bit build at work tomorrow and revert back.

]]> By: Eric Gray http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-335 Eric Gray Mon, 09 Feb 2009 20:41:40 +0000 http://www.vcritical.com/?p=584#comment-335 It looks like 64-bit systems have trouble with the 32-bit build. There is a 64-bit build here: http://www.rblasch.org/projects/console/ (get the 142.1 with the extra patch) To get the VI Toolkit to work, you need to edit the console.xml file and add " (x86) after all of the \Program Files references. Christian was on the right track. The problem is you can't edit with the GUI because the command line length is limited in that dialog box. Close Console2 and edit the file. Thanks for the feedback, guys. I'm sure it will help other readers with the same issues. It looks like 64-bit systems have trouble with the 32-bit build. There is a 64-bit build here:
http://www.rblasch.org/projects/console/ (get the 142.1 with the extra patch)

To get the VI Toolkit to work, you need to edit the console.xml file and add ” (x86) after all of the \Program Files references.

Christian was on the right track. The problem is you can’t edit with the GUI because the command line length is limited in that dialog box. Close Console2 and edit the file.

Thanks for the feedback, guys. I’m sure it will help other readers with the same issues.

]]> By: Christian Mohn (h0bbel) http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-334 Christian Mohn (h0bbel) Mon, 09 Feb 2009 13:20:28 +0000 http://www.vcritical.com/?p=584#comment-334 Forgot to mention that everything, but the VI Toolkit, seems to work just fine. :) Forgot to mention that everything, but the VI Toolkit, seems to work just fine. :)

]]> By: Christian Mohn (h0bbel) http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/#comment-333 Christian Mohn (h0bbel) Mon, 09 Feb 2009 13:19:41 +0000 http://www.vcritical.com/?p=584#comment-333 This looks great. I'm having similar problems that Duane has, and it seems like the problem is related to the VI Toolkit setup. I run this on Windows Server 2008 64bit, so the paths to the vim.psc1 file needs to be updated to also include "C:\Program Files (x86)" instead of plain old "C:\Program Files". Sadly I can't seem to get it working either way, as Console2 doesn't seem to like it if I add a new console with : <code> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\VIToolkitForWindows\vim.psc1" -NoExit -Command ". \"C:\Program Files (x86)\VMware\Infrastructure\VIToolkitForWindows\Scripts\Initialize-VITo" </code> as the parameter. It seems to just revert it to "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" and thats it. This looks great. I’m having similar problems that Duane has, and it seems like the problem is related to the VI Toolkit setup. I run this on Windows Server 2008 64bit, so the paths to the vim.psc1 file needs to be updated to also include “C:\Program Files (x86)” instead of plain old “C:\Program Files”.

Sadly I can’t seem to get it working either way, as Console2 doesn’t seem to like it if I add a new console with :

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\VIToolkitForWindows\vim.psc1" -NoExit -Command ". \"C:\Program Files (x86)\VMware\Infrastructure\VIToolkitForWindows\Scripts\Initialize-VITo"
 as the parameter. It seems to just revert it to “C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe” and thats it.

]]>