Skip to main content

How to find out what VMTools version will come with ESXi

Before installing an VMWare ESXi server i was little curious that what VMTools version will come after the ESXi have been installed and any VM has been created.
Looking around found a link on VMWare worth to share and keep handy while working on the deployment of VMWare especially before upgrading and existing VMWare infrastructure to newer one you would like to know the VMTools version, its support with your Operating Systems in Guest OS and/or read upon open or resolved caveats by identifying the VMTools version prior the installation and choosing the right version for your environment.

Below information has been collected from the link here

# The ESXi server mapping is only to show that the particular version of
# Tools ships with that particular ESXi server build number, but the Tools
# can work with a greater range of ESXi versions.
#
# Column 1: Tools version on NGC/VI Client
# Column 2: ESXi server version.'esx/0.0' indicates that the tools version
# is not yet bundled with ESXi.
# Column 3: Tools version on guest Setup/About page
# Column 4: ESXi server build number
#
10287       esx/0.0      10.1.15
10282       esx/0.0      10.1.10
10279       esx/6.5u1    10.1.7        5969303
10277       esx/6.0p05   10.1.5        5572656
10272       esx/6.5p01   10.1.0        5146846
10272       esx/6.5      10.1.0        4564106
10252       esx/6.5      10.0.12       4564106
10249       esx/5.5p11   10.0.9        6480324
10249       esx/5.5ep11  10.0.9        5230635
10249       esx/6.0u3    10.0.9        5050593
10249       esx/5.5p10   10.0.9        4722766       
10249       esx/6.0p04   10.0.9        4600944
10249       esx/5.5p09   10.0.9        4345813
10249       esx/6.0p03   10.0.9        4192238
10249       esx/5.5p08   10.0.9        4179633
10248       esx/0.0      10.0.8
10246       esx/6.0u2    10.0.6        3620759
10245       esx/0.0      10.0.5
10240       esx/6.0ep05  10.0.0        3566359
10240       esx/6.0p02   10.0.0        3380124
10240       esx/5.5p07   10.0.0        3248547
10240       esx/5.5ep10  10.0.0        3568722
10240       esx/5.5ep09  10.0.0        3343343
9541        esx/6.0ep04  9.10.5        3247720
9541        esx/6.0u1    9.10.5        3029758
9537        esx/6.0p01   9.10.1        2809209
9536        esx/6.0      9.10.0        2494585
9359        esx/5.5ep08  9.4.15        3116895
9359        esx/5.5u3    9.4.15        3029944
9356        esx/5.5p05   9.4.12        2668677
9355        esx/5.5ep07  9.4.11        2638301
9355        esx/5.5ep06  9.4.11        2456374
9355        esx/5.5p04   9.4.11        2403361
9354        esx/5.5ep05  9.4.10        2143827
9354        esx/5.5p03   9.4.10        2143827
9354        esx/5.5u2    9.4.10        2068190
9350        esx/5.5p02   9.4.6         1892794
9349        esx/5.5ep04  9.4.5         1881737
9349        esx/5.5ep03  9.4.5         1746974
9349        esx/5.5ep02  9.4.5         1750340
9349        esx/5.5u1    9.4.5         1623387
9344        esx/5.5p01   9.4.0         1474528
9344        esx/5.5      9.4.0         1331820
9233        esx/5.1p09   9.0.17        3872664
9232        esx/5.1p08   9.0.16        3070626
9231        esx/5.1p07   9.0.15       2583090
9231        esx/5.1u3    9.0.15        2323236
9229        esx/5.1p06   9.0.13        2126665
9228        esx/5.1p05   9.0.12        1897911
9227        esx/5.1ep05  9.0.11        1900470
9227        esx/5.1p04   9.0.11        1743533
9226        esx/5.1ep04  9.0.10        1612806
9226        esx/5.1u2    9.0.10        1483097
9221        esx/5.1p03   9.0.5         1312873
9221        esx/5.1p02   9.0.5         1157734
9221        esx/5.1ep03  9.0.5         1117900
9221        esx/5.1u1    9.0.5         1065491
9217        esx/5.1ep02  9.0.1         1021289
9217        esx/5.1p01   9.0.1         914609
9216        esx/5.1      9.0.0         799733
8401        esx/5.0p13   8.6.17        3982828
8400        esx/5.0p12   8.6.16        3086167
8399        esx/5.0p11   8.6.15        2509828
8398        esx/5.0p10   8.6.14        2312428
8398        esx/5.0p09   8.6.14        1976090
8397        esx/5.0ep06  8.6.13        1918656
8397        esx/5.0p08   8.6.13        1851670
8396        esx/5.0p07   8.6.12        1489271
8395        esx/5.0u3    8.6.11        1311175
8395        esx/5.0p06   8.6.11        1254542
8395        esx/5.0ep05  8.6.11        1117897
8395        esx/5.0p05   8.6.11        1024429
8394        esx/5.0u2    8.6.10        914586
8397        esx/5.0p08   8.6.13        1739451
8389        esx/5.0p04   8.6.5         821926
8389        esx/5.0p03   8.6.5         768111
8389        esx/5.0u1    8.6.5         623860
8384        esx/5.0p02   8.6.0         515841
8384        esx/5.0p01   8.6.0         474610
8384        esx/5.0      8.6.0         469512
8307        esx/4.1p11   8.3.19
8307        esx/4.1p10   8.3.19
8307        esx/4.1p09   8.3.19
8307        esx/4.1p08   8.3.19
8306        esx/4.1p07   8.3.18
8305        esx/4.1p06   8.3.17
8305        esx/4.1u3    8.3.17
8300        esx/4.1p05   8.3.12
8300        esx/4.1p04   8.3.12
8300        esx/4.1u2    8.3.12
8295        esx/4.1p03   8.3.7
8295        esx/4.1u1    8.3.7
8290        esx/4.1      8.3.2
8199        esx/4.0p15   8.0.7
8199        esx/4.0p14   8.0.7
8198        esx/4.0p13   8.0.6
8197        esx/4.0ep09  8.0.5
8196        esx/4.0p12   8.0.4
8196        esx/4.0p11   8.0.4
8196        esx/4.0u4    8.0.4
8196        esx/4.0p10   8.0.4
8196        esx/4.0u3    8.0.4
8195        esx/4.0u2    8.0.3
8194        esx/4.0u1    8.0.2
8192        esx/4.0      8.0.0
7304        esx/3.5p27   7.4.8
7304        esx/3.5p25   7.4.8
7304        esx/3.5p24   7.4.8
7304        esx/3.5u5    7.4.8
7303        esx/3.5u4    7.4.7
7302        esx/3.5u3    7.4.6
7302        esx/3.5u2    7.4.6

Comments

Popular posts from this blog

Connection control operation failed for disk 'ide1:0'

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine.

What worked for me, is
1. Uncheck the "Connected and Connect at power on" from Device Status.
2. Then Change the Device type from "Datastore ISO File to Client Device" Radio Button
3. and press OK to save the changes.

Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui

where it asks

"The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?"

You need to select yes to eject the CD-ROM and then remove the ISO file successfully.

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application.

As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps.


Open your mRemoteNGCreate a folder if you want segregation of multiple networksCreate a new connectionEnter the IP address of remote server under connection in Config paneUnder the config pane, select protocol "SSH version 2".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below.


In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.



a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.