If you attempt to install the VI client, (in this case on a 2012 R2 Datacenter Server), you may see this error;
Error 28173. Setup failed to enable Microsoft .NET Framework 3.5 Refer to Microsoft KB article 2734782 and 3002547 which may help you resolve the .NET failure. You will need to enable this feature in Windows Server Manager before installing vSphere Client.
Solution
I’ve had problems with .NET on server 2012 before, so let’s cut out the middle man and install it directly from the install media. Pop in the server 2012 DVD. Then execute the following command in PowerShell, (change drive letter accordingly);
I did a VMware VI3 to vSphere (4.1 U1) upgrade today. While bringing all the guest machines across, suddenly I could no longer browse the datastore, I only had one more guest to “Add to the inventory”, and all the mission critical machines were already migrated. I tried rebooting the virtual center, I tried restarting the ESXi host machines, still it sat saying “Searching Datastore……”.
Solution
1. I found the solution by accident. I was adding virtual machines to the new VSphere inventory, so I went in search of a method of doing it from the console, I was just about to:
Command to add a VMware guest to the inventory
[box]vmware-cmd -s register {full path to virtual machine}MACHINE_NAME.vmx[/box]
But, while looking in the folder with the guest files, I saw thousands of log files, I guess the VI client is struggling to parse them all, and display them. A quick internet search and I found out I can safely delete the log files.
2. Log into the ESX/ESXi servers console, for ESXi servers (version 4.0 and below) see here, for newer versions you can simply enable SSH access from Troubleshooting Mode Options > Enable Remote Tech support (SSH).
3. Log on as root and issue the following command to find the symlink path to your shared storage:
[box]ls -l /vmfs/volumes/[/box]
4. Now you know your symlink, you can change to the folder that contains the affected guest OS.
[box]cd /vmfs/volumes/{your symlink}/{your vm folder}[/box]
5. To get rid of all the log files, simply issue the following command.
[box]rm -f vmware-*.log[/box]
6. Now retry and you should see the folder contents when you “Browse Datastore”.
Related Articles, References, Credits, or External Links
Seen when connected to the VMware VI client software, and attempting to open a console session with a virtual machine.
Solution
This is a pretty generic error, for whatever reason the client software cannot connect to the KMS (Keyboard, Mouse, and Screen).
In NEARLY every case this is a communication issue, either the machine running the client software cannot resolve the name of the ESX host that is hosting the virtual machines, or TCP Port 902 is being blocked by a firewall.
1. If you can’t simply pop the correct name in your DNS, then add the name and IP to the machines, (the one running the VI client software) host file. You will locate this in;
[box] C:WindowsSystem32Driversetc [/box]
2. Open it with Notepad, and add the IP and name of your ESX host(s), Note: I’m also putting the name and IP of my Virtual Center server as well. Save the file and try again.
3. You should now be able to connect.
It’s NOT DNS!
If you can happily resolve the name and are sure that the port is not being blocked, then have you made any IP changes? Is the default gateway on the ESX Server set correctly? And finally restart the management agents on the host, either from the console, or by running ‘/sbin/services.sh restart’.
I’ve also fixed this error by shutting down the machine > removing it from the inventory > then browsing the storage, to locate the .vmx file > then simply import it back again.
Related Articles, References, Credits, or External Links
This is a pretty generic error. It basically means “I cant connect to what you are asking me to connect to, on TCP Port 443 (https)”.
Solution
Internet searching for this error is very frustrating, everyone who was posting this error was seeing it because, instead of putting the IP address or name in the box (that actually tells you to put in the IP address or name (see image above)). If you put in https://{Name or IP Address}, you will see this error. However this was NOT MY PROBLEM.
This is happening because there is no communication between you and the ESX/vCenter you are trying to connect to. The first thing you need to do is see if HTTPS is open. On the affected machine open a web browser and point it to the same target and make sure you see the web console of the ESX/vCenter server. If you can’t see this, check firewalls (and proxies) and make sure HTTPS is not getting blocked.
In my case I could see this but it still did not work! Then I was reminded we have had strange comms problems on this site before, which I have documented here. Sure enough, when I dropped the MTU on the server I was trying to connect from (which was over a site to site VPN tunnel). It started to work fine.
Related Articles, References, Credits, or External Links
Whilst attempting to add 3D graphic support to a Windows Server 2012 guest VM, the option was greyed out.
Solution
1. Locate the .vmx file for this virtual machine and download it so you can edit it (Select a Host > Configuration > Storage > {Storage the guest is on} > Right Click > Browse Data Store > {Guest VM Name}) > Download.
2. Edit the file, and add the following to the end of the vmx file;
[box]
mks.enable3d = TRUE
[/box]
3. Upload the file back to your storage, at this point I checked and it was still greyed out. I had to remove the VM from the inventory* then add it back to the inventory.
*WARNING: Remove it from the inventory by right clicking the VM in the VI Client. DO NOT Delete it from Disk!
Related Articles, References, Credits, or External Links
I tried to install the VI client on my test network and this happened;
vSphere Client requires Windows XP SP2 or later. vSphere Client cannot be installed on a Domain Controller.
Solution
Well I’m not over the moon about that? Ive only got one permanent VM and it’s a DC? Who came up with this? What about sites who have a single DC on an ESX box? What are they going to do!
Turns out its quite easy to bypass, install the VI client from command line with a switch on the end, like so;
The install will now complete without error. I thought that it might be a cunning ploy to get me to use the new web client instead, so out of interest I tried that, and got the following error;
vSphere Web Client requires Windows Server 2008 or later. vSphere Web Client cannot be installed on a Domain Controller.
Fair enough! So I tried the same switch on that, and guess what? That works as well.
Have you installed the VI client on Windows 10? My boss asked me this week, I replied no, but if it didn’t work then loads of people would soon be moaning. I remember sometime ago I had to use comparability mode to install it on Windows 8. I had the brainwave, “Why not ThinApp the client” it would work then, but the 5.5 client stubbornly refused to fire and the ThinApp package size was enormous.
So using the manual process I had used to try and ThinApp it on Windows 8, I pulled down Windows 10 from MSDN and tried it on that, successfully.
Disclaimer: Yes you should be using the VMware web client, but what if it’s a standalone ESXi server?
Speaking of which, the web client will not currently run in ‘Spartan’, (yes flash is enabled).
But it runs in Internet Explorer 11, which is still in Windows 10.
Solution
Anyway we want the ‘Fat’ VMware client, here I’m using 5.5 (build 1618071). Which I have downloaded to the desktop.
1. The install EXE file is actually an archive with the installation files within it, to open that archive I’m going to use 7Zip, download and install that first.
2. Now I can open the archive and navigate around the folder structure inside.
3. Locate and extract the actual VI client install file (in the bin folder).
4. VI client requires .Net 3.5 the install file for that is in the redist folder.
5. Finaly it also requires Visual J#, you will find that in redistvjredist directory locate the 32 or 64 bit version as applicable, and extract that also.
6. Install the .Net 3.5 first, Then install Visual J#.
7. Then on the properties of the extracted setup file >properties > Compatibility > Run as Windows 7 > Apply > OK.
8. I also launched by right clicking and selecting ‘Run as Administrator’, but I don’t think that’s necessary. When done launch the application.
9. All being well, you should be able to log in as normal.
Related Articles, References, Credits, or External Links
I have made the transition to a MAC laptop pretty easily, but theres one thing thats still a pain, VMware ESXi servers! I know these days vCenter has a nice shiny web management portal, but ESXi does not. When I’m working on the test bench I usually connect using the VI client from a virtual machine running inside VMware fusion. Which works, but the performance is not brilliant, things wont move where I want them, and for some reason copy and cut will work, but paste does not (I have no idea either).
So when I’d spend half an hour trying to move some certificates from one VM to another, I lost my temper, and made a monumental discovery. VMware fusion can connect straight to an ESXi host, (why did I not know this!)
Solution
1. With Fusion running > File > Connect to Server (or command+K).
2. Enter the details as if you were using the VI client > Connect.
3. If you are using self signed certificates accept the warning and continue.
4. OK it looks a bit mickey mouse but from here you can open a console, and provided the VMware tools are installed in the VM it performs quite well.
5. Console Session.
6. And you can even change the VM settings, including browsing data stores on the ESXi server for ISO files etc.
Related Articles, References, Credits, or External Links
