| title | description | keywords | services | ms.subservice | ms.date | ms.topic |
|---|---|---|---|---|---|---|
Create configurations from existing servers for Azure Automation State Configuration |
This article tells how to create configurations from existing servers for Azure Automation State Configuration. |
dsc,powershell,configuration,setup |
automation |
dsc |
08/08/2019 |
conceptual |
Applies To: Windows PowerShell 5.1
Creating configurations from existing servers can be a challenging task. You might not want all settings, just those that you care about. Even then you need to know in what order the settings must be applied in order for the configuration to apply successfully.
Note
This article refers to a solution that is maintained by the Open Source community. Support is only available in the form of GitHub collaboration, not from Microsoft.
A community maintained solution named ReverseDSC has been created to work in this area starting SharePoint.
The solution builds on the SharePointDSC resource and extends it to orchestrate gathering information from existing servers running SharePoint. The latest version has multiple extraction modes to determine what level of information to include.
The result of using the solution is generating Configuration Data to be used with SharePointDSC configuration scripts.
Once the data files have been generated, you can use them with DSC Configuration scripts to generate MOF files and upload the MOF files to Azure Automation. Then register your servers from either on-premises or in Azure to pull configurations.
To try out ReverseDSC, visit the PowerShell Gallery and download the solution or click "Project Site" to view the documentation.
- To understand PowerShell DSC, see Windows PowerShell Desired State Configuration overview.
- Find out about PowerShell DSC resources in DSC Resources.
- For details of Local Configuration Manager configuration, see Configuring the Local Configuration Manager.