One day, any virtual infrastructure needs to be updated. That may be just due to admin’s wish to keep up with modern trends or the need for some cool features that are brought to life with the latest updates. And, speaking of updates, VMware has recently released their vSphere 6.5 U2. Find out more details about it in this document: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-feature-comparison-datasheet.pdf So, being a VMware fan, I decided to update my vSphere 6.5 and describe the entire update process from its planning through the installation itself.

In my today’s topic, I discuss why PowerShell behaves like that. Specifically, I shed light on why you cannot run scripts or access a computer on a different domain. Also, I’ll take a closer look at how some cmdlets work.

Sometimes, guys running home labs do not have licenses for Remote Desktop Services (RDS). Well, that’s not a big deal, you know, because Microsoft provides the 120-day grace period for the platform! However, one day the time runs out and RDS server breaks all the client connections. That day, admins are to choose between reinstalling the server and cheating a bit to reset the 120-day RDS grace period.

Some time ago, while looking through what SQL server Basic Availability Groups (BAG) can do, I found an awesome article by Pieter Vanhove: https://blogs.technet.microsoft.com/msftpietervanhove/2017/03/14/top-5-questions-about-basic-availability-groups/. There was nothing about performance, though, so I thought: “Hey, why not write an article about BAG performance?” Later, I realized that you need to compare this performance to something else, right? So, I decided to add SQL Server Failover Cluster Instance (FCI) performance measurements. Maybe, I’ll add some SQL Server Availability Groups (AG) measurements at the end; but, let’s see first whether SQL Server FCI can run twice as fast as SQL Server BAG. In this study, I measured BAG performance alone. Now, as we know the scope of the article, let’s move on!

In this article, I’d like to compare results of the previous two and find out whether SQL Failover Cluster Instance (FCI) can provide you two times higher performance than SQL Server Basic Availability Groups (BAG).

There was a race to bring NVMe-oF to Windows some time ago. Many tried, but I know that only StarWind and Chelsio succeeded so far. Now, it’s time to see who won this race! It is the fourth part of my NVMe-oF Initiators’ performance study. Before, I tested NVMe-oF initiators developed by Linux, Chelsio and StarWind. Here, the battle ends: which NVMe-oF initiator delivers the highest performance and which one Windows admins should use

Well, hyperconvergence is certainly a good deal but there are certain factors to consider when choosing a hyper-converged vendor. Support is a number one thing you should be looking for. Basically, decent support increases chances that your production remains operational all the time or at least minimizes the downtimes. Unified management is the “core” of hyperconvergence, so make sure you won’t need any additional software for administrating your hyper-converged infrastructure. Finally, the price. Take your time and calculate if you’re not overpaying just for a vendor’s “logo”. So, there is a wide variety of hyper-converged appliances, but I hope these three simple factors will help you with choosing a vendor that will provide you with the one that will serve you faithfully.

From day to day, admins troubleshoot issues remotely. And, pretty often, they cannot count on another guy who helps them to enable Remote Desktop (RD) on the remote host. There may also be the case when you loose the access to RD on another computer for some reason, and there’s no one in the remote office who can help you. Whatever, I hope you got the point. What do you need to do? Sure, you can just ask a fellow admin to enable RD on the remote host and wait a bit, but what if that’s something really urgent and you are to fix that issue in the middle of the night? Let’s think through what you can do in that case.

Recently, I decided to automate some boring routine procedures related to setting up virtual networks in ESXi 6.5. That’s right, I’m talking about PowerCLI. This command-line tools allows automating all aspects of vSphere management, including network, storage, VM and so on and so forth. Sure, I had to dig into the details of orchestrating ESXi with PowerCLI. Yep, it took me some time but at the end of the day, the knowledge and experience I acquired paid back! Apparently, this case is not unique, so I decided to share my experience in today’s scribbling.