We have received requests to see more detail around what is happening while Beekeeper applies patches for devices. We have built a PowerShell script to query Beekeeper and the patched devices to display what is going on within Beekeeper and show the progress on individual patches.
To execute the script, you can run it on the Beekeeper server. Learn how below.
Before using Beekeeper for your patching cycle for Exchange DAGs, you should make sure the servers are healthy and ready to be patched. We have developed a script to assist you.
We return to our ongoing series on Beekeeper patching automation software penned by Beekeeper Product Manager John Hann. This entry describes how to link validation tasks to your various Application Groups, Failover Clusters, and Exchange DAGs.
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.