This year already started great for me by passing the AZ-102: Microsoft Azure Administrator Certification Transition exam! This transition exam is based on content from the AZ-100 and AZ-101 exams. In this blog post, I will share some tips that really helped me passing the exam.
Because of the recent domain change of my blog, I decided to completely start over again with my lab in Azure. I’ve been working with Desired State Configuration Configs in Azure for quite a few years, but never used them for my own lab environment. It felt a bit overkill to do that, but now I wanted to start over and do everything right.
This step-by-step installation guide explains how to create a DSC Configuration in Azure Automation and how to apply this on your domain controller in Azure.
This article describes the licensing options you have when you want to deploy Windows Server Virtual Machines in Azure. It’s getting complicated when you start using the Hybrid Use Benefit solution, so always contact Microsoft or your licensing supplier. Please note that I will not answer any licensing questions.
Built-in Licensing for Windows Server
This type of licensing is by-far the most easy to use but it can be an expensive solution. You deploy an Azure Virtual Machine from the Portal or PowerShell and the licensing costs are automatically included with the Virtual Machine costs. But what if you want to use your existing KMS licenses which you’ve bought with your Enterprise Agreement? Or you want to use Windows Server Standard licenses instead of Datacenter licenses?
Last Tuesday Avanade announced the new Avanade Azure Stack Solution. Avanade delivers this solution from client site, at remote locations or hosted in Avanade’s own datacenters. Azure Stack is an extension of Azure to on-premises locations. People tend to forget that Azure Stack is not just a replacement of your physical servers running a hypervisor like Hyper-V. It’s a true hybrid cloud solution. You get features like Disaster Recovery with instant fail-over, Platform as a Service (PaaS) capabilities, Load Balancing, the new Portal experience and so on. I’m really excited to tell you more about this great solution.
Some error outputs are not always useful. Especially when they make no sense for the issue you have.
New-AzureRmResourceGroupDeployment : A parameter cannot be found that matches parameter name ‘YOURPARAMETER’
This error occurs because of at least the 2 following issues:
- You didn’t specify a parameter for ‘YOURPARAMETER’ in your JSON template. That’s what the error says. If you forget to specify a parameter with the New-AzureRmResourceGroupDeployment cmdlet, you’ll see a prompt to insert a value for that parameter. But if you add a paremeter like -Name “VM01” to the command while it’s not specified in the JSON template, you’ll see this error.
- The JSON code you provided isn’t valid. Always validate your JSON code. You can use http://www.jsoneditoronline.org/, paste your code and look for the red “X” buttons after a line number.
Did you find another issue where this error occurs? Please let me know in the comments section.
Today I was working on an Azure project where the deployment of Azure resources needed to be automated.
You’ll see the following error message:
In this step-by-step, I’ll show you how to configure PfSense with an Azure Site-to-Site VPN by using a Dynamic Routing Gateway/Route-based Gateway. This even works with a VPN behind a NAT setup. I was looking for a stable solution that could handle the new Route-based (IKE v2) Gateways. This tutorial is based on the new Azure Portal.
- A Hyper-V Host (Windows 10 is fine as well)
- 2 Hyper-V Virtual Networks. One called “External Virtual Network” and one called “Internal Virtual Network”.
- A Hyper-V VM with PfSense installed with NAT configured between the internal and external virtual network. Just download the ISO from the PfSense website and create a Generation 1 VM with it. Give it 512 or 1024 MB RAM and 1 vCPU and follow online installation instructions.