New Year, New Look vCheck

Its been a while since I blogged about vCheck but that doesn’t mean there has been lots of work ongoing with the project, in fact there has been multiple releases and hundreds of pull requests with great new plugins checking for even more issues with your vCenter and lots of bug fixes, in fact this project and the community updating and using it is awesome, here are some the current stats:

  • 954 Commits
  • 64 Contributors (Thanks to all here)
  • 66 Open Issues and 269 Closed Issues

Whats more, one of the most recent releases 6.25 here includes a great new look, the new look is based upon VMwares Clarity framework and personally I think it looks fantastic as you can see below:

vCheck Clarity

Also available (currently in the dev branch) is the brand new dark version of the theme as seen below:

vCheck Clarity Dark

Download for free now!

Download the latest version here:  https://github.com/alanrenouf/vCheck-vSphere/archive/master.zip

And the dev branch version here: https://github.com/alanrenouf/vCheck-vSphere/archive/dev.zip

 

14 thoughts on “New Year, New Look vCheck”

  1. This new UI it’s really much better than simply new look. In mine case, as we have more than 150 plugins running, I opted for make some modifications and adding something that Clarify offers: Grouping NAVBAR by plugins affinity. Each plugin receive a new definition:

    $PluginNavGroup = “General Information”

    And then, an little change on style.ps1 to build the groupping NavBar.

    $TOCHTML = @”

    “@
    $PluginResult | Where-Object {$_.Details} | Group-Object -Property PluginNavGroup | ForEach-Object {
    $TOCHTML += (“”)
    $TOCHTML += (“”)
    $TOCHTML += (“$($_.Name) [$($_.count)]”)
    $TOCHTML += (“”)
    foreach ($pr in $_.Group) {
    $TOCHTML += (“{1}” -f $pr.PluginID, $pr.Title)
    }
    $TOCHTML += (“”)
    $TOCHTML += (“”)
    }
    $TOCHTML += (“”)
    $TOCHTML += (“”)

    return $TOCHTML

    Once more, THANKS!

  2. Thanks Alan!

    I found a minor error in “114 VM Tools Not Up to Date.ps1”. The returned count matches the maximum number shown.

    $FullVM | Where-Object {$_.Name -notmatch $VMTDoNotInclude -and ($_.Runtime.Powerstate -eq “poweredOn” -And $_.Guest.toolsStatus -eq “toolsOld”)} | `
    Select-Object Name, @{N=”Version”;E={$_.Guest.ToolsVersion}}, @{N=”Status”;E={$_.Guest.ToolsStatus}} | Sort-Object Name | Select-Object -First $VMTMaxReturn

    Removing./commenting “Select-Object -First $VMTMaxReturn” returns the correct number.

  3. Does this require PowerCLI? I try to run it and get lots of errors of modules missing and the report is empty for the most part. No data from my environment.

  4. Thanks Alan. I was wondering if there is a setting that must be configured to enable the new UI for the vCheck report. I downloaded the version you’ve linked to, yet running it in my environment still results in the old HTLM report being generated instead of the newer-looking one you show in this article. Any ideas?

      1. @Matt Swint

        Try a different browser. It formats correctly when using chrome. When using IE, the “table of Contents” is at the bottom of the report versus the side.

Leave a Reply