VMware Tools obsolete. update problems

Similar Questions

• Let guestOS auto repair/re-install VmWare Tools after update?

  As I learned that VmWare Tools installation in guestOS (Ubuntu or Solaris, for example) can be destroyed when the guestOS is updated

  (for example a new kernel resp. drivers change).

  Is it possible to leave the guestOS AUTOMATICALLY installs/re-repair VmWare Tools in such a situation?

  I don't want to worry about Vmware tools more after the first installation.

  Matt

  Hello

  Take a look at this http://www.tuxyturvy.com/blog/index.php?/archives/48-Automating-VMware-modules-reinstall-after-Linux-kernel-upgrades.html

• 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

• VMWare Tools shared folder code does not compile on VMWare Fusion 7, Ubuntu asked 14.10, and Clipboard sharing does not work.

  Hello

  After the upgrade to a guest of 14.04 to 14.10 Ubuntu, I tried to reinstall the VMWare tools.  The problems I've come across so far:

  Shared folder code will not compile.  I get the following result:

  do: enter the directory "/ tmp/modconfig-ElOCTG/vmhgfs-only.

  Using the kernel build system.

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

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.16.0-23-generic'

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/message.o

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

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/request.o

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

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

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/rpcout.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/stubs.o

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

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

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/transport.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/module.o

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

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/super.o

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c: in function 'HgfsAioRead ':

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c:714:4: error: implicit declaration of function 'generic_file_aio_read' [-Werror-implicit-function-declaration =]

  result = generic_file_aio_read (iocb, iov, numSegs, offset);

  ^

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c: in function 'HgfsAioWrite ':

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c:786:4: error: implicit declaration of function 'generic_file_aio_write' [-Werror-implicit-function-declaration =]

  result = generic_file_aio_write (iocb, iov, numSegs, offset);

  ^

  Cc1: some warnings are treated as errors

  scripts / Makefile.build:257: recipe for target ' / tmp/modconfig-ElOCTG/vmhgfs-only/file.o' failed

  make [2]: * [/ tmp/modconfig-ElOCTG/vmhgfs-only/file.o] error 1

  make [2]: * waiting unfinished...

  Makefile:1345: recipe for target ' _module_/tmp/modconfig ElOCTG/vmhgfs-only' failed

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

  make [1]: leaving directory ' / usr/src/linux-headers-3.16.0-23-generic'

  Makefile:120: doesn't have a recipe for target 'vmhgfs.ko '.

  make: * [vmhgfs.ko] error 2

  make: leaving directory ' / tmp/modconfig-ElOCTG/vmhgfs-only.

  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]

  In addition, the shared clipboard does not work.

  I'm under VMWare 7.0.0 on OS X 10.10.

  Any help or advice will be greatly appreciated.

  
  Thank you

  Jonathan Morgan

  The VMWare Tools included with fusion 7.0.1 solved this problem for me (and without any serious regressions I noticed so far, at least, which is nice but not something I intend on with vmware), so probably the next update of each VMware product should include the updated tools.  Don't know how long updates to other products are coming, however.  Wonder if there is a separate place to get just the tools to day?

• VMware tools date

  Hello

  I 624 VM in my largest cluster virtual machine part is showing "vmware tools obsolete.

  is it possible to get how meany are update how meany are date can generate the report

  If I want to update the VMware tools what is the best practice to do... .on one can take a lot of time

  There are several ways you can find vmware date tools.

  (1) Using vSphere Client, select Data Center/cluster and select VM Filter tab with the status of the VM name and Vmware tools

  (2) using the RVtools (RVTools - homepage)

  (3) using the Power of CLI (Get - VM |) Select name, Version, ToolsVersion, ToolsVersionStatus)

  You can PowerCLI update without restart vmware tools

  Get - VM | Update-tools - NoReboot

  Check this if you want to use inside VM CSV file https://communities.vmware.com/blogs/amitrajit/2013/10/22/update-vmware-tools-without-reboot

• Upgrade VMware tools and hardware on vSphere

  Hello

  After a few questions, I seem to be a host to complete my move to vSphere, and I'm looking at the next steps - VMWare tools and update virtual machine hardware.

  Now, it seems reasonable to me to upgrade to VMWare tools, but the material I'm undecided.

  As I see it, VMware tools requires a reboot, I won't be able to do in working time, but that's just a reboot (sure of 60 odd servers, but still it is probably worth the time spent), but the material of vmware seems not critical for me? VMS seem to be running ok (Mix of Linux, Windows 2003 and Windows 2008) and I wonder if I'll get all the benefits of the upgrade of these? Is there something that puts me in danger if I let the computer virtual hardware version 4?

  It is mainly a question I have organize downtime, and the upgrade seems not smooth at all (completely detach existing NIC? Loss of MAC address I linked to the servers of licenses etc.) so if there is no benefit at this point, I'll be ok to keep the version 4?

  All advice appreciated, if I missed anything big I'd appreciate knowing what!

  Thank you!

  Hello.

  You will miss out on some of the new features Virtual material, but if you're not having performance issues it is in somewhat of a moot point.  The biggest potential problem is leaving all these VMs v4 and runs the risk of another (or one that follows) version of vSphere perhaps not material no longer v4 support.  Hardware upgrades are inevitable, so it's really just a matter of do it now or do it later.  If you are comfortable delaying the inevitable, so there is no reason to upgrade to v7 now.

  Good luck!

• FreeBSD on ESX4 VMware tools

  Is that what someone has successfully installed vmware tools on a FreeBSD virtual machine under ESX 4?  I have a vSphere 4.0 test environment I am doing an upgrade from 3.5 to 4.0 on before this on my production servers and have problems vmware-tools on FreeBSD 7.1 and 7.2 to be considered good working condition by vCenter.

  Specifically, I installed the tools of the file vmware-freebsd - tool.tar on VMware-tools-freebsd-116369 iso, which is the package tools currently referenced, on FreeBSD 7.1 and 7.2 facilities.  It's the same setup file that I used successfully on several FreeBSD installs under 3.5.

  The Installer seems to install fine, and the demon starts normally.  But for these virtual machines, I have improved on 3.5 to 4.0 hosts, vCenter (4.0) reports "VMware Tools: not installed".

  I also tried new construction FreeBSD 7.1 and 7.2 virtual machines on the 4.0 hosts upgraded, and this, after installing the vmware tools, report "VMware Tools: obsolete.

  Any thoughts would be appreciated.

  I just spent a week working with VMware support on this same exact question, and we found a resolution that works.

  Their official response, it's because of FreeBSD do not supported on older versions of ESX 4.0. The new freebsd.iso included with vSphere awaits a guest with version 7 of material. Because the machines were created before the upgrade to vSphere, the hardware version is 4. VMS also appear with a guest operating system type of "Other Linux", because FreeBSD is not possible before.

  Their solution is to uninstall the existing tools of the VM and stop the FreeBSD Guest. Then right click on the computer and upgrade virtual hardware. Then you will be able to change the type of operating system asked the new option other > FreeBSD. Start the machine and mount the iso freebsd and install the tools. It should show OK now. I know that sounds a bit risky to force the upgrade of equipment without the tools are installed, but I did it on 4 machines so far and they run a lot.

  Hope this helps you.

  -Josh

• CentOS (redhat) e I have vmware tools che non partono automatically

  Ciao a tutti, mi sono che great people knew all the vm centos che ho i tools not partono automatically launch.

  Ho trovato a post molto esplicativo su cosa nelle versioni dei tools official comments happens: in brief gli script di d non sono più in /etc/init.d perched usano 'Upstart' quindi if exposed in the file/etc/init e sono sotto forma di. conf.

  differenze sono che non li con più there great it 'service' born appaiono in chkconfig, e I comandi per gestirli sono

  NEW Command to check tools: status vmware-tools  

  NEW Command to start/stop: start/stop vmware-tools

  He problema e che... is no questi there, e probabilmente per questo non partono Reed automatically, come to this grave error syntax nel vmware - tools.conf che sotto riporto di UN

  (lanciando a beginning of mano /etc/vmware-tools/services.sh i tools partono correctly.)

  Ho googlato a po' e ho visto che esiste knew Ubuntu un comando by links the syntax (init-checkconf) che pero e non nella versione distribuita con CentOS 6.x Upstart di present

  Qualcuno ha sperimentato/solved the cosa?

  
  
  
  ##########################################################################
  # Copyright 2010 VMware, Inc..  All rights reserved. -VMware confidential
  ##########################################################################

  ##########################################################################
  # DO NOT edit this file directly, because it will be overwritten the next
  # duration that VMware tools are installed.
  ##########################################################################

  Description 'services VMware Tools'
  author "VMware, Inc.."

  # Remember to block handlers display until our work is done.  This
  # is to ensure that our core services are running before vmware-user
  # launch.
  start the runlevel [235] or start gdm or kdm to start or prefdm
  stop the runlevel [06]

  before start of /etc/vmware-tools/services.sh exec
  stop after stop of /etc/vmware-tools/services.sh exec

  Hai, tried one revive lo script di riconfigurazione? Hai da da RPM?

  Lo script e vmware-config - tools.pl (da does come from root)

