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
Copy file name to clipboardExpand all lines: articles/automation/automation-dsc-getting-started.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,17 +186,17 @@ account in the **Nodes** tab of the State configuration (DSC) page.
186
186
187
187
### DSC nodes status values
188
188
189
-
The DSC node can take six different values.
189
+
The DSC node can take six different values as follows:
190
190
191
-
- **Failed** - This status appears when an error occurs when applying one or more configuration on a node.
192
-
- **Not complaint** - This status appears when drift occurs on a node.This must be reviewed more closely if systematic.
193
-
- **Unresponsive** - This status appears when node has not been checked in for more than 24 hours.
194
-
- **Pending** - This status appears when a node has a new configuration to apply and pull server is awaiting node check in.
195
-
- **In-progress** - This status appears when a node applies configuration and the pull server is awaiting status.
196
-
- **Compliant** - This status appears when a node has a valid configuration and no drift occurs presently.
191
+
- **Failed** - This status appears when an error occurs when applying one or more configurations on a node.
192
+
- **Not complaint** - This status appears when drift occurs on a node and it requires a close review if it is systematic.
193
+
- **Unresponsive** - This status appears when a node has not been checked in for more than 24 hours.
194
+
- **Pending** - This status appears when a node has a new configuration to apply and the pull server is awaiting node check in.
195
+
- **In-progress** - This status appears when a node applies configuration, and the pull server is awaiting status.
196
+
- **Compliant** - This status appears when a node has a valid configuration, and no drift occurs presently.
197
197
198
198
>[!NOTE]
199
-
>- Node will be marked as **Unresponsive** if the node does not contact the agent service for 1440 minutes (1 Day). If the user uses a value > 1440, the node will be shown **Unresponsive** and gives false status of the nodes.
199
+
>- Node will be marked as **Unresponsive** if the node does not contact the agent service for 1440 minutes (1 Day). If you use a value > 1440, the node is shown **Unresponsive** and gives a false status of the nodes.
200
200
>- **RefreshFrequencyMins** and **ConfigurationModeFrequencyMins** - The frequency of node contacting the agent service is defined using these two different values provided as part of onboarding to DSC. These take a maximum value of 10080 minutes.
0 commit comments