IFS=' n'
for i in `find /vmfs/volumes/ -name “*.vmx” `
do
echo “Registering VM $i”
vmware-cmd -s register $i
done

I used IFS in a script to suspend all VMs at night for backup (they also had spaces in their names), but it should also work here (although not tested).

IFS=' n'
for i in `find /vmfs/volumes/ -name “*.vmx” `
do
echo “Registering VM $i”
vmware-cmd -s register $i
done

I used IFS in a script to suspend all VMs at night for backup (they also had spaces in their names), but it should also work here (although not tested).

One of my colleagues updated the script to work with spaces in the VM and file names. See the updated command in the body of the post.

Hmmm. Have not tested with .vmx files that have spaces in names. I strongly suggest to anyone who listens to never use spaces in Linux file names for reasons just like this. In ESX, change the VM name in the properties after it's already created, but be sure not to you spaces while building a new VM. I try to use the FQDN as my standard. If I have to account for a space I use the underscore (“_”). Having to work with spaces in file names at the console is always a problem or extra aggravation.