The stock Windows command prompt (cmd.exe) is pretty limited–if you want to use a better font or copy text in lines instead of clunky rectangular blocks, you need something else. For Windows command-line utilities, PowerShell, and the VI Toolkit (for Windows), I have been using the open-source Console2 with much satisfaction. The tabbed interface is pretty cool:

If that looks interesting, here is what you do:
- Download Console2 (current version is 2.00 Beta, build 142); extract on your system somewhere
- Grab this file with icons and a replacement configuration file (console.xml); extract into the same location
- Make a shortcut to console.exe
- Multiple tabs can be opened during launch by adding -t to your shortcut target (e.g., -t Console2 -t “VI Toolkit”)
- Optional: fix your prompts
My configuration file has a few changes to the mouse behavior:
- Left – select + copy automatically
- Right – paste
- Middle – pop-up menu
If you prefer to not use my entire configuration file, just copy the applicable portions from the <tabs> element.
I hope you have enjoyed this slight diversion from the regular VCritical programming lineup. Thanks for reading.
Related posts:
Tags: PowerCLI, PowerShell, Technical
-
cant seem to get console.exe to run after poping your .xml in. i have all the peices installed (vmware ps extension/powershell/cmd)???? just double click on it and nothing happens
-
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 :
as the parameter. It seems to just revert it to “C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe” and thats it.
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"
-
my issue was i had not downloaded the latest build, probably downloaded the oldest build. got the latest and now all is good
-
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.

RSS Feed
Follow
15 comments
Comments feed for this article
Trackback link: http://www.vcritical.com/2009/02/better-console-for-powershell-and-vitk/trackback/