New-ClientVM naming bug when TenantName ends in numeric value

[ghost]

When I use TenantName "InTuneTraining987" and create 2x VMs in sequence, the resulting HyperV VM's are named:

• InTuneTraining987_1 (correct)
• InTuneTraining987_9872 (should be InTuneTraining987_2).

When I use TenantName "TestTraining" and create 2x VMs in sequence, the resulting HyperV VM's are named:

• TestTraining_1 (correct)
• TestTraining_2 (correct).

Could this be a bug that affects any TenantName that ends in a numeric value?

[tabs-not-spaces]

More than likely. I'll review the naming code and try and replicate, remediate.