Scheduled Update Vmware-Tools

[PascalW2008]

Hello,

I want to update vmware-tools on specific esx-host with a scheduled cron job.

I used this cmd:

vimsh -n -e vmsvc/tools.upgrade 32

But I get this error:

# vimsh -e vmsvc/tools.upgrade 32 -n

File not found.

Current working directory: /usr/lib/vmware/hostd

HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1.

HOSTINFO: hyperthreading disabled, setting number of threads per core to 1.

HOSTINFO: This machine has 2 physical CPUS, 8 total cores, and 8 logical CPUs.

System libcrypto.so.0.9.7 library is older than our library (90701F < 90709F)

Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

Unsetting unknown path: /vmomi/

Insufficient arguments.

Usage: tools.upgrade vmid

Upgrade VMware Tools in the virtual machine

It looks like the cmd needs more arguments, but I cant find anywhere the Arguments which I should or can use for this cmd.

[alanrenouf]

Not sure about this method but the following VI Toolkit commands could be scheduled via task manager:

http://halr9000.com/article/605

If you found this information useful, please consider awarding points for Correct or Helpful.

Alan Renouf

VMware, Citrix, Microsoft Consultant

UK

[AlexNG_]

Hi pascalW2008

with vimsh execute the following command:

vimsh -n -e vmsvc/getallvms

The first column gives you the vmid, the missing argument!

AlexNG

[PascalW2008]

Hello AlexNG_

i know the ID of the VM i want to upgrade. My cmd I used was

vimsh -n -e vmsvc/tools.upgrade 32 <<< ID of the VM

but strangely the cmd needs more argmuments and I dont know what args. You can see this in the error message:

Insufficient arguments.

Usage: tools.upgrade vmid <<<< -

---

[AlexNG_ · Accepted solution]

doooooh!!! too quick reading!! You're right!!!!!!! :smileygrin:

I've tried right now the option. Inside vimsh, no problem, it runs ok, and gives what is supposed to output.

The i've executed the command from the shell i non interactive mode, and gives the same error!!

I'll give it a look, because it's not the first parameter that I cannot modify from vimsh...

AlexNG

[PascalW2008]

Yes I tried it in vimsh and it works good, obviously ist a bug in the non interactive mode.

Thanks for the answers.