Status in ESX5i and VCenter VMware tools is false

Similar Questions

• vCenter Server Appliance and VMware Tools update

  I've just updated VCSA to 5.1.0.10000 build 1065184. I had to uninstall VMware Tools first because the update failed with

  "VMware Tools can not install because it seems that another installation of.

  VMware Tools is already present. Please remove the previous installation and

  then try again to install this version of VMware Tools. »

  error in /opt/vmware/var/log/vami/updatecli.log (I had a similar problem with the previous update).

  After updating, I see in this newspaper:

  "22/05/2013 14:43:48 [INFO] Running/opt/vmware/share/vami/vami_reconfigure_tools.

  VMware tools is not installed on this virtual machine.

  "22/05/2013 14:43:48 [INFO] status update: reconfiguration of done VMware tools.

  Should I install VMware Tools via vSphere Web Client again? I assumed VMware Tools to install update VCSA. I can see the packets in any case:

  VM-vcenter: ~ # rpm - qa | grep-i vmware-tools

  VMware-Tools-vmmemctl-KMP-default-1.2.1.2_3.0.13_0.27-3

  VMware-Tools-vmxnet-KMP-default-2.0.14.0_3.0.13_0.27-3

  VMware-tools-services - 9.0.5 - 1.sles11

  vmware-tools-plugins-hgfsServer-9.0.5-1.sles11

  VMware-Tools-plugins-VMBackup-9.0.5-1.SLES11

  VMware-Tools-VMCI-Common-9.0.5-1.SLES11

  VMware-Tools-vsock-KMP-default-9.3.3.0_3.0.13_0.27-3

  VMware-Tools-Libraries-NOx-9.0.5-1.SLES11

  VMware-Tools-vmmemctl-Common-9.0.1-3

  VMware-tools-core - 9.0.5 - 1.sles11

  vmware-tools-plugins-autoUpgrade-9.0.5-1.sles11

  vmware-tools-plugins-guestInfo-9.0.5-1.sles11

  vmware-tools-plugins-powerOps-9.0.5-1.sles11

  VMware-Tools-plugins-VIX-9.0.5-1.SLES11

  VMware-Tools-ESX-kmods-default-9.0.5-1.SLES11

  VMware-Tools-vmxnet-Common-9.0.5-1.SLES11

  VMware-Tools-VMCI-KMP-default-9.3.18.0_3.0.13_0.27-3

  VMware-tools-guestlib - 9.0.5 - 1.sles11

  vmware-tools-plugins-deployPkg-9.0.5-1.sles11

  vmware-tools-plugins-timeSync-9.0.5-1.sles11

  VMware-Tools-ESX-NOx-9.0.5-1.SLES11

  VMware-Tools-vsock-Common-9.0.5-1.SLES11

  VMware-tools-Foundation - 9.0.5 - 1.sles11

  But I can not start the daemon:

  VM-vcenter: ~ # /etc/init.d/vmware-tools-services start

  From an operating system daemon invited VMware Tools: failure

  After the assumption, I deleted/usr/lib/vmware-tools/lib / and was able to run vmware - install.pl and install VMware Tools 9.0.1.18551 (build 913578) then.

  I'm still confused why vmware-tools-services - 9.0.5 - 1.sles11 and other packages installed during the VCSA update did not work.

