We’ve now reached the final article in this three part series covering Configuration Management in Azure automation. In Part 1, I discussed the Inventory tool and how to onboard an AWS EC2 virtual machine to Azure. Part 2 covered Change tracking and how to monitor changes to various resources on the AWS instance. In this article, Part 3, I will cover Azure State configuration (DSC) and how to register an AWS VM as a DSC node to apply a desired state.
Let me begin by stating that I am not a programmer or C# expert. I am a System engineer by trade, who has become proficient in Powershell scripting. When I first began working in IT, about 13 years ago, the first programming language that I tried to learn was Perl. At the beginning of that process, I immediately discovered programming is not for me and this relationship will not work. So I dumped Perl after a few “dates” and never looked back. However, that was then. Now, after having worked with Powershell to create scripts to automate tasks, I have developed a renewed interest in coding.
Do you want to know how to get the mailbox count per database on a particular server? Use the following cmdlet to get that information:
Get-Mailbox -Server servername | Group-Object -Property:database | select Name,Count | FT -AutoSize
Remember to change “servername” to the name of your Primary Mailbox server.
Here’s an example of the command output: