Virtualization is all around us these days. In the world full of clouds, hypervisors, remote desktops and many, many more “virtual” stuff, it’s very important to keep in mind how it all started. Even though it might seem like virtualization picked up only mere few years ago, it was actually around for over 50 years now! Granted, that ancient technology was nearly completely different from what we have now, but isn’t that the case with every branch of IT? Get yourself a nice cup of coffee and find a comfortable chair to sit on – this post will be one of the bigger ones.

Expanding a VMFS partition seems like an easy task – most of the time all we need to do is go to the storage tab of an ESXi host and use the “Increase Capacity” wizard…

Ah, command line. You might love it or hate it, but at the end of the day – there’s nothing you can do really to get around it. Sometimes you just have to use it and no GUI or fancy-dancy wizard will help you out. In my personal opinion, CLI/shell/SSH will always be a superior method of controlling anything in IT…

With VMware vSphere you can migrate a vmdk virtual disk to a different VM retaining Windows NTFS permissions in a very easy way. This allows you to quickly migrate the data from in an event of File Server redesign or emergency failover (i.e. during a cyber attack etc.)

Few days ago, I was doing regular upgrades within one of the vSphere environments I’m responsible for. During these upgrades, I’ve noticed there are some Windows 2008 R2 servers still on vHardware version 10. Obviously, I decided to go ahead and upgrade them too. Little did I know how’s that’s going to end up…