Azure PowerShell DSC Extension v1.8/v1.9 released
UPDATE 04/29/2015: We found an issue during install in ARM deployments. A fix is available as v1.9.
NOTE: You can find more information on the DSC Extension in our release history.
Today we are releasing version 1.8 of the Azure DSC Extension, updated with the latest WMF 5.0 Preview (April 2015).
With this update we are adding support for Windows Server 2008 R2 SP1. Please feel free to give it a try and give us your feedback using Connect: https://connect.microsoft.com/PowerShell/Feedback.
Windows Server 2012 and 2012 R2 are also supported.
Note that, as in previous versions of the Extension, the install process will reboot the VM, once on Server 2012 and 2012R2, and twice on Server 2008 R2 SP1. Also, installing on Server 2008 R2 SP1 can be a little slow because there are several components that need to be updated, typically 30 to 40 min (these estimates include the time it takes to create the VM).
NOTE: If you are upgrading from a previous version of the extension, you may see this error during the upgrade:
“An error occurred downloading the Azure Blob: Exception calling “DownloadFile” with “2” argument(s): “The remote server returned an error: (403) Forbidden.” The Set-AzureVMDscExtension cmdlet grants access to the blobs only for 1 hour; have you exceeded that interval?”
This is a known issue in upgrade. The extension will try to re-apply the previous configuration and fail.
If your previous metaconfiguration included ApplyAndAutoCorrect or ApplyAndMonitor then you will need to re-apply your configuration manually after the update. Otherwise it is safe to ignore this error.
The reason you may need to reapply your configuration is that this update of the extension also updates WMF. Updating WMF does not guarantee that ApplyAndAutoCorrect or ApplyAndMonitor will be enforced across the update.