• VMware Tools error, can not download and install the tools: "internal error of the client CD (3033). Contact your system or VMware Support Administrator"

  Hello

  I installed Windows Pro 8.1 x 64 RTM with Rollup GA A on PC, after that I installed VMware Player 6.0.1 and when I tried to download and install VMware Tools, I got the following error message: "internal error of the client CD (3033).» Contact your administrator system or VMware Support. »

  How can I install these tools? Please, fix the problem with the Server CD, I need to install VMware Tools.

  I tried to download on the deposit of CDS - / www/internship/session-32/cds/vmw-desktop/player but there is no record for the VMware Player 6.0.1 version, while the Tools-windows - 9.6.0.exe.tar is a strange form, how can I install these tools in VMware Player?

  Thank you.

  Workaround solution:

  1. download the trial of VMware Workstation 10

  2. install

  3. navigate to the Program files VMware Workstation 10

  4. find windows.iso, copy to USB or transfer it to some hosting

  5. go the machine to hosts, copy on it windows.iso

  6. inside of the guest computer mount windows.iso as drive

  7 install tools

  8 restart the guest computer

  That's all

  P.S. I am very disappointed, that such large and respected company, like VMware, after almost a month, since the question has been raised cannot pay 10 minutes and fixes a bug with CD-server and allow their users to download & install VMware Tools without any problems, even if we are talking about free product such as VMware Player!

• VMWare Tools for Windows 7 RC

  Hello from Germany!

  Im running VMWare Server 2.01 32 bit as the host computer.

  Now, I want to add Windows 7 RC 32-bit as guest system. I have create a new virtual machine using W2K8 32-bit Server to install Windows 7 RC.

  Is it possible to use VMWare Server 2.01 for this new Windows tools?

  THX and best regards

  Peter Muss

  Hello

  I installed W7 using Vista recommended settings. I installed VMWare Tools without any problem.

  J.

  If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

• "There was a component of software update problem" tool VMware

  Hello

  I have OS X Lion Update 10.7.3 and VMware Fusion 4.1.1

  I try to install the VMware Tool software, but get a message error "there was a component of software update problem"
  I've done a few virtual drives DVD and it did not help
  What Miss me?
  Thanks for any help

  Mac Book Pro

  Intel Core 2 Duo 2.4

  DDR3 4 GB

  NVIDIA geforce 9400 m 256 MB

  Mac OS X Lion 10.7.3 (11D50b)

  If you have downloaded and installed the Lite version of VMware Fusion then I download the installer complete and uninstall/reinstall VMware Fusion and then you will have complete and up-to-date VMware tools.  Note: Uninstalling/reinstalling VMware Fusion does not remove Virtual Machines.

• VMWare tools update problem

  Hi all

  I use VMWare Fusion 2.0.2 and try to upgrade the VMWARE tools. But suddenly installation stops and I get the error message that I have attached here.

  Now, I would like to know how I can solve this problem and get properly installed tool.

  Thanks for your help!

  Bjoern

  Try to uninstall VMware Tools through first control panel and uninstall the virtual machine is rebooted, then install VMware Tools in the Virtual Machine menu.

  (Start > Systemsteuerung > program hinzufügen oder entfernen)

