VMware Octopus wallpaper
Duncan over at Yellow Bricks was nice enough to share this VMware Octopus wallpaper. Of the VMware wallpaper I have this one is my favorite for some reason.
Similar Posts
How to easily add an ESXi SSH login message banner
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.
Read More “How to easily add an ESXi SSH login message banner”
VMUG EVALExperience, the new VMware VMTN
Long ago VMware offered a program called VMware Technology Network (VMTN) which was very similar to Microsoft’s TechNet, which allowed you to download and run various VMware software within your home lab for a small yearly fee. Just like the Microsoft TechNet, the VMware VMTN program was eventually closed. From the time the VMTN program closed many people have begged and pleaded with VMware to bring the program back, there is even a long forum thread asking VMware to bring VMTN back. Though it never did… until now.
How-to fix VMware Converter error FAILED: Unable to find the system volume, reconfiguration is not possible.
I was recently tasked with migrating a Hyper-V machine to our VMware environment. However, each time VMware Converter was ran, the task would fail at 97% with an error “FAILED: Unable to find the system volume, reconfiguration is not possible.“.
Looking further into the virtual machine there were a number of concerns I had on the VM. One such issue which I believe might be causing the above error, is that the system volume drive was on drive 0 while the “C:” drive was on drive 1. Whereas these are typically on the same drive in most Windows installs.
Below are the steps I took to fix this VM and made the migration from Hyper-V to VMware a success.
VMware Workstation 12.5.5 released, fixes Pwn2Own exploits
VMware has just released Workstation 12.5.5 which includes bug fixes as well as fixes for several vulnerabilities found in this years Pwn2Own contest, which two hacking teams, 360 Security (@mj011sec) and Team Sniper was able to successfully complete a virtual machine escape.
While these are serious exploits, VMware has said they are not aware of any active exploitation of the vulnerabilities that has now been fixed in 12.5.5.
Read More “VMware Workstation 12.5.5 released, fixes Pwn2Own exploits”