https://www.why-did-it.fail/tags/powercli/Recent content in PowerCLI on Why did IT failHugo -- gohugo.ioenCopyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.Tue, 16 Mar 2021 00:00:00 +0000https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/Tue, 16 Mar 2021 00:00:00 +0000https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/I am working on enhancing my vSphere release tagging script with the ability to tag the vCenter with a human-readable release name. As shown in the screenshot, it’s easy enough in the UI. Tags applied to the vCenter in the UI However, in PowerCLI there is no commandlet like get-vcenter. After many tries I gave up trying to force the object returned from $global:DefaultVIServers[0] to accept any tag-related operations. Today, I had the idea of working backwards from the assigned tags with Get-TagAssignmenthttps://www.why-did-it.fail/blog/2021-02-set-esxi-release-names-with-tags/Fri, 05 Mar 2021 00:00:00 +0000https://www.why-did-it.fail/blog/2021-02-set-esxi-release-names-with-tags/Update [2022-10-17] The VMware APIs for the KnowledgeBase have introduced a breaking change. This means the releases can no longer be updated without further development. Update [2021-03-09] The repository has been renamed to VMware-vSphere-Release-Tagging as the future scope should include the vCenter as well. Thank you for all the feedback! In this blog post I want to show you a practial application for the automation that I have built in my last project: