Every now and then new vSphere related must-have books are released, and this month there is no less than two of them, namely the vSphere 6.7 Clustering Deep Dive and VDI Design Guide: A comprehensive guide to help you design VMware Horizon, based on modern standards.
Like Sam and Simon over at definit.co.uk I’ve done a quick GDPR-related overhaul of the site.
This is the third talk I’ve found worthy of publishing in the Awesome Talks series. Enjoy Simon Wardley’s Researcher, Leading Edge Forum, keynote from KubeCon + CloudNativeCon Europe 2018 called «Crossing the River by Feeling the Stones».
Simon’s presentation technique, flair and master of language is flat out impressive — and fun!
If you boot your ESXi hosts from SD-cards or USB you might have run into this issue. Suddenly your host(s) displays the following under events: «Bootbank cannot be found at path ‘/bootbank’.»
Usually this means that the boot device has been corrupted somehow, either due to a device failure or other issues. Normally the host continues to run, until it’s rebooted that is…
Before you start on this rather long post, have a go at part #1:
This is a long read. To get to the juicy part on how Intel potentially shipped pre-release microcode to partners, skip to section 3. The short, short version is that the official Intel microcode update contains newer microcode for Skylake-SP and Kaby Lake/Coffe Lake than what currently is shipping from VMware/HPE/DellEMC etc.
Disclaimer: This is a report based on current development as of 7. January, the situation is changing by the hour so read this opinion piece with that in hindsight.
Unless you have been living under a rock for the last week you will know by now that there is a universal design flaw in most modern microprocessors, leaving them vulnerable to a serious information disclosure problem that requires updates to all operating systems and processors.
If you are not familiar with the issue, start here: Meltdown and Spectre
The issue has been known by Intel at least since June, and has been under embargo while everyone has been hammering out code to mitigate the threat and be ready when the embargo was lifted.
My good friends, and fellow VMUGgers, in Denmark is once again arranging the largest VMUG event in the Nordics in January 2018.
The Nordic VMUG Conference promises to be just as awesome as previous versions, just have a look at this speaker list:
This isn’t a technical talk, it’s originally geared towards developers but Scott’s message should resonate with everyone in the tech field. In general, it’s about how you can deal with large amounts of information. Lot’s of great takeaways here!
Simply put, this little gem let’s you hide any or all menu bar icons in macOS, while still keeping them easily accessible behind a small arrow:
This is the first post, in what hopefully will turn into a series of posts, highlighting awesome talks that are freely available. There is a lot of great content out there, both inspirational and funny, and I’ll try to publish my favorites when I find them.
So here is the first one!
Warning: Shameless self promotion ahead!
November 30th I’ll be joining Martin Plesner-Jacobsen from Veeam for a Live Webinar: _Veeam integration with VMware vSAN, vSphere tags and SPBM policies. _
Now that’s a lot of goodies in one place!
Myles Gray asked me how I integrate Pocket with Todoist, after my How I use Todoist post, and the answer is very simple: IFTTT. If-This-Then-That lets you connect services, and create rules (or applets) that trigger based on events in those services, luckily both Todoist and Pocket are supported.
Now, there is a bit of overlap between how I use Pocket and Todoist, but I mainly use Pocket to keep track of links I want to either read later, or use as basis for blog posts.
As I’ve mentioned before, I use Todoist to keep track of my personal to-do list. This is the first to-do manager I’ve been able to stick with, and I’ve been using it daily for well over 2 years now. In that two year period I’ve reorganised it a bit, but for the most part I’ve been able to keep to the main structure I initially created when setting it up the first time.
Veeam is hosting their VeeamOn Tour Virtual 2017 event on December 5th, and I’ll be part of the panel of bloggers in the Expert Lounge!
Veeam describes the event like this:
The biggest online Availability event in EMEA — VeeamON Tour Virtual 2017 — is once again coming to your desktop! No need to leave your chair — Experience Availability simply by joining us for an ultimate digital journey!
For those who don’t know, Royal TSX is an awesome Remote Management solution, which supports RDP, VNC, SSH, S/FTP and even ESXi and vCenter. I’ve been using it for years, not just because they offer free licenses for vExperts (and others), but simply because it works really well. Store it’s config file on a synchronized file area (like Dropbox), and boom, your config follows you around from machine to machine, including custom icons. What’s not to like?
In the last few months, I’ve seen an uptick in spoofed emails being sent with my own personal email domain. Not only is this extremely annoying, but more problematic is that recipients receive spam and phishing emails from what seems to be my personal mail account, simply by spoofing the from address. I don’t know why domain and email address has been «chosen» for this, but I guess this is fallout from the LinkedIn breach way back in 2012.
I didn’t think there was much I could do about this, but a recent tweet by my friend Per Thorsheim sent me down the rabbit hole.
VMware has just announced vSAN v6.6, with over 20 new features. While new and shiny features are nice I’d like to highlight a couple that I think might be undervalued from release feature-set perspective, but highly valuable in day to day operations of a vSAN environment, otherwise known as Day 2 operations.
The VMware Cross vCenter VM Mobility - CLI was recently updated so I decided to try it out. In short, this little Java based application allows you to easily move or clone VMs between disparate vCenter environments.
Welcome to the tenth edition of In The Bag! This one comes a little late, it’s (barely) Sunday here, not Friday! Sorry about that, but I was «stuck» in a secure facility all week, doing a vSphere 5.5 til vSphere 6.5 migration.
While at a customer site, migrating an old vSphere 5.5 environment to 6.5, several hosts suddenly crashed with a PSOD during the migration. Long story short, we got hit by this: VMware KB 2147958: _ESXi 6.5 host fails with PSOD: GP Exception 13 in multiple VMM world at VmAnonAllocVmmPages (2147958)