Jim Moyle
Jim Moyle
As the count property on objects returns non intuitive results as described above, I'd change $ActualValue.Count to ($ActualValue | Measure-Object).count This should fix the issues above.
Although a different solution would need to be included for PoSh 2.0 as measure-object was introduced in 3.0
Having the same issue with Windows 10 20H2
An alternative solution would be to add a hostpoolname as a parameter : `Get-AzWvdApplicationGroup -HostPoolName -ResourceGroupName ` This would bring it inline with other AVD PoSh commands
I'd say reporting back the unscrubbed number is best and then consumers could scrub themselves as you demonstrate if needed.
I'd generally normalise the version number after getting it to do comparisons later, but the reason I say don't do it in evergreen is you never know what people have...