{"id":1581,"date":"2014-08-07T10:31:00","date_gmt":"2014-08-07T10:31:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2014\/08\/07\/introducing-the-azure-powershell-dsc-desired-state-configuration-extension\/"},"modified":"2024-02-20T13:04:57","modified_gmt":"2024-02-20T21:04:57","slug":"introducing-the-azure-powershell-dsc-desired-state-configuration-extension","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/introducing-the-azure-powershell-dsc-desired-state-configuration-extension\/","title":{"rendered":"Introducing the Azure PowerShell DSC (Desired State Configuration) extension"},"content":{"rendered":"

UPDATE 11\/4\/2014: For information on using PSCredential objects, please refer to this blog post<\/a>.<\/span><\/strong><\/strong><\/p>\n

UPDATE 11\/21\/2014: For information on OS support, and other features, please refer to our release history<\/a><\/span><\/strong>.<\/strong><\/p>\n

For the latest information regarding DSC Extension, refer to the product\u00a0documentation.<\/a><\/p>\n

……….<\/p>\n

Earlier this year Microsoft released the Azure VM Agent and Extensions<\/a> as part of the Windows Azure Infrastructure Services. VM Extensions are software components that extend the VM functionality and simplify various VM management operations; for example, the VMAccess extension can be used to reset a VM\u2019s password, or the Custom Script extension<\/a> can be used to execute a script on the VM.<\/p>\n

Today, we are introducing the PowerShell Desired State Configuration (DSC) Extension for Azure VMs as part of the Azure PowerShell SDK<\/a>.<\/strong> You can use new cmdlets to upload and apply a PowerShell DSC configuration on an Azure VM enabled with the PowerShell DSC extension. PowerShell DSC extension will call into PowerShell DSC to enact the received DSC configuration on the VM.<\/p>\n

If you already have the Azure PowerShell SDK installed, you will need to update to version 0.8.6<\/strong><\/a> or later.<\/p>\n

Once you have installed and configured Azure PowerShell and authenticated to Azure<\/a>, you can use the Get-AzureVMAvailableExtension<\/a> cmdlet to see the PowerShell DSC extension.<\/p>\n

PS C:\\> Get-AzureVMAvailableExtension<\/span> -Publisher<\/span> Microsoft.PowerShell                                                   \r\n                                                                                                                        \r\nPublisher                  : Microsoft.Powershell                                                                       \r\nExtensionName              : DSC                                                                                        \r\nVersion                    : 1.0                                                                                        \r\nPublicConfigurationSchema  :                                                                                            \r\nPrivateConfigurationSchema :                                                                                            \r\nSampleConfig               :                                                                                            \r\nReplicationCompleted       : True                                                                                       \r\nEula                       : http:\/\/azure.microsoft.com\/en-us\/support\/legal\/                                            \r\nPrivacyUri                 : http:\/\/www.microsoft.com\/                                                                  \r\nHomepageUri                : http:\/\/blogs.msdn.com\/b\/powershell\/                                                        \r\nIsJsonExtension            : True                                                                                       \r\n<\/pre>\n
Executing a simple scenario<\/h4>\n
One scenario in which this new extension can be used is the automation of software installation and configuration upon a machine\u2019s initial boot-up.<\/p>\n
As a simple example, let\u2019s say you need to create a new VM and install IIS on it. For this, you would first create a PowerShell script that defines the configuration (NOTE: I saved this script as C:\\examples\\IISInstall.ps1):<\/p>\n
\n\n\n\n
\n
001\n002\n003\n004\n005\n006\n007\n008\n009\n010\n011\n012<\/div>\n<\/td>\n
\n
configuration<\/span>\u00a0<\/span>IISInstall<\/span>\n{<\/span>\n\u00a0\u00a0\u00a0 <\/span>node<\/span>\u00a0<\/span>(<\/span>“localhost”<\/span>)<\/span>\n\u00a0\u00a0\u00a0 <\/span>{<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>WindowsFeature<\/span>\u00a0<\/span>IIS<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>{<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Ensure<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>“Present”<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Name<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>“Web-Server”<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>}<\/span>\n\u00a0\u00a0\u00a0 <\/span>}<\/span>\n}<\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Then you would use Publish-AzureVMDscConfiguration to upload your configuration to Azure storage. Publish-AzureVMDscConfiguration is one of the new cmdlets in the Azure PowerShell SDK. The example below uses all the default values, but later in this post we\u2019ll go over more details of how this works<\/a>.<\/p>\n
PS C:\\> Publish-AzureVMDscConfiguration<\/span> -ConfigurationPath<\/span> C:\\examples\\IISInstall.ps1                                   \r\n<\/pre>\n
This cmdlet creates a ZIP package that follows a predefined format that the PowerShell Desired State Configuration Extension can understand and then uploads it as a blob to Azure storage. The ZIP package in the above example was uploaded to<\/p>\n
https:\/\/examples.blob.core.windows.net\/windows-powershell-dsc\/IISInstall.ps1.zip<\/p>\n
\u201cexamples\u201d in this URI is the name of my default Azure storage account, \u201cwindows-powershell-dsc\u201d is the default storage container used by the cmdlet, and \u201cIISInstall.ps1.zip\u201d is the name of the blob for the file I just published.<\/p>\n
Now my sample configuration is available for VMs to use, so let\u2019s write a script that creates a VM that uses our sample configuration (NOTE: I saved this script as C:\\examples\\example-1.ps1):<\/p>\n
\n\n\n\n
\n
001\n002\n003\n004\n005\n006\n007\n008<\/div>\n<\/td>\n
\n
\n
$vm<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>New-AzureVMConfig<\/span>\u00a0<\/span>-Name<\/span>\u00a0<\/span>“example-1”<\/span>\u00a0<\/span>-InstanceSize<\/span>\u00a0<\/span>Small<\/span>\u00a0<\/span>-ImageName<\/span>\u00a0<\/span>“a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-R2-201407.01-en.us-127GB.vhd”<\/span>\u00a0<\/span><\/p>\n
$vm<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>Add-AzureProvisioningConfig<\/span>\u00a0<\/span>-VM<\/span>\u00a0<\/span>$vm<\/span>\u00a0<\/span>-Windows<\/span>\u00a0<\/span>-AdminUsername<\/span>\u00a0<\/span>“admin_account”<\/span>\u00a0<\/span>-Password<\/span>\u00a0<\/span>“Bull_dog1”<\/span><\/p>\n
$vm<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>Set-AzureVMDSCExtension<\/span>\u00a0<\/span>-VM<\/span>\u00a0<\/span>$vm<\/span>\u00a0<\/span>-ConfigurationArchive<\/span>\u00a0<\/span>“IISInstall.ps1.zip”<\/span>\u00a0<\/span>-ConfigurationName<\/span>\u00a0<\/span>“IISInstall”<\/span>\u00a0<\/span><\/p>\n
New-AzureVM<\/span>\u00a0<\/span>-VM<\/span>\u00a0<\/span>$vm<\/span>\u00a0<\/span>-Location<\/span>\u00a0<\/span>“West US”<\/span>\u00a0<\/span>-ServiceName<\/span>\u00a0<\/span>“example-1-svc”<\/span>\u00a0<\/span>-WaitForBoot<\/span><\/p>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
New-AzureVMConfig, Add-AzureProvisioningConfig, and New-AzureVM are the existing Azure cmdlets used to create a VM. The new kid on the block is Set-AzureVMDscExtension\u00a0\u00a0(line 5 of above example).<\/p>\n
This cmdlet injects a DSC configuration into the VM configuration object ($vm in the example). When the VM machine boots, the Azure VM agent will install the PowerShell DSC Extension, which in turn will download the ZIP package that we published previously (IISInstall.ps1.zip), will execute the \u201cIISInstall\u201d configuration that we included as part of IISInstall.ps1, and then will invoke PowerShell DSC by calling the Start-DscConfiguration cmdlet.<\/p>\n
Now, let\u2019s go ahead and execute the sample script (NOTE: if you get an error telling you that the VM vhd is not available or you don\u2019t have access to it, that likely means that the image referenced on line 1 of the script has been updated, and you will need to find the new image name. You can do so by enumerating the available images with Get-AzureVMImage and picking the image that you wish to use. See Azure SDK documentation for more details on this. In my case, I will use a 2012-R2 machine).<\/p>\n
PS C:\\> C:\\examples\\example-1.ps1<\/span>                                                                                       \r\n                                                                                                                        \r\nOperationDescription          OperationId                             OperationStatus                         \r\n--------------------          -----------                             ---------------                         \r\nNew-AzureVM                   9cfb922d-db5b-cdd0-9c74-1a4e34b91e28    Succeeded                               \r\nNew-AzureVM                   17acca22-c6ff-cb5a-8116-a41ff9764d35    Succeeded                               \r\n                                                                                                                        \r\n<\/pre>\n
Our sample configuration was very simple: it just installed IIS. As a quick verification that it executed properly, we can logon to the VM and verify that IIS is installed by visiting the default web site (http:\/\/localhost<\/a>):<\/p>\n
\"iis\"<\/a><\/p>\n
That is the PowerShell DSC Extension in a nutshell.<\/p>\n
And now for the gory details\u2026<\/p>\n
<\/h4>\n
<\/h4>\n
Publish-AzureVMDscConfiguration<\/h4>\n
As the previous example illustrated, the first step in using the PowerShell Desired State Configuration Extension is publishing. <\/strong><\/em>In this context, publishing is the process of creating a ZIP package that the extension can understand and uploading that package to Azure blob storage. This is accomplished using the Publish-AzureVMDscConfiguration cmdlet.<\/p>\n
Why use a ZIP package for publishing? Publish-AzureVMDscConfiguration will parse your configuration looking for Import-DSCResource statements and will include a copy of the corresponding modules along with the script that contains your configuration. For example, let\u2019s take a look at the ZIP package produced by a configuration that creates an actual website instead of just installing IIS. This new example is the FourthCoffee website, which you may have already seen in other DSC blog posts or demos). The FourthCoffee demo has a dependency on the DSC resource xWebAdministration, which is included in the DSC Resource Kit Wave 5<\/a>.<\/p>\n
(NOTE: I saved this script as C:\\examples\\FourthCoffee.ps1)<\/p>\n
\n\n\n\n
\n
001\n002\n003\n004\n005\n006\n007\n008\n009\n010\n011\n012\n013\n014\n015\n016\n017\n018\n019\n020\n021\n022\n023\n024\n025\n026\n027\n028\n029\n030\n031\n032\n033\n034\n035\n036\n037\n038\n039\n040\n041\n042\n043\n044\n045\n046\n047\n048\n049<\/div>\n<\/td>\n
\n
\n
configuration<\/span>\u00a0<\/span>FourthCoffee<\/span>\n{<\/span>\n\u00a0\u00a0\u00a0 <\/span>Import-DscResource<\/span>\u00a0<\/span>-Module<\/span>\u00a0<\/span>xWebAdministration<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/p>\n
\u00a0\u00a0\u00a0 <\/span># Install the IIS role <\/span>\n\u00a0\u00a0\u00a0 <\/span>WindowsFeature<\/span>\u00a0<\/span>IIS<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>{<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Ensure<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Present”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Name<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Web-Server”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>}<\/span>\u00a0<\/span>\n\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span># Install the ASP .NET 4.5 role <\/span>\n\u00a0\u00a0\u00a0 <\/span>WindowsFeature<\/span>\u00a0<\/span>AspNet45<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>{<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Ensure<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Present”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Name<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Web-Asp-Net45”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>}<\/span>\u00a0<\/span>\n\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span># Stop the default website <\/span>\n\u00a0\u00a0\u00a0 <\/span>xWebsite<\/span>\u00a0<\/span>DefaultSite<\/span>\u00a0 <\/span>\n\u00a0\u00a0\u00a0 <\/span>{<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Ensure<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Present”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Name<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Default Web Site”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>State<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Stopped”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>PhysicalPath<\/span>\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“C:\\inetpub\\wwwroot”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>DependsOn<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“[WindowsFeature]IIS”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>}<\/span>\u00a0<\/span>\n\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span># Copy the website content <\/span>\n\u00a0\u00a0\u00a0 <\/span>File<\/span>\u00a0<\/span>WebContent<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>{<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Ensure<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Present”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>SourcePath<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“C:\\Program Files\\WindowsPowerShell\\Modules\\xWebAdministration\\BakeryWebsite”<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>DestinationPath<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>“C:\\inetpub\\FourthCoffee”<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Recurse<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>$true<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Type<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Directory”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>DependsOn<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“[WindowsFeature]AspNet45”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>}<\/span>\u00a0 <\/span><\/p>\n
\u00a0\u00a0\u00a0 <\/span># Create a new website <\/span>\n\u00a0\u00a0\u00a0 <\/span>xWebsite<\/span>\u00a0<\/span>BakeryWebSite<\/span>\u00a0 <\/span>\n\u00a0\u00a0\u00a0 <\/span>{<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Ensure<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Present”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Name<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“FourthCoffee”<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>State<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“Started”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>PhysicalPath<\/span>\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“C:\\inetpub\\FourthCoffee”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>DependsOn<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>=<\/span>\u00a0<\/span>“[File]WebContent”<\/span>\u00a0<\/span>\n\u00a0\u00a0\u00a0 <\/span>}<\/span>\u00a0<\/span>\n}<\/span><\/p>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
To inspect the ZIP package created by the publish cmdlet I used the -ConfigurationArchivePath parameter, which saves the package to a local file instead of uploading it to Azure storage (NOTE: I typed the command below in two separate lines using the ` character; the >>> characters are PowerShell\u2019s prompt):<\/p>\n
PS C:\\> Publish-AzureVMDscConfiguration<\/span> C:\\examples\\FourthCoffee.ps1 `                                                  \r\n>>> -ConfigurationArchivePath<\/span> C:\\examples\\FourthCoffee.ps1.zip<\/pre>\n
When I look at the ZIP package using the File Explorer I can see that it contains my configuration script and a copy of the xWebAdministration module:<\/p>\n
\"FourthCoffee.ps1.zip\"<\/a><\/p>\n
That copy comes from the xWebAdministration module that I already installed on my machine under \u201cC:\\Program Files\\WindowsPowerShell\\Modules\u201d. The publish cmdlet requires that the imported modules are installed on your machine, and that they are located somewhere in $PSModulePath.<\/p>\n
(NOTE: To simplify the example, I slightly altered the xWebAdministration module so it included the files needed for the website as part of the xWebAdministration module, in the \u201cBakeryWebsite\u201d directory)<\/p>\n
\"xWebAdministration\"<\/a><\/p>\n
The two previous examples use a PowerShell Script file (.ps1) to define the configuration that will be published. You can also do this in a PowerShell Module file (.psm1), or if the configuration you want to publish is part of a larger module, you can create the ZIP package manually and simply copy the directories for the module that defines your configuration and any modules referenced by your configuration. For example, if the configuration of our example was defined within a PowerShell module named FourthCoffee the ZIP package would include these two directories: the FourthCoffee module folder, and the dependent DSC resource module folder for xWebAdministration<\/p>\n
\"fourth<\/a><\/p>\n
Once you have a local ZIP package (either created manually, or using the publish cmdlet), you can upload it to Azure storage with the publish cmdlet:<\/p>\n
PS C:\\> Publish-AzureVMDscConfiguration<\/span> C:\\examples\\FourthCoffee.ps1.zip<\/pre>\n
ContainerName and StorageContext parameters<\/h5>\n
By default Publish-AzureVMDscConfiguration will upload the ZIP package to Azure blob storage using \u201cwindows-powershell-dsc\u201d as the container and picking up the default storage account from the settings of your Azure subscription.<\/p>\n
You can change the container using the \u2013ContainerName parameter:<\/p>\n
PS C:\\> Publish-AzureVMDscConfiguration<\/span> C:\\examples\\FourthCoffee.ps1.zip `                                              \r\n>>> -ContainerName<\/span> mycontainer<\/pre>\n
And you can change the storage account (and authentication settings) using the \u2013StorageContext parameter (you can use the New-AzureStorageContext<\/a> cmdlet to create the storage context).<\/p>\n
Set-AzureVMDSCExtension<\/h4>\n
Once a configuration has been published, you can apply it to any Azure virtual machine using the Set-AzureVMDSCExtension cmdlet. This cmdlet injects the settings needed by the PowerShell DSC extension into a VM configuration object, which can then be applied to a new VM, as in our first example, or to an existing VM. Let\u2019s use this cmdlet again to update the VM we created previously (NOTE: the first example used the configuration defined in C:\\examples\\IISInstall.ps1; now we will update this machine with the configuration defined in C:\\examples\\FourthCoffee.ps1; the script that we will use was saved as C:\\examples\\example-2.ps1. Also note that this example uses Update-AzureVM instead of New-AzureVM because we are applying the extension to a VM that already exists.)<\/p>\n
\n\n\n\n
\n
001\n002\n003\n004\n005\n006<\/div>\n<\/td>\n
\n
\n
$vm<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>Get-AzureVM<\/span>\u00a0<\/span>-Name<\/span>\u00a0<\/span>“example-1”<\/span>\u00a0<\/span>-ServiceName<\/span>\u00a0<\/span>“example-1-svc”<\/span><\/p>\n
$vm<\/span>\u00a0<\/span>=<\/span>\u00a0<\/span>Set-AzureVMDSCExtension<\/span>\u00a0<\/span>-VM<\/span>\u00a0<\/span>$vm<\/span>\u00a0<\/span>-ConfigurationArchive<\/span>\u00a0<\/span>“FourthCoffee.ps1.zip”<\/span>\u00a0<\/span>-ConfigurationName<\/span>\u00a0<\/span>“FourthCoffee”<\/span>\u00a0<\/span><\/p>\n
$vm<\/span>\u00a0<\/span>|<\/span>\u00a0<\/span>Update-AzureVM<\/span><\/p>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
PS C:\\> C:\\examples\\example-2.ps1<\/span>                                                                                       \r\n                                                                                                                        \r\nOperationDescription              OperationId                             OperationStatus                         \r\n--------------------              -----------                             ---------------                         \r\nUpdate-AzureVM                    afa38e1a-5717-cac6-a6e7-6f72d0af51d2    Succeeded<\/pre>\n
In our first example we were working with a new VM, so the Azure VM agent first installed the PowerShell DSC Extension and then it invoked it using the information provided by the Set-AzureVMDSCExtension cmdlet. In this second example we are working on an existing VM on which the extension is already installed so the Azure VM agent will skip the installation part and just invoke the PowerShell DSC Extension with the new information provided by the set cmdlet.<\/p>\n
The extension will then<\/p>\n