You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> This article refers to a solution that is maintained by the Open Source community. Support is only available in the form of GitHub collaboration, and not from Microsoft.
> The 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.
20
+
> The article refers to a solution that is maintained by the Open Source community. Support is only
21
+
> available in the form of GitHub collaboration, not from Microsoft.
21
22
22
-
This article explains how to create configuration from existing servers for an Azure Automation state configuration. To create configurations from an existing servers is a challenging task as you need to know the right settings and the order they must be applied to ensure that configuration is successful.
23
+
This article explains how to create configuration from existing servers for an Azure Automation
24
+
state configuration. Creating configurations from an existing server is a challenging task. You need
25
+
to know the right settings and the order to apply them to ensure that the configuration is
26
+
successful.
23
27
24
28
## Community project: ReverseDSC
25
29
26
-
The [ReverseDSC](https://github.com/microsoft/reversedsc) is a community maintained solution created to work in this area beginning with the SharePoint. The solution builds on the [SharePointDSC resource](https://github.com/powershell/sharepointdsc) and extends it to orchestrate by [gathering information](https://github.com/Microsoft/sharepointDSC.reverse#how-to-use) from existing servers running SharePoint.
27
-
28
-
The latest version has multiple [extraction modes](https://github.com/Microsoft/SharePointDSC.Reverse/wiki/Extraction-Modes) to determine the level of information to include. The result of using the solution is generating
29
-
[Configuration Data](https://github.com/Microsoft/sharepointDSC.reverse#configuration-data) that must be used with SharePointDSC configuration scripts.
30
+
The [ReverseDSC][07] is a community maintained solution created to work in this area beginning with
31
+
the SharePoint. The solution builds on the [SharePointDSC resource][12] and extends it to
32
+
orchestrate by [gathering information][11] from existing servers running SharePoint.
30
33
34
+
The latest version has multiple [extraction modes][09] to determine the level of information to
35
+
include. The result of using the solution is generating [Configuration Data][10] that must be used
36
+
with SharePointDSC configuration scripts.
31
37
32
38
## Create configuration from existing servers for an Azure Automation state configuration
33
39
34
-
Follow the steps to create a configuration from existing servers for an Azure Automation state configuration:
40
+
Use the following steps to create a configuration from existing servers:
35
41
36
-
1. After you generate the data files, you can use them with [DSC Configuration scripts](/powershell/dsc/overview) to generate *MOF* files.
37
-
1. upload the [MOF files to Azure Automation](./tutorial-configure-servers-desired-state.md#create-and-upload-a-configuration-to-azure-automation).
38
-
1. Register your servers from either [on-premises](./automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines)
39
-
or [in Azure](./automation-dsc-onboarding.md#enable-azure-vms) to pull configurations.
42
+
1. After you generate the data files, use the files with [DSC Configuration scripts][05] to generate
43
+
**MOF** files.
44
+
1. Upload the [MOF files to Azure Automation][03].
45
+
1. To pull the configurations, register your servers from either [on-premises][02] or
46
+
[in Azure][01].
40
47
41
-
For more information on ReverseDSC, visit the [PowerShell Gallery](https://www.powershellgallery.com/packages/ReverseDSC/) and download the solution or select **Project Site** to view the [documentation](https://github.com/Microsoft/sharepointDSC.reverse).
48
+
For more information on ReverseDSC, visit the [PowerShell Gallery][13] and download the solution or
49
+
select **Project Site** to view the [documentation][08].
42
50
43
51
## Next steps
44
52
45
-
- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview](/powershell/dsc/overview).
46
-
- Find out about PowerShell DSC resources in [DSC Resources](/powershell/dsc/resources/resources).
47
-
- For details of Local Configuration Manager configuration, see [Configuring the Local Configuration Manager](/powershell/dsc/managing-nodes/metaconfig).
53
+
- To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration overview][05].
54
+
- To find PowerShell DSC resources, see [DSC Resources][06].
55
+
- For details of Local Configuration Manager configuration, see
56
+
[Configuring the Local Configuration Manager][04].
Azure Automation State Configuration retains node status data for 30 days. You can send node status data to [Azure Monitor Logs](/azure/azure-monitor/logs/data-platform-logs) if you prefer to retain this data for a longer period. Compliance status is visible in the Azure portal or with PowerShell, for nodes and for individual DSC resources in node configurations.
The Azure Desired State Configuration (DSC) VM [extension](/azure/virtual-machines/extensions/dsc-overview) is updated as-needed to support enhancements and new capabilities delivered by Azure, Windows Server, and the Windows Management Framework (WMF) that includes Windows PowerShell.
0 commit comments