Upgrade VMware Tools post 5 upgrade

Similar Questions

• 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.

• Question about VMware Tools when upgrading of vSphere 5.1 to 5.5

  We are the vSphere upgrade 5.1 to 5.5. We have still a few virtual machines with obsolete tools VMware vSphere 4.  There problems upgrade to vSphere 5.5 and then upgrade VMware Tools on those virtual machines to the version 5.5?  Or should we upgrade VMware Tools version 5.1 first before doing the upgrade to vSphere 5.5? We need plan restarting downtime when upgrading to VMware Tools on those virtual machines and would rather not upgrade VMware Tools twice and planning two stops

  There is no problem, as vSphere ESXi 5.5 supports the VM running older versions of VMware Tools.

  This blog post explain this more in detail: is a vSphere VMware Tools upgrade required during the upgrade? VMware vSphere Blog - VMware Blogs

• Is it possible to automate upgrades of VMware Tools with Foglight Standard Edition?

  Its probably a stupid question but don't Foglight Standard Edition (6.5) have an automated function upgrade VMware Tools?

  Thank you!

  HI - not sorry that it's not, you will have to do it in vCenter. (there is no such thing a stupid question on these forums!)

• 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

• VMware Tools upgrade fails with the error

  12 Pro - 12.1.0 workstation build-3272444

  Individual license

  Guest operating system: Ubuntu 14.10 64-bit

  VMware Tools: 9.6.2.31837 (build 1688356)

  Virtual MACHINE works fine except...

  Updated the VMware Tools, download stage publishes a message and is abandoned:
  Error: There was a problem updating a software component.   Try again later and if the problem persists, contact your system administrator or the VMware support.

  I can't find useful this question online resolution.  Perhaps this community can help find a solution?

  Furthermore, I also have a VM for 64-bit Ubuntu 15.10 who works with success the VMware Tools 10.0.1.357 (build 3160059).

  I need to run both versions of Ubuntu for software compatibility.

  Maybe you can try to get the packages of the latest VMTools from their repo upgrade server: filing of CDS - /var/www/public/stage/session-59/cds/vmw-desktop/ws/12.1.0/3272444/windows/packages

• Impossible to get files shared, open-vm-tools or vmware tools to work after upgrading Fusion 8

  I just upgraded to Fusion 8 and have been upgrading my VMs accordingly.  I went to install vmware tools as usual on Ubuntu 14.04, and the script or the pop-up said that the preferred method for this OS has been to use instead the open-vm-tools. I installed open-vm-tools, but my shared folders disappeared. I tried to install vmware-tools, since I found an old ad saying that would solve the problem, but he wants to only replace open-vm-tools.  I thought I would try anyway, but the installation fails with errors.  I completely uninstalled vmware tools and restarted open-vm-tools.  It doesn't seem to be a manual for the use of open-vm-tools.

  If open-vm-tools is the preferred method to use ubuntu on vmware, how to bring back all the features (shared folders, etc.)  Why did every upgrade VMware accompanied by pain and hard to find answers?  Or maybe I'm being really stupid.

  (this was originally released by chance in the wrong place.  It is now being published in the Fusion forum)

  OK, I FINALLY got working open-vm-tools on Ubuntu.  I'm not sure that all that was necessary, but here's what I did:

  1. Completely uninstalled vmware tools using the uninstall program
  2. Open-vm-tools, open-vm-tools-desktop and open-vm-tools-dkms is installed. I am not sure I needed everything, but at least man pages were here who has helped.
  3. At one time I used vmware-user-suid-wrapper, which defined the Office on the appropriate resolution, but is not persisted until I upgraded to Ubuntu.
  4. Updated Ubuntu Studio ot 15.04 Vervet vives.
  5. VMware-hgfsclient will show you what is actually shared by the virtual machine, even if it is not mounted.
  6. To constantly rising stocks, I added the following to the / etc/fstab: "".host: / / mnt/hgfs vmhgfs defaults 0 0 ""
  7. Rebooted and everything works now.

  Given that VMware now recommends that users use open-vm-tools instead of the deprecated vmware-tools, it would have been nice to have brief instructions on how to make the transition, rather than have me spend hours in trial and error until I have to work.

• 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

• 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 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 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

• 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

• VMware Tools upgrade changes machineID, breaks the issuance of licenses for some applications

  We have this application called localization, manufactured by Hyland Software. Whenever I've upgrade VMware Tools on our ESXi hosts on all virtual machines, it breaks the granting of licenses for the application and localization will not work until the licensing is completely redone. No idea why this is happening?

  Below is the reading of the application regarding the issuance of licenses, and attached is a screenshot of the error in the application. I'm certainly not asking someone to solve the problem of the application, but what on earth could possibly VMTools change that would have caused this? Thanks in advance!

  RegisterName	dateregistered	Networkid	pcserialnum	usernum	stationdesc	wkstationgrpnum	cachenum	MacAddress	lastLogon	badlogincount	MachineId
  DALONBASE	01/02/2013	BVVGRCRGRKRO	715828130	0	DALONBASE (SELF)	0	0	005056b33b87	04/02/2013	0

  C8C2A6CCADFA02BFBAA68E68D9842B25

  DALONBASE

  04/08/2012

  YIEGRCRGRKRO

  715827788

  0

  DALONBASE (SELF)

  0

  0

  005056b33b87

  01/02/2013

  0

  006EEA89FBC395E1DAD4C3BA17DF7DF2

  If this is what is causing the problem?

  I'm sure of it - about 99.9% Yes.

  And if so, what changes would affect a particular software feature licenses?

  "All the virtual machines have a hardware version, which shows the characteristics of virtual hardware that supports the virtual machine, such as BIOS or EFI, number of virtual slots, maximum number of processors, the maximum memory configuration and other features material." - from http://www.vmware.com/products/datacenter-virtualization/vsphere/compute.html

  They probably linked the license to an individual (or several) attribute of the "hardware" of the virtual machine. Think of it regarding a physical system - changed nothing in the operating system (at least not GUID, MSN, etc.), it was something that the operating system has access to related material. You could probably bug them enough and get them to reveal madness method they use for this, but I don't know if it would be really useful. You can leave virtual to older material , to some extent, which means that you can reduce the number of times you have to repeat this process.

• VMware tools will not install on Windows 2000 comments: "Setup failed to upgrade windows install.

  Just installed VMware player 5.0.0 on a host windows 7 to run a guest OS for win2k.  Going to install VMware tools, the installation program starts as expected but gives the error dialog box, ' the installer could not upgrade windows install "and closes.  How can I install VMware tools?

  See attached screenshot.

  Thanks in advance.

  Service Pack installed inside the 2 k VM?

  AFAIK the installer needs to SP 4

• Upgrade VMware Tools in ESXi

  Hello

  I can't find how to upgrade vmware ESXi 4.0 to latest tools, or is it automatically upgrade itself to the latest version? I mean not for the guest OS but for ESXi. So when I install VMware Tools on a new guest OS I get the latest VMware tools.

  Thank you

  / Martin

  Hello

  You need to update your ESXi host, usually new updated comes with its own updated VMware tools. Use the Manager to update to patch/update your ESXi hosts. Once the host is update/upgrade VMware tools in the virtual machines will also have the opportunity to upgrade to the latest version.

  Hope this information is helpful

  Nikhil