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.
In my previous post PowerShell Profiles – The profile.ps1 file I showed you my profile.ps1 file. In this post, I’ll show you a way to structure your base file, so that you can use it for your functions and aliases. Make sure that you always use max 2 files. 1The first file is your profile.ps1 file and the other file is this _PSH_BASE.ps1 file. If you use like 3 or 4 files, it can take a couple of seconds to load your PowerShell session.
Continue reading “PowerShell Profiles – The structure of your _PSH_BASE.ps1 file”
Welcome to this blog series about PowerShell profiles. I’m using PowerShell profiles for a couple of months now to make life a lot easier. To start this blog series, I would like to show you my Profile.ps1 file. It’s located in “C:\Users\<Your username>\Documents\WindowsPowerShell”. Because I use my PowerShell profiles at multiple locations such as my work notebook, home computer and sometimes at projects, I need to make sure that my PowerShell script home is always right so that the rest of the PowerShell profile is able to load successfully. That’s why I have these commands at the beginning of my profile:
Continue reading “PowerShell Profiles – The profile.ps1 file”
I had an issue within my lab with deploying Windows 8.1 drivers to Windows 10 with SCCM 2012 R2 SP1. It isn’t possible to make all Windows 8.1 drivers compatible with Windows 10 within the SCCM 2012 R2 SP1 console with just one click. Because I was running within a lab environment and I only had 2 driver packages for Windows 8.1 x64, I was able to make the drivers available for deployment to all platforms. You can do this with the magic of PowerShell:
Continue reading “SCCM 2012 R2 SP1 – Make Windows 8.1 drivers supported on Windows 10 with PowerShell”
I was looking for a way to deploy and automatically domain join a VM in Azure. The solution was quite simple: Azure Automation. I found the blog post of DexterPOSH very useful, but the script doesn’t work for me. Follow the steps on his blog and use this script below. I’ll update this post if I find some improvements. Don’t forget to update the domain in the Add-Computer part.
Continue reading “Azure – Deploy and automatically domain join a VM with Azure Automation Runbooks”
I was looking for a way to automatically deploy a VM in Azure. The solution was quite simple: Azure Automation. I found the blog post of DexterPOSH very useful, but the script doesn’t work for me. Follow the steps on his blog and use this script below. I’ll update this post if I find some improvements.
Continue reading “Azure – Automatically deploy a VM in Azure (Runbook)”
I have an Intel NUC with 8 GB as media center and Hyper-V host for a test domain controller. I attached 2 physical external disks (1x 2,5″ USB 3, 1x 3,5″ USB 2) and created a storage pool. A couple of weeks later, I bought a new 2,5″ USB 3 disk with 1 TB to replace the older USB 2.0 disk. That disk is a lot quieter than the older one.
Continue reading “Windows Storage Spaces – Remove physical disk from storage pool with PowerShell”