Upgrade VMware Tools in ESXi

Similar Questions

• Upgrade VMware Tools post 5 upgrade

  I have updated vCenter to 5 and have my first ESXi host also running 5. Most of the time, it was a pretty easy upgrade. Now, I have two other guests are still running 4.1 and all our virtual machines are run on these hosts. By doc upgrade, then next step is to upgrade VMware tools for each virtual computer. Almost all of our machines virtual under Windows 2 k 8 and 2 k 3.

  The problem I have is in vSphere Client 5, when I try to upgrade the tools, it throws an error that the tools are already up to date. I don't know what is the current version, but I show version 8.3.2 build 257589 installed. If I try to vMotion one of these virtual machines to the ESXi 5 host, he erred in declaring the virtual material is incorrect.

  
  The specific error is "the version of VMware Tools is already up to date" installed in the virtual machine

  Any ideas?

  Thank you!

  Josh

  The error has nothing to do with VMware tools. It is more a problem with the types of CPU of the ESXi host and cluster settings. What type/model of CPU you have in your hosts and have you enabled EVC on the cluster?

  André

• upgrade vmware tools with orchestrator

  I still have many armies ESXi 3.5 although I updated my environment to ESX 4 3/4.  The task of rehabilitation for the vmware tools upgrade does not work for virtual machines running on esx 3.5.  Can orchestrator automate the task of upgrading vmware tools on a host ESX 3.5 and reboot the virtual machine.  Does anyone have an example to help out me with?  I know probably possible, but I have just install Orchestrator and did nothing with it yet.  I was thinking that this may be a task well start with.

  vCO server comes with a plug-in of VC4.0 with which you can configure some hosts/VC only 4.0 and later versions. In order to run workflows on ESX 3.5 hosts, you need to install the plug-in, VI3.5 there in vCO/extras/plugins server. The file has the extension VMOAPP, you can change to .jar then check out the plugin VI3.5 .dar file. After installing correctly, you can then drill library of built-in workflow, for the category of the VMware Tools, which you can find the upgrade tools workflow. It would automate the up-gradation of the tools, as long as the toolsAutoUpdateSupported is set to true in the virtual machine. In addition, this API works successfully if the tools are not updated. For ESX 3.5 hosts, you must run the workflow in the VMS VIM3 management category.

  Hope it will be useful.

• Upgrade Vmware Tools always fails

  I use VmWare WorksStation 10.0.6 build-2700073

  The host Windows 8.1 on a laptop Lenovo with 16 GB of Ram

  Guest is Windows 7 with 4 GB of Ram

  When I try to upgrade VmWare Tools

  

  I try to download and install and got this

  

  No idea how to continue?

  Hi, I got the file now and it works again

  Concerning

• Upgrade VMware Tools to 11.1 in Xubuntu invited 14.04 fails

  Hello

  Upgrade VMware Tools from 11.0 to 11.1 in Xubuntu 14.04 fails - see the error message below.

  My Xubuntu 14.04 is up-to-date. I've recently performed 'apt - get dist-upgrade'.

  I can continue with the installation, but then shared folders does not work.

  I don't know what the problem... Everything has worked fine up to 11.0 and I never had problems with VMware Tools upgrade. Help, please.

  Annex: Error Message

  Using the kernel build system.

  "do: Verzeichnis" / tmp/modconfig-snuOuv/vmhgfs-only 'enter wird. "

  / usr/bin/make /lib/modules/3.13.0-46-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Verzeichnis»/usr/src/linux-headers-3.13.0-46-generic«wird enter

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/backdoor.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/backdoorGcc64.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/cpName.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/bdhandler.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/cpNameLinux.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/cpNameLite.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/dentry.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/dir.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/file.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/filesystem.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/fsutil.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/hgfsBd.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/hgfsEscape.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/hgfsUtil.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/inode.o

  CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/link.o

  In file included from usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/percpu.h:44:0,

  of usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/preempt.h:5.

  of include/linux/preempt.h:18.

  of include/linux/spinlock.h:50.

  of include/linux/mmzone.h:7.

  of include/linux/gfp.h:4.

  of include/linux/mm.h:8.

  of include/linux/pagemap.h:7.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c: in function 'HgfsPermission ':

  include/Linux/kernel.h:793:27: error: 'struct dentry' has no member named 'd_alias '.

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.

  for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  include/Linux/kernel.h:793:48: warning: initialization of the [default] incompatible pointer type

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.

  for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from include/linux/compiler-gcc.h:106:0,

  of include/linux/compiler.h:54.

  of include/uapi/linux/stddef.h:1.

  of include/linux/stddef.h:4.

  of usr/src/linux-headers-3.13.0-46-generic/include/uapi/linux/posix_types.h:4.

  of include/uapi/linux/types.h:13.

  of include/linux/types.h:5.

  of tmp/modconfig-snuOuv/vmhgfs-only/./shared/driver-config.h:71.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:26:

  include/Linux/compiler-gcc4.h:14:34: error: 'struct dentry' has no member named 'd_alias '.

  #define __compiler_offsetof(a,b) __builtin_offsetof (a, b)

  ^

  include/linux/STDDEF.h:17:31: Note: the expansion of the macro '__compiler_offsetof '.

  #define offsetof (TYPE, MEMBER) __compiler_offsetof (TYPE, MEMBER)

  ^

  include/Linux/kernel.h:794:29: Note: the expansion of the macro "offsetof".

  (type *) ((char *) __mptr - offsetof (type, member)) ;})

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.

  for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from include/linux/preempt.h:10:0,

  of include/linux/spinlock.h:50.

  of include/linux/mmzone.h:7.

  of include/linux/gfp.h:4.

  of include/linux/mm.h:8.

  of include/linux/pagemap.h:7.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:

  include/linux/List.h:710:35: error: 'struct dentry' has no member named 'd_alias '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  include/linux/List.h:697:12: Note: in the definition of the macro 'hlist_entry_safe '.

  ({typeof (ptr) ___ptr = (ptr); \})

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  include/linux/List.h:710:35: error: 'struct dentry' has no member named 'd_alias '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  include/linux/List.h:697:28: Note: in the definition of the macro 'hlist_entry_safe '.

  ({typeof (ptr) ___ptr = (ptr); \})

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/percpu.h:44:0,

  of usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/preempt.h:5.

  of include/linux/preempt.h:18.

  of include/linux/spinlock.h:50.

  of include/linux/mmzone.h:7.

  of include/linux/gfp.h:4.

  of include/linux/mm.h:8.

  of include/linux/pagemap.h:7.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:

  include/Linux/kernel.h:793:27: error: 'struct dentry' has no member named 'd_alias '.

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  include/Linux/kernel.h:793:48: warning: initialization makes pointer from integer without a cast [default]

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from include/linux/compiler-gcc.h:106:0,

  of include/linux/compiler.h:54.

  of include/uapi/linux/stddef.h:1.

  of include/linux/stddef.h:4.

  of usr/src/linux-headers-3.13.0-46-generic/include/uapi/linux/posix_types.h:4.

  of include/uapi/linux/types.h:13.

  of include/linux/types.h:5.

  of tmp/modconfig-snuOuv/vmhgfs-only/./shared/driver-config.h:71.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:26:

  include/Linux/compiler-gcc4.h:14:34: error: 'struct dentry' has no member named 'd_alias '.

  #define __compiler_offsetof(a,b) __builtin_offsetof (a, b)

  ^

  include/linux/STDDEF.h:17:31: Note: the expansion of the macro '__compiler_offsetof '.

  #define offsetof (TYPE, MEMBER) __compiler_offsetof (TYPE, MEMBER)

  ^

  include/Linux/kernel.h:794:29: Note: the expansion of the macro "offsetof".

  (type *) ((char *) __mptr - offsetof (type, member)) ;})

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  make [2]: * [/ tmp/modconfig-snuOuv/vmhgfs-only/inode.o] Fehler 1

  make [2]: * Auf noch nicht processes wird going going...

  make [1]: * [_module_/tmp/modconfig snuOuv/vmhgfs-only] error 2

  make [1]: Verzeichnis»/usr/src/linux-headers-3.13.0-46-generic«verlassen wird

  make: * [vmhgfs.ko] Fehler 2

  "do: Verzeichnis" / tmp/modconfig-snuOuv/vmhgfs-only "verlassen wird."

  The filesystem (vmhgfs module) driver is used only for the shared folder

  feature. The rest of the software provided by VMware Tools is designed to work

  regardless of this function.

  If you want the shared folders feature, you can install the driver of

  running vmware-config - tools.pl again after making sure that gcc, binutils, make

  and your kernel sources are installed on your computer.

  These packages are available on the installation of your distribution CD.

  [Press the Enter key to continue]

  As Barney42 pointed out, this question comes with the new kernel 3.13.0 - 46. And indeed helped me to find a workaround:

  Tools can be patched manually. In vmhgfs.tar, inode.c d_alias should be replaced by d_u.d_alias put it back to the tar and then recompile tools.

  Here is a script that does this (tested on ubuntu 32 bit 14.04, vmware workstation on a windows host 11.1):

  #!/bin/sh -x
cd /usr/lib/vmware-tools/modules/source
tar xf vmhgfs.tar
grep -q d_u.d_alias vmhgfs-only/inode.c && echo "already patched" && exit 0
sed -i -e s/d_alias/d_u.d_alias/ vmhgfs-only/inode.c
cp -p vmhgfs.tar vmhgfs.tar.orig
tar cf vmhgfs.tar vmhgfs-only
vmware-config-tools.pl -d -m

  NOTE: This makes incompatible tools with older versions of the kernel, i.e. 3.13.0 - 45.

  (Original post at askubuntu)

  However, @VMware-team, please do run again out of the box, or submit a patch for the Linux kernel. You are a large business, should be no problem.

• Upgrade VMware Tools without rebooting

  Hello

  The tools on a Windows Server virtual machine VMware can be upgraded without having to restart the virtual machine after update?

  After version 5.5 is no longer, you will need to restart to install / upgrade VMware tools, however the 5.5 upgrade still requires a reboot

• Upgrade VMware Tools in the form of scheduled tasks

  Hi all

  I need to upgrade my VM to the latest version of VMware Tools (9.0.10 since 5.1.0 Update 2).

  As some of the virtual machine are used in a production environment, reset must be done during the night on weekends.

  I wanted to create a scheduled task for the automatic update of the VMware Tools, but unfortunately, this task is not available.

  I wonder if there is a way to create tasks scheduled using the Scheduler of vSphere.

  Thank you very much in advance for your help.

  Best regards, Werner

  Hi Werner,.

  PFB the process to install VMtool without restarting the machines.

  1. click on any virtual machine that needs the tools updated

  2. right click on the vm and hover over the comments and select Install/Upgrade VMware tools

  3. click on automatic tools upgrade and Advanced Options enter the command of follow-up

  "/S /v" /qn REBOOT = R.

  VMware KB: Install VMware Tools in a Windows virtual machine

  BR

  JD

• Certificate error, upgrade VMware Tools

  I get this error when you try to install or upgrade VMware Tools in VMware Player.

  

  Does anyone have a solution for this?

  I use a client of Windows 7 32 bit on a 64-bit Windows 7 host.

  You can work around the problem with the information in: Re: VMware Tools for Ubuntu 11.04 on Windows XP

• Snapshoting a virtual machine (Windows or Linux) before a upgrade VMware Tools as a precaution

  Our company has standardized on the use of VMware snapshoting than a level 1 to save uninstall mechanism possible to issues related to the updates / patches.  It works very well for Windows updates on our Windows guests, as well as the updates I YOU on our Linux guests.

  My question is if anyone thinks that there is a risk associated with the use of this process to guard against a possible problem that might occur after an upgrade VMware Tools.

  The process would be: Patch ESX host, migrate a guest to host newly patched, instant, prompt, install VMware Tools update, restart, test and certify, delete the snapshot.

  Since you're snapshoting a system that has an older version of VMware Tools, it's a bad idea to rely on this snapshot in a recovery scenario?  Use the VMware Tools as part of the process of snapshoting a guest?

  Thank you all for any advice you may have!

  Matt Heldstab

  Yes, you can snapshot before the upgrade tools and come back if something don't jive.  To take it even further, you can snapshot before the hardware upgrade of the v7 and return to v4 if it does not work.

  Seems like a lot of works well, but it does not offer a good backup method.

• upgrade VMware tools

  I answered the request of upgrading vmware tools on both servers in 5 days.

  main of the application server 1 does not start, missing is not dll. Seller working on it.

  backup server 2 application starts not due missing dll failed.

  Y at - it some problem discussed not related to upgrading vmware tools?

  We see it in our environment during the upgrade of 3.5 to 4.0.  The solution that we use is to copy the file msvcp71.dll c:\windows\system32 or c.\windows\syswow64 if it is a x 64 comments. After the upgrade of the tools and reboot, you can copy the file if it is deleted.  Search the forums for the name of the dll and you can find a few messages about this.

