Proxy support for the DSC agent is available in Windows release 1809 and later. Configuration of private networksĬheck Azure Automation Network Configuration for detailed information on the ports, URLs, and other networking details required for nodes on a private network. For nodes running Windows Server 2012 and Windows 7, ![]() Thus it can't be managed by PowerShell DSC or Azure Automation State Configuration.įor nodes running Linux, the DSC Linux extension supports all the Linux distributions listed in the PowerShell DSC documentation. The Microsoft Hyper-V Server standalone product SKU does not contain an implementation of DSC. Operating system requirementsįor nodes running Windows, the following versions are supported: PrerequisitesĬonsider the requirements in this section when using Azure Automation State Configuration. See Forward Azure Automation State Configuration reporting data to Azure Monitor logs. This data to your Log Analytics workspace. ![]() You can configure Azure Automation State Configuration to send Nodes that are managed with Azure Automation State Configuration send detailed reporting status data to the built-in pull server. Import of reporting data into Azure Monitor logs From the Azure portal or from PowerShell, you can manage all your DSC configurations, resources, and target nodes. Management of all your DSC artifactsĪzure Automation State Configuration brings the same management layer to PowerShell Desired State Configuration as it offers for PowerShell scripting. AzureĪutomation can target virtual or physical Windows or Linux machines, in the cloud or on-premises. The built-in pull server in Azure Automation eliminates the need to set up and maintain your own pull server. Target nodes can automatically receiveĬonfigurations, conform to the desired state, and report on their compliance. Built-in pull serverĪzure Automation State Configuration provides a DSC pull server similar to the Windows Feature DSC-Service. In other words, in the same way that Azure Automation helps you manage PowerShell scripts, it also helps you manage DSC configurations. The Azure Automation State Configuration service is to DSC what Azure Automation runbooks are to PowerShell scripting. You can easily enable machines, assign them declarative configurations, and view reports showing each machine's compliance with the desired state you specify. ![]() This service enables scalability across thousands of machines quickly and easily from a central, secure location. Why use Azure Automation State ConfigurationĪzure Automation State Configuration provides several advantages over the use of DSC outside of Azure. For more information, see Automation pricing page. Managing Azure VMs with Azure Automation State Configuration is included at no extra charge if the installed Azure VM Desired State Configuration extension version is greater than 2.70. This feature allows you to set (push) configurations through DSC and view reporting details in Azure Automation. If you aren't ready to manage machine configuration from the cloud, you can use Azure Automation State Configuration as a report-only endpoint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |