The Best Tools You Didn’t Know You Needed – The VESI

Posted on by

Saving one of the best for last. This tool is every bit as awesome as any of the other tools listed this week, and then some. Why? What other tool can you point at your vCenter and with a few clicks, generate a Visio. Yeah, that’s right, virtual infrastructure documentation in a few clicks. It can be pulled down from here.

Check it out:

Managing VMware vSphere 4 with The Virtualization EcoShell from Eric Sloof NTPRO.NL on Vimeo

Have another tool you find useful? Let us know in the comments!

4 thoughts on “The Best Tools You Didn’t Know You Needed – The VESI”

  • Hello,
    very nice and helpful work!!

    I have some trouble in my german Windows XP installation.

    Export to Viso fails with this error message:

    Das Argument kann nicht an den Parameter “Path” gebunden werden, da es sich um eine leere Zeichenfolge handelt. (Join-Path) Bei C:Dokumente und EinstellungenUSERNAMEAnwendungsdatenVizioncoreVirtualization EcoShellScripts4603dc99-244c-4e87-b4ae-b4f0706b4103VMware.ps1:3486 Zeichen:40 + $stencilMyShapesPath = Join-Path -Path <<<< $myShapesPath -ChildPath $Filename

    I checked the script and find out that the registry value:
    HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0VisioApplicationMyShapesPath
    does not exist.

    I set the value manualy to:
    REG_SZ C:Dokumente und EinstellungenUSERNAMEEigene DateienMeine Shapes
    and now it works fine!!

  • This one took me a while to figure out as well. I found that my problem was
    that I had a fresh install of Visio. I shut it down and opened it again,
    which created the registry entry.

    -C

  • Hello,
    very nice and helpful work!!

    I have some trouble in my german Windows XP installation.

    Export to Viso fails with this error message:

    Das Argument kann nicht an den Parameter “Path” gebunden werden, da es sich um eine leere Zeichenfolge handelt. (Join-Path) Bei C:Dokumente und EinstellungenUSERNAMEAnwendungsdatenVizioncoreVirtualization EcoShellScripts4603dc99-244c-4e87-b4ae-b4f0706b4103VMware.ps1:3486 Zeichen:40 + $stencilMyShapesPath = Join-Path -Path <<<< $myShapesPath -ChildPath $Filename

    I checked the script and find out that the registry value:
    HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0VisioApplicationMyShapesPath
    does not exist.

    I set the value manualy to:
    REG_SZ C:Dokumente und EinstellungenUSERNAMEEigene DateienMeine Shapes
    and now it works fine!!

  • This one took me a while to figure out as well. I found that my problem was
    that I had a fresh install of Visio. I shut it down and opened it again,
    which created the registry entry.

    -C

Comments are closed.