This blog series shows you how to quickly import vital components for configuring and scheduling your patches using Beekeeper automation. Last week we looked at how to import data, this week we will demonstrate how to import a schedule for your patches.
When you enter data into Beekeeper Patching Automation, you use the UI to add servers groups, Windows Failover Clusters, and Exchange DAGs. Then, you assign validation tasks to these server groups or clusters. To create the execution job, you assign the server groups or clusters to a schedule. This can be time consuming.
I have created PowerShell scripts to do these tasks. In a series of blog posts, I will share these PowerShell scripts and go over their usage.
The first PowerShell script will export servers from an SCCM collection into a CSV. Then another script will import that CSV to create the appropriate Application groups, Windows Failover Clusters, or Exchange DAGs.
Using a PowerShell validation during any of the Beekeeper Execution Job phases, you can write information to the Windows Application Log. This helps enable discovery for SCOM. The Event Log Validation Pack is a collection of PowerShell validations that you can customize in your environment.
Learn how to implement this, including downloadable Validation Pack and code snippets, in this blog post. For more information about Beekeeper patching automation software, view the product page.
We're releasing version 5.1.0 of our Beekeeper patching automation software this week. Let's take a look at the new features available to make your patch workflow even more efficient.
Unless you’ve been living under a rock or aren’t in the IT field at all, by now you’ve likely heard about the widespread Spectre and Meltdown vulnerabilities affecting an enormous swath of processors manufactured by Intel and AMD, the industry leaders, leading to security vulnerabilities and performance problems.
Green House Data staff have been hard at work patching systems as fixes have come available this week. Here’s a quick summary of the vulnerabilities, their effects on cloud and general computing performance, and what we’ve done to fix them so far. We also provide a few links for users who need to patch their own operating systems or investigate further.
It’s easy to provision additional VMs and increase resource commitment from your overall resource pool using the vSphere web portal. Maybe too easy. If you overstretch your resources, some features like High Availability failover may not function as planned. HA keeps your VMs from failing by pooling VMs and hosts in a cluster, relaunching failed VMs on alternate hosts.
Overcommitting resources can also lead to general performance problems, so it is in your best interest to use Admission Control to keep a close watch on overall capacity. Another reason? You might be trying to power on new VMs, only to run into errors as you exceed your Admission Control rules. Tweaking them can save you from buying additional host resources.
This post will introduce the concepts of slot sizes and configuration of Admission Control to allow more VMs to move between hosts when you have turned on High Availability in vSphere/vCenter.
Looking to improve your workflow and be more efficient when you’re managing virtual machines in the VMware vSphere Web Client? Keyboard shortcuts not only make you look like a wizard when you’re showing someone how to perform an operation, they also make your daily admin life a little bit faster and easier.
While you may be used to the desktop client, the web client also includes some handy features that can help speed up your workflow. Below are some of our most-used keyboard shortcuts and tips for quickly navigating the VMware vSphere web client.