VMware has recently released ESXi 6.5 and last week I posted on how to Install VCSA 6.5 as well as how to upgrade VCSA 6.0 to 6.5, now we’re going to look at how to easily and quickly perform an ESXi 6.5 upgrade via command line.
Synology has just released DSM 6.0.2-8451 Update 2 which offers almost a dozen fixes as well as patches multiple vulnerabilities found throughout OpenSSL and curl. If you haven’t already, it would be highly recommended to go ahead and do so now. Below is a list of fixes in DSM 6.0.2-8451 Update 2.
Microsoft recently pushed out a “Convenience Update“, a sort of rollup of rollups for Windows Server 2008 R2 SP1 and Windows 7 machines. This “Convenience Update” however comes with an incompatibility issue with VMware virtual machines that are using VMXNet3 network adapters, which causes the network to become unresponsive.
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.
Just last week I replaced my Synology DS412+ to with a Synology DS1815+, which has twice the drive bays with the addition of supporting two expansion units, a much more powerful CPU, and 2GB RAM out of the box.
I’ve seen some people mention with very mixed results that both the Synology DS1515+ and Synology DS1815+ can be upgraded to 16GB of RAM, the biggest issue seems to be around what memory modules to use. So I figured I’d document how I upgraded my DS1815+ to 16GB RAM and what memory I used with success.
Just a quick heads up! Over the last week I’ve been upgrading our vCenter servers from version 5.5 to the most recent 5.5 Update 3b version and have ran into a small hiccup.
The upgrade of SSO, Web Client, Inventory Service and even vCenter server all went as expected without any issues. Then I rebooted the vCenter server and after the reboot noticed that the vCenter server service hadn’t started and when I tried to start it manually I then received the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.