• Update the vmWare tools in VoP via vCenter

  I'm still new to this community and I hope I'll catch up here soon, but I'm not sure of the update process the vmtools on the device of VoP. I know once I spunt'sand he upwards and configured the IP etc, the vCenter as the tools were obsolete. Tonight is our night of patch management and we'd get VoP abreast, as far as tools go. What is the process to get this done? Do I just shoot vCenter or are there steps to perform on the server of VoP so.

  Thank you in advance for your help!

  Hi David,

  You can update VMWare Tools on the device in the same way as you would for any virtual machine of OpenSUSE Linux.  This can be done manually from the console if vCenter may not withdraw that, alone.

  I hope this helps!

• Problem downloading VMware Tools

  I am running VMware Workstation Pro 12 (12.1.1 build-3770994) on Windows 7. Whenever I start VMware Workstation and then to start a virtual machine, software updates window opens:

  "The following software are available for download: VMware Tools for WIndows 2000 or later version - version 10.0.6.

  If I click on the button to download and install it, it goes through the download and verification phases, but fails during the update phase, including a generic 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. »

  The details of error only I can find is in the log of the user interface:

  2016-05-09 T 16: 24:20.689 - 05:00 | vmui | I125: Error VMUICOM: hr = 0 x 80004005, (null)

  2016-05-09 T 16: 24:20.689 - 05:00 | vmui | W115: wui::ExecuteToolsISOInstall: cannot install VMware -.

  tools-windows - 10.0.6 - 3595377.iso: COM routine failed

  2016-05-09 T 16: 24:20.689 - 05:00 | vmui | I125: CD: CdsInstallProgress: installation of bulletin a3196322 -.

  fce0-49ee-abbf-18d43e91e39d

  2016-05-09 T 16: 24:20.689 - 05:00 | vmui | I125: CD: CdsInstallProgress: install for newsletter a3196322.

  fce0-49ee-abbf-18d43e91e39d returned installerStatus 3, exitCode 0

  2016-05-09 T 16: 24:20.747 - 05:00 | vmui | I125: DlgUI: 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 any explanation of VMUICOM error 0 x 80004005.

  Note that this error occurred before before the 12.1.1 update and is still ongoing.

  I think that building tools that currently is 10.0.1.357.

  No idea how to solve this problem?

  It turns out that the problem was caused by McAfee Host Intrusion Prevention 8 running on the host computer. It is the firewall component, not the component virus protection.

  Part of intrusion detection is 'VMware Workstation shielding - file Modification. Probably there's some bad signatures, because he sees any attempt to change the files .iso in VMware Tools as an attack.  This includes:

  • Installation of VMware Launcher, as when VMware is modernized
  • Windows Installer that are managed by the system, for example when VMware tries to download and install new tools
  • User who attempts to remove or rename files

  So the tools .iso files are frozen in time: they cannot be changed even by a complete uninstall and reinstallation of VMware Workstation, and still less a version upgrade.

  The surprising thing is that a change to a file is blocked by the HIP, which is well beyond what you expect normally to a firewall.  That's why it took me so long to realize it was the root cause.

  Work is about to open the HIP interface, and then temporarily disable Host IPS in the IPS policy. While the IPS is disabled you can go forward with VMware Workstation or tools to level, then turn on IPS.

  The permanent solution would be to get McAfee to fix the signature HIP. There are release notes that say that this is not the first time the functionality of VMware Workstation armor has had false positives.

• Update only the vmware tools?

  Hi all

  
  Recently we received BSOD on server 2012. Microsoft is continuing its investigation, but it seems likely vmxnet3 drivers are involved. Therefore, we would like to update.

  However, given that we are now very busy on a project, we would like to avoid completely updated vcenter and ESX (if possible). So my question is, can we day purely VMXNET3 driver to the latest version on our virtual machine? Or maybe only the VMWare tools? Or is there a possibility for stability/performance issues if you do not keep everything on the same version?

  
  Thanks in advance!

  So my question is, can we day purely VMXNET3 driver to the latest version on our virtual machine? Or maybe only the VMWare tools? Or is there a possibility for stability/performance issues if you do not keep everything on the same version?

  This isn't a problem, running new versions of VMware Tools on the former ESXi hosts is supported only by the product VMware interoperability matrices: