Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3068
  • Last Modified:

vmware esxi, vmrc character limit for target in shortcut?

Is there a 64 character limit in the -m parameter of the vmrc command line?

I have one guest with 65 characters in the -m "[datastore1] folder/vm_name.vmx" parameter, and I can't connect to it using vmrc.  Other guests with less than 64 characters work fine.

(I don't know how to find the MOID to try the -M option and verify that I can connect that way).

I'm getting errors trying to connect to a guest using VMRC from 2 different machines.  One a Win7 workstation, the error is:

Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe: The system cannot find the file specified.

From another workstation, I get an error about username/password.
0
snowdog_2112
Asked:
snowdog_2112
  • 4
  • 2
1 Solution
 
bgoeringCommented:
Looking at your test case it would appear that you are hitting a character limit, but have not been able to find any documentation to support that.

From this post on VMware server 2 (http://communities.vmware.com/message/999988) to find the MOID

" you can specify the VM by either datastore path, or managed object ID (a.k.a. "Moe ID"). You can determine the moid for a VM by looking at vmInventory.xml in /etc/vmware/hostd/ or %ALLUSERSPROFILE%\Application Data\VMware\VMware Server\hostd as appropriate."

The vmInventory.xml file also works for ESX/ESXi to find the MOID.

If you are on the VMware Server 2.x platform you could also obtain an newer version of vmware-vmrc by installing either (1) the vSphere 4.1 client, or (2) the VMware Guest Console (VGC) Fling from http://labs.vmware.com/flings/vgc. I don't know if that alleviates the 64 character limit but it might be worth a try.

Good Luck
0
 
bgoeringCommented:
Also note that if using the path (rather than the MOID) don't actually include the -m parameter. It should be:

vmware-vmrc -h hostname:port -u <username> -p <password> "[datastore1] folder/vm_name.vmx"

From what I have been able to determine including the -m can cause your login errors.
0
 
snowdog_2112Author Commented:
I think you can use -m (lowercase) for the path, and -M (uppercase)when specifying the MOID (i.e., case sensitive).

The same command works for the other Server 2003 guests on this esxi host, which leads me back to the character limit - the non-working guest is the only one near/past 64 characters.

I'll try the moid - if I can find that - and report back.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
snowdog_2112Author Commented:
AHA!  That seems to be the case:

-m "[datastore1] path/filename.vmx"  format must be less than 64 characters, and must have a space after the [datastore] name.

-M 64 where the "64" is the moid found in the  /etc/vmware/hostd/vmInventory.xml file works.

Maybe this can be considered documentation to verify this for someone else!
0
 
snowdog_2112Author Commented:
-m "[datastore] path/filename.vmx
must be less than 64 characters including the "[ ]"'s and all spaces.

-M [n]
where [n] is the moid - do not include the "[" and "]" in the command line.

Thanks!
0
 
snowdog_2112Author Commented:
bgoering -

You are correct about the -m (lowercase) when connecting to an ESX/ESXi host.  The -m can be used when connecting to a VMware Server 2.x host.

In fact, if you include -m when connecting to an ESX host, the vmrc window does not even pop open.  That was a head-scratcher for me for a while.

oh..and in my previous post, I see I forgot the closing " on the first line.  It should be:

-m "[datastore] path/filename.vmx"
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now