When I turned on my computer today and browsed to my company intranet my browser had problems displaying the site. Wondering which version I had I went to “help” then about”. Somehow I got ver. 11 installed on my machine. What was disturbing was the little check box I saw (and unchecked) that said “Install new versions automatically”. Who at Microsoft thought this was a good idea? I really wish Microsoft would just stop trying to be like Apple and Google and go back to being Microsoft.
5 – Missing Realtek drivers – so, on a previous blog post I showed how to add the Realtek drivers back to an already installed ESXi 5.5 installation and included a link to a post which explained how to compile an install disc that already included them. Most of us IT Pro’s that are running white box labs know how important this was to us when they introduced it in 5.0. I have never heard of a company removing drivers from their distribution unless the were antiquated which is why this was such a surprise. Why did the not keep the drivers? This is one of the most popular NIC chip sets out there.
4 – Dump collector configuration still requires you to use CLI – Why do I still have to use the command line interface to configure this feature. VMware does not recommend you log on to the machine using ssh or the control console except for diagnostics but they haven’t made it possible for you to configure their base features using the GUI?
3 – Single sign on – Need I say more? Yeah, I get that not everyone in the world is running Active Directory (but they should be) and that you want to be platform agnostic. That said, when I installed single sign on it did not discover the domain on which I installed it. Ultimately I had to go into the vSphere Web client (which is not installed until after vCenter Server) to add then domain. Then I had to go back into vCenter and create the administrator delegations. This should really be automatic in my opinion. Oh, and before any one goes on about the ‘simple install’ sit back and think about how many bad practices (like installing database engines and files on your system volume) are included in that process.
2 – Different virtual hardware versions (8 vs VMX-10) – I was really looking forward to experimenting with vFRC (vSphere Flash Read Cache) until I realized it required virtual hardware version 10 (VMX-10). The problem here is that to create (or manage) a virtual machine that has VMX-10 you have to do it from the web client. When creating with the conventional client is only creates machines with hardware version 8. The traditional client cannot manage virtual machines with a hardware version greater than 8 so becomes almost useless to manage VMX-10 based machines.
1 – Distributed administration consoles – so, as you may have heard, VMware is really pushing their web client. I am not personally against this as it is more efficient use of bandwidth. However, not all of the administration tasks can be performed in the web client and not all of the administration tasks can be performed in the conventional client. This shows a divergence in management which, as all us IT Pro’s know, is not a good thing. No one wants to be switching between clients to perform administration now do they want to memorize what tasks have to be done where.
Well, when VMware released ESXi 5.5 I was very excited to get it installed on my home lab and take it for a spin. Unfortunatly, after installing it I only had one active adapter, a broad com adapter. See, like many other people I built white box lab using Realtek network adapters which VMware included in versions 5.0 and 5.1. Honestly, I am not sure what they were thinking when they decided not to include those drivers in the distro. It was kind of like giving all us IT Pro’s with home labs the finger. That said there are several pages which explain how to download the .VIB’s and create a custom ISO. One of the first to publish this was Erik Bussink (http://www.bussink.ch/?p=1228). This will easily solve your problems but you have to re-install the operating system.
In my case, I simply did not want to create the custom .ISO so here is the instructions to add the RealTek drives to the stock install of ESXi 5.5
First, Download the .vib files. I have posted them on my site for reference
Then, copy them over to the server (using WinSCP or something similar)
Finally, connect to the server (I use Putty) and install them manually using the following command - # esxcli software vib install -v </path/vibname.vib>
This method will not require you to re-install the operating system.
Thanks go out to Erik Bussink.
Did you know that in order to expand the hard disk of a shared virtual machine on VMware Workstation you have to un share it first? Me either. Not sure why. Essentially, you have to un share it (which moves it to a different directory) and then the utilities button is accessible from where you can increase the size. Then of course you have to expand the partition inside the VM, shut it down, the share it out again (for those that do not know, a shared virtual machine will auto boot with your system).
“Really? Why did they do this? This pretty much kills it for all of us that use home labs.”
Yeah, that is what I said when I installed 5.5 too. Let me show you how to get them back.