Today the version 1.3.0 of AzureRM module was released and in that there was a new cmdlet Export-AzureRMResourceGroup that can be used on an resource group and get a json file from that!
updating your AzureRM is quite easy with the powershell gallery repository
And then you can run the Export cmdlet and get the json file from that deployment and start playing in Visual Studio or VS Code 🙂
Have fun automating and deploying with Azure Resource Manager!
I was testing some xAzure DSC configuration stuff on my Windows Server 2016 TP4 and noticed that when I was trying to use the resource it said that duplicate modules was found but I could not find any in the powershell module libraries and thus it ought to be something else,
I found the tweet that Ben Gelens sent pointing me to the $env:psmodulepath
So looking in my psmodulepath I could see that I had two records that was the same and that had to be fixed,
So to remove the duplicate I first remove both and then add the one again:
During last week I was working on some bare metal deployment on some Hyper-V hosts with System Center VMM. We had deployed them before using legacy boot but now we had updated the BIOS to latest version and got into some trouble.. Maybe it was because of the HPE instead of the HP 😉
During the deployment the WinPE got an error and could not connect to the VMM server,
We tried to update NIC drivers and stuff on the WinPE image but that did not help. During the testing we started the server and configured it to boot with EFI instead of legacy boot and olala it worked to connect to the VMM server but thus as the Hyper-V VHD was MBR we got the following error:
The easiest way I could think of right there and then was to create my new GPT based VHD to boot the Hyper-V host with a powershell convert script from the original MBR vhd. The script required to be run on a Hyper-V host so I connected to one of the Hyper-V nodes in the test cluster and ran the script on a patched VM that was sysprepped:
And once that was done I had to update the Physical profile to set the disk to GPT instead of MBR:
I was exploring last week how I could add a managed windows node in my internal test environment where I have a chef server.
Bootstrap a windows node has been possible quite a while but not so long ago the knife windows added the parameter for also setting up the client as a service. This was part of the Knife Windows 1.0 release as you can read on the Chef site.
Another great parameter now available is the –msi_url that gives the possibility to set the chef client msi path to something local if the servers cannot speak to the mighty Internet
