Hi,
is there any rule or something that Organization vDC name can't have characters like space?
Let's say I have organization named "Test vDC" and the name is accepted by vCD. But when I am using PowerCLI to get VMs in this vDC its not working because the field Organization vDC is empty. If I change the name to "Test_vDC" its working OK.
Example
PS C:\user\PowerShell\vCD> get-civm -Org test | select Name, OrgVdc
Name OrgVdc
---- ------
Photon TestvDC
Server-2019 test2
SRV-2016-T… test
SRV-2016-T… TestvDC
SRV-2016-T… TestvDC
SRV-2019-t… TestvDC
PS C:\user\PowerShell\vCD> get-civm -Org test | select Name, OrgVdc
Name OrgVdc
---- ------
Photon
Server-2019 test2
SRV-2016-T… test
SRV-2016-T…
SRV-2016-T…
SRV-2019-t…
Its that a bug in PowerCLI or documentation should have some more details about naming (I only noticed the length limit)?
Besides the length restriction, I'm not aware of any other rules.
Since the name with the blank is accepted, I would assume it is a PowerCLI issue.
I suggest you open an SR.
Contrary to what GSS might claim, you do not need a Developer Support contract for PowerCLI support.
Point them to PowerCLI Support Breakdown, more specifically para 3 & 4
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Besides the length restriction, I'm not aware of any other rules.
Since the name with the blank is accepted, I would assume it is a PowerCLI issue.
I suggest you open an SR.
Contrary to what GSS might claim, you do not need a Developer Support contract for PowerCLI support.
Point them to PowerCLI Support Breakdown, more specifically para 3 & 4
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I thought so. I opened SR.
Thank you.