Check out these instructions. This should do the trick for you to upgrade PowerShellGet: http://shaulov.us/2018/01/13/upgrading-powershellget-1-0-0-1-to-the-latest-version/

There are two gotcha’s that I’ve seen with updating PowerShellGet:
-Sometimes you need to save PowerShellGet locally to install the new version
-Sometimes you have to manually delete the version from the PowerShell Modules folders.

I am also unable to install the dashboard due to the error:

PS C:Windowssystem32> install-module -Name UniversalDashboard -Force
WARNING: The specified module ‘UniversalDashboard’ with PowerShellGetFormatVersion ‘2.0’ is not supported by the
current version of PowerShellGet. Get the latest version of the PowerShellGet module to install this module, ‘UniversalDashboard’.

When trying your suggestion to uninstall:
uninstall-module powershellget -RequiredVersion 1.0.0.1 -Force
it also did not work. The error I received was:

PS C:Windowssystem32> uninstall-module powershellget -RequiredVersion 1.0.0.1 -Force
PackageManagementUninstall-Package : No match was found for the specified search criteria and module names
‘powershellget’.
At C:Program FilesWindowsPowerShellModulesPowerShellGet1.0.0.1PSModule.psm1:2194 char:21
… $null = PackageManagementUninstall-Package @PSBoundParameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : ObjectNotFound: (Microsoft.Power…ninstallPackage:UninstallPackage) [Uninstall-Package]
, Exception
FullyQualifiedErrorId : NoMatchFound,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage

Make sure powercli is up to date. If you open up a console and run this snippet: $ESXiConnectionTest = Connect-VIServer -server $Vcenter -Credential $Credentials -NotDefault

Then immediately typing in this should come out as “True”: $ESXiConnectionTest.IsConnected

As long as the isconnected property shows True it will redirect you to the homepage.

The way the dashboard verifies that the user credentials are correct, is by checking if the “isconnected” property equals “True” from the connect-viserver session. If it’s not, you’ll get the “Your Credentials were not able to authenticate with $VCenter” message. To troubleshoot you might want to open up a separate powershell console, and run this snippet to get connected to VCenter: $ESXiConnectionTest = Connect-VIServer -server $Vcenter

Then see what you get after entering: $ESXiConnectionTest.IsConnected
This should be set to “true”

Make sure .net 4.7.2 is installed. Also, you can use -requiredversion to remove specific module versions: uninstall-module powershellget -RequiredVersion 1.0.0.1 -Force

I am getting the following error message:

WARNING: The specified module ‘UniversalDashboard’ with PowerShellGetFormatVersion ‘2.0’ is not supported by the current version of PowerShellGet. Get the latest version of the
PowerShellGet module to install this module, ‘UniversalDashboard’.

I already installed the latest PowerShellGet, so now I have two versions running in parallel, but it still does not work:

PS C:WINDOWSsystem32> Get-Module -ListAvailable PowerShellGet

Directory: C:Program FilesWindowsPowerShellModules

ModuleType Version Name ExportedCommands
———- ——- —- —————-
Script 2.1.2 PowerShellGet {Find-Command, Find-DSCResource, Find-Module, Find-RoleCapability…}
Script 1.0.0.1 PowerShellGet {Install-Module, Find-Module, Save-Module, Update-Module…}

Any suggestions on what I am missing here?

I think I got everything working right. I even added a line to ignore the invalid cert error. My only hangup now is that login displays “Bad username or password” when using known good un/pw. The error message changes when I use a known bad un/pw to “Connect-VIServer Cannot complete login due to an incorrect user name or password”. Any thoughts on where the authentication piece might be broken?

Thanks and excellent project!

Looks like whatever endpoint your trying to publish the dashboard on doesn’t have the PowerShell Universal Dashboard modules installed. If that’s the case, open up an Administrative Powershell console and type the following to install the modules on that endpoint: Install-Module -Name UniversalDashboard

Make sure that before you use Publish-UDDashboard, that the “Pages” folder is in the C:UDService folder. The Publish-UDDashboard cmdlet will automatically copy over the dashboard.ps1 file to the C:UDService folder, however the dashboard pages that are contained within the “Pages” folder aren’t automatically copied and if these dashboard pages are missing at the time of Publishing, the service won’t start correctly.