![]() The message for this error is provided by the specific exception The message for this error is provided by the specific exception in extension logs Įrror codes and their meanings Error Code The following JSON shows the schema for the settings portion of the DSC Extension in an Azure Resource Manager template. ![]() The DSC extension for Windows requires that the target virtual machine is able to communicate with AzureĪnd the location of the configuration package (.zip file) if it is stored in a location outside of Azure. Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows Client 7/8.1/10 Internet connectivity The DSC Extension supports the following OS's This document details the supported platforms, configurations, and deployment options for the DSC virtual machine extension for Windows. The DSC Extension calls into PowerShell DSC to enact the received DSC configuration on the VM. The extension uploads and applies a PowerShell DSC Configuration on an Azure VM. The PowerShell DSC Extension for Windows is published and supported by Microsoft. Machine configuration also includes hybrid machine support through Arc-enabled servers. The machine configuration feature combines features of the Desired State Configuration (DSC) extension handler, Azure Automation State Configuration, and the most commonly requested features from customer feedback. SourceInfo = "C:\\DSC\\ServiceExample.Before you enable the DSC extension, we would like you to know that a newer version of DSC is now generally available, managed by a feature of Azure Automange named machine configuration. ![]() Install-Module -Name PSDesiredStateConfigurationĭesired State Configuration Overview for EngineersĭSC mofs C:\Windows\System32\ConfigurationĬontents of the mof of MSFT_ServiceResource as $MSFT_ServiceResource1ref Start-DscConfiguration -Path ServiceExample -ComputerName localhost -Wait -Verbose -Force StartupType = "Automatic" # Automatic, Disabled, and Manual Import-DscResource -ModuleName PSDesiredStateConfiguration Make a declarative script > generate mof > apply mof > verify configuration is running Using a DSC script, set service to Automatic and Running, start configuration, and view configuration. Let’s say, you want all client machines to have the same configs for a company application-and maintain those configs in a sort of permanent manner-it’s DSC to the rescue. If the system is out of state, the LCM makes calls to the code in resources to make it so according to the configuration.įor example, you want to make sure a Windows feature is always enabled on your web server, that’s where DSC can help you. The LCM regularly polls the system using the control flow implemented by resources to ensure that the state defined by a configuration is maintained. The Local Configuration Manager (LCM) is the engine by which DSC facilitates the interaction between resources and configurations. Resources reside in PowerShell modules and can be written to model something as generic as a file or a Windows process, or as specific as an IIS server or a VM running in Azure. They contain the code that put and keep the target of a configuration in the specified state. Resources are the make it so part of DSC. What does that mean? That means once the configuration has been started, you no longer have to keep checking on it DSC takes over. DSC configurations are also idempotent (a fancy way of saying static): the Local Configuration Manager (LCM) will continue to ensure that machines are configured in whatever state the configuration declares. Upon running the configuration, DSC (and the resources being called by the configuration) will simply make it so, ensuring that the system exists in the state laid out by the configuration. Scripts, configurations, and resources become solid-state or static, rather than dynamic.Ĭonfigurations are declarative PowerShell scripts which define and configure instances of resources. I’m not sure why Microsoft doesn’t describe it that way, but that’s exactly what it is. What does that mean? Think…group policy, but using PowerShell. DSC, or Desired State Configuration, is a declarative platform in PowerShell that enables you to manage your IT and development infrastructure with configuration as code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |