VMware has released vCenter Server 6.0 Update 2 and ESXi 6.0 Update 2 (build: 3620759) which include a number of new features and fixes. VMware has also released the much anticipate VSAN 6.2 which includes it’s own bunch of new features such as deduplication, compression, QoS, and RAID5/RAID6 Erasure coding.
You may remember not to long ago, the GHOST vulnerability found in glibc, a GNU C library. Well a new glibc vulnerability (CVE-2015-7547) has been discovered and it affects VMware ESXi 5.5 and 6.0 in addition to all versions of VMware virtual appliances running Linux such as vCenter, Orchestrator, vRealize, etc.
VMware has just released patch ESXi550-201602401-SG for ESXi 5.5 and ESXi600-201602401-SG for ESXi 6.0 which fixes the glibc vulnerability,
a patch for ESXi 6.0 has yet to be released. VMware has however posted workarounds for affected virtual appliances.
It’s no secret many people have really disliked the vSphere web client, it’s very sluggish, clunky, and based on flash (flash comes with it’s own security issues). It was rumored and highly hoped that vSphere 6 might be re-written in HTML5, but sadly this didn’t and hasn’t happened yet. While vSphere 6 did improve a bit on the web client the issues many people have had with it in the past still remain today.
Enter the VMware HTML5 Embedded Host Client fling. I’ve been using and following this fling for a while now and have really enjoyed it and with each release it keeps getting better and better.
The Embedded Host Client fling is based on HTML5 which allows it works great across all kinds of platforms, it’s fast, responsive, and doesn’t require any plug-ins – YES the VM console works great. If this happens to be a look of what’s to come in a new VMware vSphere web client, then a client is looking very promising!
If you haven’t tried it yet, you should. It’s extremely easy to install and doesn’t even require a reboot just follow these simple instructions.
Just recently we have some hardware issues in our primary datacenter and during that time had a few VM’s that became unresponsive and needed to get them back online. The VM’s had stopped responding to the normal vSphere commands to reboot, shutdown or even restart. I didn’t want to power cycle the entire ESXi host and instead just power off an unresponsive VM.
Here is a quick and easy way to do just that using ESXTOP.
VMware has released vSphere 6.0 Update 1, ESXi 6.0 U1 and updates for several other VMware products:
- VMware vCenter Server 6.0 Update 1 Release notes / Download
- VMware ESXi 6.0 U1 Release notes / Download
- VMware Data Protection 6.1 Update 1 Release notes / Download
- VMware Site Recovery Manager 6.1 Release notes / Download
- VMware vCloud Director 8.0 Release notes / Download
- VMware vRealize Automation 6.2.3 Release notes / Download
- VMware vRealize Operations Manager 6.1.0 Release notes / Download
- VMware vRealize Orchestrator Appliance 6.0.3 Release notes / Download
- VMware vSphere Data Protection 6.1 Release notes / Download
- VMware vSphere Replication 6.1 Release notes / Download
Preparing for some upcoming audits, I noticed one of the checkpoints was to ensure each ESXi host was configured with a warning banner stating the machine is being monitored and audited when someone logs into the ESXi host via SSH. This type of message is something you see on most any company or government computer before you login.
There are two message types that can be used to achieve this, the first being login banner (/etc/issue) and MOTD (/etc/motd). The difference between the two are where they are shown. The login banner is shown between the username and password inputs during login, while the MOTD is displayed after a user has successfully logged into SSH.