What is required when changing a virtual machine name using the vSphere Web Client?

To rename a VM, the vSphere Web Client must have an active, responsive connection to the ESXi host where the VM resides so that the VM appears in the inventory in an editable state and the rename operation can be committed back to the host. Without host connectivity, the VM may appear grayed out or disconnected, preventing any inventory-level edit including a name change.

Identifying the datastore where the VM resides is not a prerequisite for renaming the VM - renaming is an inventory metadata operation performed at the vCenter level, not a storage-layer operation.

Having all VM files on a single datastore is a consideration for storage operations such as cloning or migration, but it has no bearing on changing the display name of a VM in the inventory.

Fault Tolerant mode and Distributed Resource Scheduler membership impose restrictions on operations such as snapshots and manual migrations, but renaming a VM in the inventory does not require verifying or altering either of these settings.