VC Allows Unsupported Characters

[Xitor]

We had an issue today where someone created a folder in the data center with a period and em dash in it. While VC was perfectly happy creating this, after that user then cloned a VM into that folder they were presented with an error that they couldn't start up the VM because the path did not exist. Logging into the host the offending characters had been removed from the name.

Is there a list of folder name / VM name restrictions that VC may accept, but isn't supported by the Unix kernal? Max character length, and characters to avoid?

Thanks in advance.

[masaki]

Avoid spaces and special characters if you want live well and for a long.

a-z,0-9 should be Enough.

[Texiwill]

Hello,

It would be very nice if VC checked the characters and removed all the not so nice ones .,?,&,#, etc. Yet it does not. I would submit a feature request to VMware to do so.

underscore in addition to the ones masaki mentioned are what I use.

Best regards,

Edward

[masaki]

This is a good idea Texiwill.

I think VC has to grow a lot on Control Features.

[Texiwill · Accepted solution]

Hello,

Well VC is a windows application and .NET has windows controls for characters but they are interacting with Linux and they have not really accounted for that in how things are named. They have handled this somewhat on interaction with ESX but it is not perfect.

Best regards,

Edward