• How to launch and use the VMware tools

  After installing 2008r2 as a virtual machine and install VMware Tools, I am unable to open the tools and use them.  I did two days of searching, and I can't find an answer to my problem.    Downstairs is an action I took, but I would appreciate any help from the community.

  Purpose:

  Laboratory at home training and certification.

  Hardware environment: (based on "Chris Wahl" home Build Lab)

  SuperMicro Motherboard MBD-X10SLH-F-O

  Intel Xeon E3-1230 v3 3.30 GHz processor with 32 GB of ram

  Software environment:

  64-bit version of Windows 7 Professional, host operating system

  VMware Workstation 10 with all updates installed with administrator privileges

  VM #2: vSphere 5.1 install

  VM #1: The Windows 2008R2 VM I have a problem with VMware tools.

  I've deleted and rebuilt the two VM three times now, thinking it was my environment somehow.  ESXi 5.1 works although I have not built anything there yet.  I am able to access this part of the laboratory fine of vSphere Client.

  VMware Tools:

  Within the Services of VM 2008 I can see VMware Tools started service, the icon in the system tray notification area and see the files on the C: drive of the virtual computer, but there is no way to open it.

  I followed several links to create a virtual laboratory, but should not be this hard to run a program.  It's my first time that you try to use VMware tools, but I'm following the steps in the lab below install procedures.

  In the middle of the page of "Blog Editor" part 4 "build the ultimate vSphere Lab is where it installs the VMware tool and lowest after restarting Windows Update service I'm stuck to the next step."

  "Open VMware Tools, go to the Shrink ."  Click on the button of the prepare to shrink . »

  ?  How to "open the VMware Tools?

  Now on the path I have searched for and deleted and reinstalled the tools, but always without success.

  Here is a link where I found the following measures to be taken, but it doesn't work either.  The "NOTE" at the bottom, it's something I noticed and made sure was right when I installed the last time tools.

  I even found a link to where you can download the tools separately from the ISO files, and yet, it does not work.  A LITTLE HELP PLEASE!

  http://www.vdsyn.com/Windows-2008-R2-virtual-machine-VMware-tools-shows-not-running-current-after-vmotionsnapshot-operations-randomly/

  So next step that we did was
  1 uninstalled VMware Tools in the virtual machine
  2 restarted the VM
  3. manually deleted/renamed the C:\Program VMware Tools
  4. manually deleted/renamed C:\Programdata\VMware\VMware tools
  5 Rebooted
  6. install the VMware tools
  7 Rebooted

  The issue is not reproducible after the same

  
  NOTE: Make sure that the virtual computer CD player points to the correct image.  I found it always go back to the windows 7 iso image on my C: drive from physical machines to where the image 2008r2 was on drive E:

  No need to reinstall again. You're not missing something. VMware has changed the VMware Tools tray and removed options that were available in previous versions. Take a look at for example experience front of VMware: The VMware Tools GUI is gone - now what? with some information about this change and the replacement of the command line.

  André

• 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 and the vMA

  Hello

  I noticed that VMware tools shows as obsolete for vMA 4.0. I ran the command ' sudo vima-implementation to date update "to update the vMA.

  The reason is that I need to install a script for our UPS on the vMA to stop customers automatic and host when AC power is lost and before that sinks in the battery, this script needs VMware tools running and I guess he wants to the most recent version.

  Anyone know if VMware tools is supposed to be a part of the updates? and if not can just download the rpm and execute it?

  Thank you

  John

  Vima-update is update patches on vMA and has nothing to do with VMware Tools. As long as VMware Tools is running, you will be able to make a stop of comments, it does not require the most recent version. The reason for which the tools of vMA is outdated is probably due to when it was released, the Tools version was the latest version and compatibility purposes, they kept to that. If you want tools to update, just right click on the VM and install VMware Tools.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• VMware tools does not start on the comments

  I would be recognizing a few tracks on this problem, the VMTools won't start;

  The server VM/host: Linux 2.6.18 - 92.1.22.el5PAE #1 SMP i686 i686 i386

  Comments: Linux 2.6.18 - 92.1.22.el5PAE #1 SMP i686 i686 i386

  Anything not appearing in the newspapers when I try to start the services;

  status of /etc/init.d/VMware-Tools

  VMware-guestd is not running

  /etc/init.d/VMware-tools start

  Checking connection to hot acpi OK

  Starting VMware Tools services on the host:

  Switching to host config: OK

  status of /etc/init.d/VMware-Tools

  Mike

  Before running VMware Tools for the first time, you must

  Configure it to your kernel running on the

  following command: "/ usr/bin/vmware-config-tools.pl".

  Config tools... He'll try to compile tools for your kernel, make sure you have the kernel and GCC installed headers.  If the compilation fails, there should be a build any - any for the "vmware tools" somewhere on this site...

