The PowerShell DSC Package resource can be used to install (and uninstall) software from a machine using DSC. This is a great resource to get software installed, but it does have a slight complication, in that it requires a product ID for the package you are installing. It's understandable why, it uses this to confirm that the particular version of the software is present, but it can be a pain to get this ID.
//Build (henceforth known as just Build) is Microsoft's annual developer conference held last week in San Francisco. As you might expect there were a large amount of announcements, including a lot of Azure ones. Many of the Azure ones where IoT and Analytics focused but there were quite a few IaaS announcements that I am going to summarise here. I'm sure I have missed some, and I won't go into great detail here, expect upcoming
It's quite a common occurence in an Azure Resource Manager template to be creating a storage account and then need the key for that storage account later in the script. For example I have a template that creates a storage account, then a website and then adds an application setting to that website with a connection string for storage.
Previously to do this you could use the following syntax in an ARM template
Azure Resource Manager (ARM), the new V2 method for deploying Azure resources offers a new template based deployment method. Using JSON based templates it is quick and easy to build a repeatable deployment process. If you are just starting out with this new process then the resources below may help with your transition.
When recently deploying a Remote Desktop environment into Azure with ARM and the DSC extension I encountered an issue when I got to calling the xRDSessionDeployment resource to create the new deployment. The deployment would be created OK, but this would then be followed by the machine rebooting 5-10 times before DSC finally generated an error and would not move on to the next task. My DSC extension logs