VMware PowerCLI

The Best User Interface for your VMware Datacenter!

Tags and TagCategories in VCSA are case-sensitive, to test if a tag already exists you have to know the exact case. Please add an option to the tagging cmdlets to make it behavior case-insensitive.

  • Marcel Swartjes
  • Jan 5 2018
  • Attach files
  • Steve Kaplan commented
    January 05, 2018 22:09

    What version of PowerCLI are you using? I just tested with 6.5.4, and it definitely is not case sensitive.

  • Steve Kaplan commented
    January 05, 2018 22:10

    Secondary question, how are you doing this checking? I specifically went and used the -Name parameter on both Get-Tag and Get-TagCategory... and both returned regardless of case on the string.

  • Kyle Ruddy commented
    January 05, 2018 23:15

    Marcel, thanks for the heads up. I have filed a bug to get this issue resolved. 

  • Kyle Ruddy commented
    January 05, 2018 23:16

    Adding to Steve's comments, we found out that there is a vCenter version dependency with this issue. vCenter 6.5 is the one experiencing the issue, vCenter 6.0 behaves as expected. 

  • Angel Evrov commented
    January 24, 2018 13:51

    Hi Marcel,

    The bug is logged internally. 

    In the meantime - a workaround is to use some wildcard characters in the -Name parameter of Get-Tag. This will force the filtering to be done client-side which is case-insensitive. For example: you can just put one of the characters of the name in square brackets (square brackets indicate a range of characters so the new filter will be equivalent to the one without brackets):

    Get-Tag -Name "[T]agName"