• Catch 22 tries to install VMware Tools

  I created a Windows 7 VM from a physical PC. I 'play' on a Player 10 Windows via VMware Workstation 12 host, connect to the guest and then click on the "Install tools" button in the player. I see this error message:

  "The virtual machine must have a virtual CD/DVD device to install VMware Tools."

  OK, so I turned off the guest who also ends the player, rerun the player, select the virtual machine and click on "Edit virtual machine settings". On the Hardware tab, I click on the Add button, select "reader of CD/DVD", click Next, select the "use ISO image" radio button (because I guess that's what the error message means by "virtual CD/DVD"), and then click Next, and then I get invited to an ISO image. And that's the Catch 22 - the error message indicates that the player has just need a virtual device, not an ISO, but when I try to add a virtual device, the player wants an ISO.

  How to break this vicious circle and install VMware Tools?

  I thought about it myself the answer to a question on the superuser. Here are the steps:

  1. Stop the virtual machine
  2. Run the drive and select the virtual machine
  3. Click on "Edit virtual machine settings".
  4. Click on "Add..." "in the Hardware tab
  5. Select "CD/DVD Drive", and then click Next
  6. Select the "use ISO image" radio button and click Next
  7. Navigate to C:\Program Files (x 86) \VMware\VMware drive and double-click windows.iso
  8. Uncheck the box "Connect to light" (probably any) and click on finish
  9. Click OK
  10. Click on "Play virtual machine."
  11. Log on to the virtual computer
  12. Click installation tools
  13. Follow the instructions in the installer

• VMware Tools not settled in XP Pro Sp3 invited

  I think that VMware tools is supposed to install drivers for these (SCSI), which are of unknown devices in my device manager and Vga adapter but it crashes in normal and safe mode on my xp after manual installation running.  Have also tried to folder on the drive.

  Anyway to get these installed and get VMware tools running?

  Also MY XP hangs after logging in normal mode and in safe mode I get error blue screen after awhile 0X0000008E and similar.

  Yes I am the administrator also - I'm using the official XP administrator account (account first when it was setup) but still the problem.  There maybe some group policy or the registry thing/permissions setting (I have set permissions as approved for the application installer and still issue).  Don't know what else to try.  In any case thanks for trying to help.  Let me know if you think of something else.

  Post edited by: Astrogirl
  Hi I think that question could have been set by the combination of responses - I tried to configure the virtual machine through my windows 8.1 host VMWare converter standalone 5.5.1 - selection only add Vmware Tools (later) and remove restore points and after responsible for this virtual machine without register suspended or system crash or wedging.  VMware tools of the 6 worm drive was also loading and installation had to find setup.exe and run it from ISO loaded manually (when selected for the installation of the player window - Player - manage - install Vmware Tools).  However obtained related permissions errors and install the first roll back (see attached screenshots).  Then I loaded the regedit and set of local service, service network and administrator name real current user in its entirety with all permissions to access these key: HKLM system services and under software - perflib under Microsoft - Windows NT - current worm (although the latter do not know if it had to) - missed me the perflib key being added if it based on another doc help on the internet.
  Then restart may have helped also but Vmware tools installed without error and in Device Manager I also removed any? and unknown devices, but my SCSI and VGA drivers now loading properly.

  Thank you and thank all those who contributed to this issue - so seems a problem now solved.  Your answers have helped keep research regarding permissions and versions of vmware and reminded me to try to reconfigure etc. have been so helpful.  I hope that these positions help others facing similar problems.

• The VMware Tools ISO image does not exist or is not accessible

  I have a few virtual machines with a yellow exclamation mark on the vmware tools icon indicating that they can be updated. When I try and update vmware tools manually, I get the error: "VMware ISO image tools exist or is inaccessible. See the error of the stack for more details on the cause of this problem". Below in the window of the error stack, I see messages, 'called 'VirtualMachine.MountToolsInstaller' or object < servername > ESXi '192.168.3.39' failed. Cannot install VMware Tools. An error occurred trying to access the image file ' / usr/lib/vmware/isoimages/windows.iso ' to install VMware Tools: 0 (input/output error). If your product comes with the module of VMware tools, VMware ESX to reinstall, then try again to install the VMware Tools package in the virtual machine. »

  I got messages stating I must check vmtools directory symbolic links and I think that those who are present. I also tried to manually navigate to the image file, but it seems that there is a problem any with the file system. See the images below:

  

  ESXi installed on a USB key. The directory of the iso images is corrupt? Can anyone help me on how can I fix? Should I just replace the USB key, or is there another way?

  See the input / output error on the screen usually indicates a faulty drive (or in this case device USB). I wouldn't waste a lot of time and replace the USB key.

• AutoFit Guest stopped working after update the VMWare Tools

  I've updated Workstation version 8 to 10.  I had several virtual machines of Windows 7 x 64 I then updated with the latest VMWare tools (v9.6.1.1378637).  Now, one of the virtual machines will not automatically resize correctly.  (Three other virtual machines with the same o/s resize correctly and with Windows Server 2008 resizes correctly.)  Workstation is set to Autosize > Autofit guest.  The resized correctly VM before VMWare Tools has been updated.  In other words, the auto resizing feature worked for the virtual machine within the 10 workstation when the previous version of VMWare Tools was installed.  Upgrade VMWare Tools triggered behavior.  When I use the 'Fit Guest Now' view of the virtual machine command flashes but does not resize.  When the my computer window is resized, the prompt is not resized.

  I tried the following:

  • Uninstalled and reinstalled VMWare tools.
  • Confirmed VMWare Tools (vmtoolsd.exe) is set to start automatically and runs.
  • Changed the display of the virtual machine settings to a custom resolution and then to 'host to use setting for monitors '.
  • Attempted to change the resolution of the guest, but he won't go high 1920 x 1440 (it should be set to 2556 x 1496 based on the resolution of the other virtual machines that resize correctly).

  Thanks for your suggestions!

  Update of material compatibility on the virtual machine to which auto resize has stopped working has helped auto resize again.  Hardware compatibility was 6, 5-7.x.  I've updated to be compatible with 10.

  The question remains as to why three other similar virtual machines (with the same compatibility level of 6, 5-7.x) should not be updated so that the automatic resizing to work.

  I didn't want to answer my own question but hope this helps people who have encountered this particular problem.

• Install VMWare tools on Windows 8 (x 86) - kill comments

  I'm a consumer of Windows 8 Preview x 86 VM (built manually as 'other', since easy install did not work - http://communities.vmware.com/thread/392887).

  It would be good to install VMWare Tools on this and it seems mentioned as a success, install so - of windows.iso:

  

  and then the comments screen goes... broken:

  

  At this point, it does not. Reset the prompt, it will boot (with splash screens, etc.), but then switch to a blank screen - then... not very interesting.

  VMWare Tools works on Windows 8 Preview of consumers (x 86)?

  Don't use 'other' for Windows 8 - that makes no sense - use rather Windows 7.

  And next time just jump the video driver and install vmware-tools with "custom option.

• Update VMware tools - shows "does not work".

  I'm having a problem where vmware tools say that they are not running.

  Background:

  Upgrading to esx 4.0 to esx 4.1

  VM = Server 2008 R2 core - console open after clicking on upgrade vmtools/interactive

  past to the drive (d :) to cdrom and ran the setup64.exe

  all is well and restarted

  and now under vmware tools just says he does not

  I can ping the server and it seems that the tools are running as I can the mouse in the console window without having to leave the cursor etc..

  However it is said that they are not running and the vmware tools service does not, either. The error of the service gives when I try and start it is:

  "Error 2: the system cannot find the file specified. '.

  All other services seem to work fine on the server.

  Any ideas?

  Thank you

  Have you tried to remove the tools and reinstall?

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

  Twitter: http://twitter.com/mittim12

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

• VMware tools and host of virtual hardware upgrade process

  We currently have 8 guests esx4 we plan to upgrade to esxi5.  Our downtime window is relatively low.  We should have sufficient time to upgrade all hosts, but I'm not so sure that we will be able to get all the vm tools and equipment as well updated.  Is there a common question VMs on the older virtual hardware and vm versions tools until our next maintenance window?

  Or would it be best to try to get half of the hosts and all the computers upgraded this time and the other half next time?  We have not all hosts the value automatically vmotion machines so that they remain in place unless you have an accident.  In addition, in this scenario is any problem to launch half esx4 and the other half to esxi5?

  Any advice or ideas would be appreciated.

  Thank you

  Steve Hrabak

  Is there a common question VMs on the older virtual hardware and vm versions tools until our next maintenance window?

  There is no problem.  Your guests will not be able to take advantage of some of the new features added with vHardware 8, but as they are upgraded they will be.

  http://www.VMware.com/support/vsphere5/doc/vSphere-ESX-vCenter-Server-50-new-features.html

  y at - it no problem running esx4 half and half to esxi5

  No worries there, too.  The only thing that you must do is upgrade to VMFS5.  The bed and breakfast vSphere5 no cannot be able to see a LUN VMFS5, but everyone can see and use a LUN VMFS3

• A few questions about VMware tools and U2 of ESXi 4.0 and 4.1

  In my workplace, there is a cluster of vSphere 4 six nodes containing 5 servers ESXi 4.0 U2 (4.0.0, 261974) and a server ESXi 4.1 (4.1.0, 260247).  Aparently, it was built that way in the environment concept then deployed into production and now I head for VMware deployment.  This environment is up in producgtion now for over 8 months with this configuration, but starting to be more widely used.  Ideally, I know, we should have all the nodes on the same patch level, but here's the question.

  Models used to get the operating system to the virtual machines in this environment were built on the apparently new 4.1 server using this version of VMware tools (Version 8.3.2 build-257859).  All so most of the running virtual machines, use this version of VMware tools.  Using this new version of VMware tools on a virtual machine running on a server ESXi 4.0 U2 ESXi would cause issues?  ESXi 4.0 U2 servers push version 4.0.0 build 261974 of the VMware tools, identical to the ESXi version.  The status of the VMware tools when the new 4.1 version is running on a host of U2 4.0 still shows as OK and we have operated this way for more than 8 months.

  Another problem is that we have still a few other virtual machines with the 4.0 build U2 VMware tools so when these virtual machines will eventually be VMotioned to an ESXi 4.1 host, VMware tools show as outdated.

  Until we can get of planned downtime to upgrade the servers, it should be like that for several weeks if possible.  We have HL7 interfaces on many of these virtual machines that are not too good with VMotion and being in an organization of health care, sometimes difficult to get downtime.  It is perhaps more possible to downgrade the only host to 4.0 U2 until we can plan time to upgrade all hosts.  I would keep the node in the cluster, even if for the moment, assuming that to release 4.1 with other guests at 4.0 U2 should not cause problems, since we can use the resources of that node in this cluster.

  Until then, ensuring that all the virtual machines in the cluster use the ESXi version 4.1 of the VMware tools (Version 8.3.2 build-257859) would be acceptable?  I just wanted to check that this version should be fully backwards compatible with the previous version of ESXi 4.0 U2, and as I mentioned before, its run like that and have noticed yet all the problems and the status of the VMware Tools also records OK when this new version works on ESXi 4.0 U2 host computer.  I just wanted some feedback from those of the community.

  Thank you

  Exactly, do you VMotion, virtual host 4.1 machine and if necessary would upgrade the VMware tools. To install VMware tools, it is necessary to restart the virtual machine.

  And another option that I say is the first upgraded version of all hosts ESXi4.0 U2 to 4.1, after that, you do an upgrade in the tools of all virtual machines vmware.

  Perfect.

  You´re are welcome!