Merge pull request #98502 from MGoedtel/Task4871347

updated doc about agent rights to TMP folder

Author: PRMerger8

articles/automation/automation-dsc-onboarding.md

@@ -1,21 +1,21 @@
 ---
 title: Onboarding machines for management by Azure Automation State Configuration
-description: How to setup machines for management with Azure Automation State Configuration
+description: How to set up machines for management with Azure Automation State Configuration
 services: automation
 ms.service: automation
 ms.subservice: dsc
 author: mgoedtel
 ms.author: magoedte
 ms.topic: conceptual
-ms.date: 08/08/2018
+ms.date: 12/10/2019
 manager: carmonm
 ---
 # Onboarding machines for management by Azure Automation State Configuration
 
 ## Why manage machines with Azure Automation State Configuration?
 
 Azure Automation State Configuration is a configuration management service
-for DSC nodes in any cloud or on-premises datacenter.
+for Desired State Configuration (DSC) nodes in any cloud or on-premises datacenter.
 It enables scalability across thousands of machines quickly and easily from a central, secure location.
 You can easily onboard machines,
 assign them declarative configurations,
@@ -41,10 +41,16 @@ State Configuration can also be used as a report-only endpoint.
 This allows you to set (push) configurations through DSC and view reporting details in Azure Automation.
 
 > [!NOTE]
-> Managing Azure VMs with State Configuration is included at no extra charge if the virtual machine DSC extension installed is greater than 2.70. Refer to the [**Automation pricing page**](https://azure.microsoft.com/pricing/details/automation/) for more details.
+> Managing Azure VMs with State Configuration is included at no extra charge if the virtual machine DSC extension installed is greater than 2.70. For more information, see [**Automation pricing page**](https://azure.microsoft.com/pricing/details/automation/).
 
 The following sections outline how you can onboard each type of machine to Azure Automation State Configuration.
 
+> [!NOTE]
+>Deploying DSC to a Linux node uses the `/tmp` folder and modules like **nxAutomation** are temporarily downloaded for verification before installing them in their appropriate location. To ensure the modules install correctly, the Log Analytics agent for Linux needs read/write permission on `/tmp` folder. The Log Analytics agent for Linux runs as the `omsagent` user. 
+>
+>To grant write permission to `omsagent` user, run the following commands: `setfacl -m u:omsagent:rwx /tmp`
+>
+
 ## Azure virtual machines
 
 Azure Automation State Configuration lets you easily onboard Azure virtual machines for
@@ -75,7 +81,7 @@ Azure virtual machines can be deployed and onboarded to Azure Automation State C
 Azure Resource Manager templates. See [Server managed by Desired State Configuration service](https://azure.microsoft.com/resources/templates/101-automation-configuration/)
 for an example template that onboards an existing VM to Azure Automation State Configuration.
 If you are managing a Virtual Machine Scale Set, see the example template
-[VM Scale Set Configuration managed by Azure Automation](https://azure.microsoft.com/resources/templates/201-vmss-automation-dsc/).
+[Virtual machine scale set Configuration managed by Azure Automation](https://azure.microsoft.com/resources/templates/201-vmss-automation-dsc/).
 
 ### PowerShell
 
@@ -114,7 +120,7 @@ can also be onboarded to Azure Automation State Configuration, as long as they h
    ```
 
 1. If you cannot apply the PowerShell DSC metaconfigurations remotely, copy the metaconfigurations folder from step 2 onto each machine to onboard. Then call **Set-DscLocalConfigurationManager** locally on each machine to onboard.
-1. Using the Azure portal or cmdlets, check that the machines to onboard now show up as State Configuration nodes registered in your Azure Automation account.
+1. Using the Azure portal or cmdlets, check that the machines to onboard appear as State Configuration nodes registered in your Azure Automation account.
 
 ## Physical/virtual Linux machines on-premises, or in a cloud other than Azure
 
@@ -123,7 +129,7 @@ can also be onboarded to Azure Automation State Configuration, as long as they h
 [outbound access to Azure](automation-dsc-overview.md#network-planning):
 
 1. Make sure the latest version of [PowerShell Desired State Configuration for Linux](https://github.com/Microsoft/PowerShell-DSC-for-Linux) is installed on the machines you want to onboard to Azure Automation State Configuration.
-1. If the [PowerShell DSC Local Configuration Manager defaults](/powershell/scripting/dsc/managing-nodes/metaConfig4) match your use case, and you want to onboard machines such that they **both** pull from and report to Azure Automation State Configuration:
+2. If the [PowerShell DSC Local Configuration Manager defaults](/powershell/scripting/dsc/managing-nodes/metaConfig4) match your use case, and you want to onboard machines such that they **both** pull from and report to Azure Automation State Configuration:
 
    - On each Linux machine to onboard to Azure Automation State Configuration, use `Register.py` to onboard using the PowerShell DSC Local Configuration Manager defaults:
 
@@ -133,8 +139,8 @@ can also be onboarded to Azure Automation State Configuration, as long as they h
 
      If the PowerShell DSC Local Configuration Manager defaults **do not** match your use case, or you want to onboard machines such that they only report to Azure Automation State Configuration, follow steps 3 - 6. Otherwise, proceed directly to step 6.
 
-1. Follow the directions in the following [**Generating DSC metaconfigurations**](#generating-dsc-metaconfigurations) section to generate a folder containing the needed DSC metaconfigurations.
-1. Remotely apply the PowerShell DSC metaconfiguration to the machines you want to onboard:
+3. Follow the directions in the following [**Generating DSC metaconfigurations**](#generating-dsc-metaconfigurations) section to generate a folder containing the needed DSC metaconfigurations.
+4. Remotely apply the PowerShell DSC metaconfiguration to the machines you want to onboard:
 
     ```powershell
     $SecurePass = ConvertTo-SecureString -String '<root password>' -AsPlainText -Force
@@ -153,7 +159,7 @@ The machine this command is run from must have the latest version of [WMF 5](htt
 
    `/opt/microsoft/dsc/Scripts/SetDscLocalConfigurationManager.py -configurationmof <path to metaconfiguration file>`
 
-1. Using the Azure portal or cmdlets, check that the machines to onboard now show up as DSC nodes registered in your Azure Automation account.
+2. Using the Azure portal or cmdlets, check that the machines to onboard now show up as DSC nodes registered in your Azure Automation account.
 
 ## Generating DSC metaconfigurations
 
@@ -356,7 +362,7 @@ number of reasons why you may need to re-register that node in the future:
 - To change any [PowerShell DSC Local Configuration Manager values](/powershell/scripting/dsc/managing-nodes/metaConfig4) that were set during initial registration of the node, such as ConfigurationMode. Currently, these DSC agent values can only be changed through re-registration. The one exception is the Node Configuration assigned to the node -- this can be changed in Azure Automation DSC directly.
 
 re-registration can be performed in the same way you registered the node initially, using any of the
-onboarding methods described in this document. You do not need to un-register a node from Azure
+onboarding methods described in this document. You do not need to unregister a node from Azure
 Automation State Configuration before re-registering it.
 
 ## Troubleshooting Azure virtual machine onboarding