Deploy including VM Name underscore (_),

[xzpluszone]

env : vSphere Client version: 7.0.0.10400

I discovered something new when including VM Name underscore (_).

It was set up and deployed without any special settings as VM Guest Customization Specification.

After Sysprep is finished, the DNS name underscore (_) is automatically removed.

In unattend.xml there is also a DNS with underscore (_) removed.

Where can I find this special character removal policy? ex > "\, . )" .. 

The documentation has a 15 character limit or so, but I can't find any other policies.

 

 

Thanks in advance. 

[bluefirestorm]

DNS host names cannot have underscores. Here is a Microsoft link for allowed characters for computer name (i.e. which will become a DNS host name in an AD domain)
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou

Here is the VMware customisation documentation
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-CAEB6A70-D1CF-446E-BC64-EC42CDB47117.html

So both the Microsoft and VMware customisation limitations (only alpha characters, digits and hyphens) are just based on DNS host naming limitations.

 

[xzpluszone]

thank you. But,
I know I can't use underscore by FQDN standardization.

What I want to know is that generally "Use the virtual machine name" doesn't cause an error, but removes the underscore(_) special character arbitrarily.

I ask because there is no policy statement about removing random special characters from vmware.

ps : When "Enter a name" is pressed, a special character error occurs according to the policy of the document.

[bluefirestorm]

It is better to stick to the DNS host name limits just to make work easier even though the validation at the VMware customisation is not enforcing it properly (call it a bug) even though the VMware documentation somewhat states it (although not as explicit as the Microsoft link).

Otherwise, it will just come back to bite you one day, if not today, maybe some years down the road.

For example, hypothetically, if these VMs will be migrated to the one of the cloud providers these DNS host name limitations will mostly likely still be enforced.

 

[xzpluszone]

Thank you. eat drink and be Merry~