Discover VMWare-Tools-Version

Similar Questions

• VMware Tools Version 5.0.1 of merger?

  Can someone else please check that the correct version of VMware Tools for Windows in Fusion 5.0.1 is 9.2.1 build-818201?

  Thank you!

  Clayj ha scritto:

  Can someone else please check that the correct version of VMware Tools for Windows in Fusion 5.0.1 is 9.2.1 build-818201?

  Thank you!

  Yes, I can confirm that.

• What is the VMware Tools version / build number in ESXi 4.1U2?

  Hello world

  As far as I know, the version/version number of "VMware Tools" in ESXi 4.1U1 ("4.1 Update 1") is "Version 8.3.7, build-341836" (at least for Windows virtual machines). "

  Can someone tell me if the version/version number of "VMware Tools" in 4.1U2 ("4.1 Update 2") ESXi is different? I read the "Release Notes" for vCenter Server 4.1 update ESXi 4.1 Update 2 - http://www.vmware.com/support/vsphere4/doc/vsp_esxi41_u2_rel_notes.html - and 2 - http://www.vmware.com/support/vsphere4/doc/vsp_vc41_u2_rel_notes.html - but I did find the information on this subject.

  Thanks in advance!

  See you soon,.

  Ricardo

  Hello

  Based on my VMware 4.1 hosts update 2, I ve vmware tools 8.3.12.8191

  So I found following KB that can be useful for you - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003947

  Post edited by: MauroBonder

• VMware Tools Version with vCenter update 4

  Can someone tell me what version of vmtools with vCenter 2.5 update 4?

  Rick,

  The tools are specific to the host and not vCenter.

  Jase McCarty

  http://www.jasemccarty.com

  Co-author of VMware ESX Essentials in the virtual data center

  (ISBN:1420070274) Auerbach

  _{Please consider awarding points if this post was helpful or appropriate}

  

• 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

• 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

• Wrong message 'VMware Tools can be updated' for the virtual machine within ESXi 4.1

  These VMware tools in my guest operating system keep on the list "VMware Tools can be updated" and the yellow exclamation point.

  Host operating system is ESXi 4.1.0 build 348481

  VMware Tools version is 8.4.8 build 491717

  It is not on the files with the extension.001 as described in the following article

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2001382

  I checked and there is no file with this extension.

  I think that VMware tools is unable to read or to compare the correct numbers.  Or is there another reason?

  Reply to my own post:

  The answer, in fact the procedure, is inside this article:

  https://communities.VMware.com/docs/doc-31365

  For some reason VMware Tools is not installed correctly (for example files from previous versions are left inside the hard disk).  So I have to do a manual cleaning before you reinstall the tools.

• VMware Tools update fails

  When I run a virtual machine, I get a popup telling me that a new version of VMware Tools (version 8.8.2) is available.  If I click to download, update the product for awhile then stops with an error box saying that there was a problem updating the component.

  As far as I can tell, I have VMware Tools installed 8.8.2.  How can I remove this popup?

  Running VMware on Linux CentOS 5.8 8.0.3.

  With the machine off, go in the Edition-> Preferences-> updates and and uncheck the two boxes «»  That should do it.

• VMS with VMware Tools ESXi5 works for host ESX4.1?

  Hello

  Just upgraded a 4.1 ESX host to ESXi 5 host in a Cluster of 3 armies.

  We observe that VMware tools running obsolete for the virtual machines on the host ESXi5.  We would like to know if we apply the latest VMWare tools on those virtual machines, they run correctly when they are transferred to ESX 4.1 hosts?

  Thank you

  VMware Tools version 5.0 is compatiable on 4.x, but the virtual hardware version 8 is NOT compatible on 4.x

  Se see page 3 what 's new

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

• Question number building VMWare tools

  Hi all

  This article:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003947

  said that the version of VMWare tools number should be the same build number of the ESX host.

  This is not what I see here. Here's what we have:

  ESXi, 4.1.0 260247 (as reported by vSphere Client)

  VMWare tools Version 8.3.2 build 257589 (as reported by VMWare dialogue tools 'about')

  It is its own version of the tools for the host?

  I've uninstalled and reinstalled the tools on my guests several times, and they always communicate the same build number.

  Is it possible for a host to install a version of 'out of sync' tools? If so, how can I "Resync" it?

  Thanks for the pointers.

  Luke

  I would be grateful if you could tell me whether or not this file should be present on the guest operating system.

  Take a look at activation record for VMware Tools within an operating system called Windows debugging in this article that the location of the "tools.conf" queue is specified for different OS comments.

  I checked my VMs, I saw that there is a file with a name like on some VMS (but it is empty), while there is no file on others.

• vSphere VMware Tools

  Hello

  I have to upgrade my host 3.5 4.0 through the host update utility.  Then, I upgraded vmware tools on a virtual machine (with success, according to the OK status in VI client).  When I tried to upgrade the virtual hardware, I got an error saying my vmware tools has not updated yet.  So I powered the VM on connected and checked the version of VMware Tools.  It reads: v2.0!  I have re-run the again manually, vmware tools upgrade restarted, and it was always the same.  I checked on one of my other virtual machines that have not been upgraded yet, and the Tools version is 3.5 as expected.  I wouldve thought he'd say v4.0 for vSphere.

  Is this normal?  If not, how to fix this?  What version is your vmware tools show?

  I think something is wrong since I also tried to add paravirtual scsi and nic to the virtual machine, and the pilots were not available anywhere.  The virtual machine also knows morbid slow network communications.

  Help!

  Hello

  I have VMware ESXi 4.0 Version 208167, after installing the VMware tools, it shows Version 4.0

  

  Check other virtual machines VMware Tools Version?

  Tried to uninstall VMware's VM tools completely and after restart, install the new VMware tools?

  -= If you have found this note/response useful, please consider awarding points to 'Correct' or 'useful ' = -.

  -= If there is a mistake in my notes, please correct me! =-

  -= Thank you =-

• PowerCLI download guest OS version reported by VMware tools set up versus when VM created or altered.

  in my inventory and what RV tools scripts out I get the version of the OS that is selected for the virtual machine to change settings - options - version.  I would also like to produce a list of the version of the OS that signal the VMware tools in order to find those with poorly chosen OS and fix them.  I tried to. ExtensionData.config.Tools and I do not see the operating system listed there, anyone know where it is?

  PowerCLI C:\Program Files (x 86) \VMware\Infrastructure\vSphere PowerCLI > $vm1.extensiondata.config.tools

  ToolsVersion: 9354

  AfterPowerOn: true

  AfterResume: true

  BeforeGuestStandby: true

  BeforeGuestShutdown: true

  BeforeGuestReboot:

  ToolsUpgradePolicy: upgradeAtPowerCycle

  PendingCustomization:

  SyncTimeWithHost: true

  LastInstallInfo: VMware.Vim.ToolsConfigInfoToolsLastInstallInfo

  DynamicType:

  DynamicProperty:

  aside, where can note I find a resource that shows what options are available for each command get, such as get-host and get - vm?  I learn a lot about what I can find in powercli by running this command and explore those who returns VMware.Vim..., but would allow me to save a lot of time to be able to just go get him.

  PowerCLI C:\Program Files (x 86) \VMware\Infrastructure\vSphere PowerCLI > $vm1 = get - vm test-vm1

  PowerCLI C:\Program Files (x 86) \VMware\Infrastructure\vSphere PowerCLI > $vm1.extensiondata

  Capacity: VMware.Vim.VirtualMachineCapability

  Config: VMware.Vim.VirtualMachineConfigInfo

  Layout: VMware.Vim.VirtualMachineFileLayout

  LayoutEx: VMware.Vim.VirtualMachineFileLayoutEx

  Storage: VMware.Vim.VirtualMachineStorageInfo

  EnvironmentBrowser: EnvironmentBrowser-envbrowser-653

  ResourcePool: ResourcePool-resgroup-11

  ParentVApp:

  ResourceConfig: VMware.Vim.ResourceConfigSpec

  Duration: VMware.Vim.VirtualMachineRuntimeInfo

  Comments: VMware.Vim.GuestInfo

  Summary: VMware.Vim.VirtualMachineSummary

  Data store: {Datastore-datastore-591}

  Network: {Network-network-145}

  In summary:

  RootSnapshot: {}

  GuestHeartbeatStatus: Green

  LinkedView:

  Parent: File-group-v.41

  CustomValue: {}

  OverallStatus: Green

  ConfigStatus: Green

  ConfigIssue: {}

  EffectiveRole: {-1}

  Authorization: {}

  Name: test-vm1

  DisabledMethod: {UnregisterVM, RevertToCurrentSnapshot_Task, Destroy_Task, RemoveAllSnapshots_Task...}

  RecentTask: {}

  DeclaredAlarmState: {10.vm - alarm-653, alarm - 11.vm - 653, 653 - 2.vm - alarm, alarm - 23.vm - 653...}

  TriggeredAlarmState: {}

  AlarmActionsEnabled: true

  Tag                  : {}

  Value                : {}

  AvailableField: {FA. GosAgent}

  MoRef: VirtualMachine-vm-653

  Client: VMware.Vim.VimClientImpl

  Try $vm. ExtensionData.Guest.GuestFullName

• No end of shooting reports supported by VMWare and VMWare tools Windos version?

  Hello.

  Now what I want to know exactly, that's the latest VMWare workstation with VMWare tools are supported on Windows 98 (Yes, sad, we must deploy some of these virtual machines in order to revive old software).

  Is there any public document describing VMWare tools OS are supported by the version of VMWare?

  Guys thank you very much in advance.

  According to the HCL, Windows 98 is supported for up to WS 9.0, the Tools for this version can be the one to use.

  André

• How to see the latest version of Vmware Tools in CentOS guestOS?

  After the installation of the new v5.0.0. VmWare Player on Win7 hostOS I improved as VmWare Tools in CentOS guestOS.

  After that (and restart) I wanted to check/verify the current installed version of VmWare Tools and entered (as usual in previous versions):

  VMware-toolbox - version

  Unfortunately, the Terminal was told: "unknown command".

  Who is wrong?

  If not, how can I check the currently installed version of VmWare Tools?

  Matt

  Try the following command:

  vmware-toolbox-cmd --version
  

  It reported the following on my setup:

  9.2.0.15626 (build-799703)