• How upgrade VMware tools Web Client 5.5

  Hi all

  I was wondering how upgrade you VMware tools on a virtual machine in the web client 5.5 without using tools to upgrade to the next option reboot inside the virtual machine.  When you go into the VM options is grayed out just

  

  Let me know,

  Thank you

  • The Web Client vSphere incorrectly invites you to update the VMware Tools, even in the last version.
  • A yellow banner will appear in the summary tab for the virtual machine with the message:

    VMware Tools is obsolete on this virtual machine.

  • The Web Client vSphere may or may not give you the option to update the VMware Tools.
  • When you try to update the virtual machine of VMware Tools reports the installed version is earlier than the version currently running.
  • In the view hosts and Clusters of the army of ESXi, related objects , the affected virtual machine tab shows the version of VMware Tools is common.
  • Tab summary of the view models and virtual computers for the affected virtual machine, VMware Tools version is listed as current.

  Cause

  When VMware Tools is installed in a virtual machine and the virtual machine is then migrated to a host older ESXi, vSphere Web Client correctly detects that the version of VMware Tools installed is equal to or greater than the version provided by the ESXi host where the virtual machine resides. However, the yellow banner is designed to match the version of VMware Tools exact provided by the host against the virtual machine.

  Resolution

  This question is only cosmetic.

  If the State of VMware Tools is listed as a current, you can ignore this message

• Upgrade vmware tools with Update manager

  Hello

  There seems to be some discussions about this.  I was not able to get a solid answer of «Yes, you can, and that's how...» "or"no, you can't "by following these discussions.

  So, can we use the Update Manager today to upgrade the tool invited?

  Thank you

  Daniel

  taken from the VMware vCenter Update Manager Administration Guide

  Manager update allows you to update the host ESX/ESXi, virtual appliances, VMware Tools and virtual hardware to virtual machines to a newer version, with the opportunity to decline the upgrade in case of failure. You can also configure preupgrade and postupgrade custom scripts to run before and after an upgrade. Upgrades for the host ESX and ESXi virtual machines and virtual appliances are managed through baselines and groups basic

• Create a workflow to upgrade VMWare tools

  We have an alert to tell clients VMWare tools is out of date, can someone create a workflow that would allow them to begin the upgrade.

  ActionPack for VMware vCenter does not provide the necessary steps to create this workflow from including 5.5.8 release with vFoglight 6.5.1.

  We CAN fix this in future versions. Stay tuned.

  PS: Sorry for the late reply

• Need for security upgrade VMware Tools?

  Hello, Im using a VMware environment that runs a good handful of Linux VM.  We're running 5.1 VMware update 3 on all hosts.

  Im not a Linux guy and im going to have to start learning more about Linux, but I've noticed to allocate to the virtual machine is here who have Linux, either do not have VMware tools installed, or are obsolete.  Its mix of Red Hat Enterprise 6, SUSE Linux 11, CentOS 4/5/6/7 and Ubuntu.

  My first concern is security, from a point of view security should I get these Linux VM up to date with the latest VMware tools, or else get installed on it?

  A feature point of view im says that the virtual machine is working well.

  Thank you

  Mike

  Hi Defrogger,

  I have a small number of Linux virtual machines in my environment and I have VMware tools installed, its always good to keep up to date.

  They also provide the required drivers for the VM Client interact with the reliable ESXi host. This interface allows also ESXi host be able to check on the health of the client VM during its operation.

  Here's a link below to help you install vmware tools on linux servers

  VMware Tools for Linux clients

  Rob

• Upgrade VMware Tools on Linux based virtual appliances

  I just updated a cluster of 5.1 to 5.5, some of the VMS are virtual appliances based on Linux (most of them on CentOS) which are fairly locked down (no easy access console) critical how's this for upgrade these types of virtual machines to the latest version of VMware Tools? I'm a little OCD and it bothers me that some of the VMS are VMware Tools reports that are "Stale" :-)

  Thank you.

  I know what you mean about the annoying notification bit... However, most of the providers WILL group and test vmtools as well as the Virtual Appliance that they release.

  The answer isn't vmtools upgrade, it has upgraded the Virtual Appliances.

  for example

  Installation of NetScaler virtual appliance on VMware ESX - Citrix eDocs

  You have a list of virtual appliances and you run versions?

  Chris