Skip to content

Commit 34eb003

Browse files
committed
updated article
1 parent 15f371e commit 34eb003

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

articles/automation/automation-dsc-onboarding.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,13 @@ This allows you to set (push) configurations through DSC and view reporting deta
4545
4646
The following sections outline how you can onboard each type of machine to Azure Automation State Configuration.
4747

48+
> [!NOTE]
49+
>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. Instead of the Log Analytics agent for Linux running as a privileged user - `root`, the agent runs as the `omsagent` user. In most cases, explicit permission need be granted to this user in order for certain files to be read. To grant permission to `omsagent` user, run the following commands:
50+
>
51+
> - Add the `omsagent` user to specific group `sudo usermod -a -G <GROUPNAME> <USERNAME>`
52+
> - Grant write access to the folder `sudo chmod 1777 /tmp`
53+
>
54+
4855
## Azure virtual machines
4956

5057
Azure Automation State Configuration lets you easily onboard Azure virtual machines for
@@ -133,13 +140,8 @@ can also be onboarded to Azure Automation State Configuration, as long as they h
133140

134141
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.
135142

136-
3. Deploying DSC to a node uses the `/tmp` folder, 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. Instead of the Log Analytics agent for Linux running as a privileged user - `root`, the agent runs as the `omsagent` user. In most cases, explicit permission must be granted to this user in order for certain files to be read. To grant permission to omsagent user, run the following commands:
137-
138-
- Add the `omsagent` user to specific group `sudo usermod -a -G <GROUPNAME> <USERNAME>`
139-
- Grant write access to the folder `sudo chmod 1777 /tmp`
140-
141-
4. Follow the directions in the following [**Generating DSC metaconfigurations**](#generating-dsc-metaconfigurations) section to generate a folder containing the needed DSC metaconfigurations.
142-
5. Remotely apply the PowerShell DSC metaconfiguration to the machines you want to onboard:
143+
3. Follow the directions in the following [**Generating DSC metaconfigurations**](#generating-dsc-metaconfigurations) section to generate a folder containing the needed DSC metaconfigurations.
144+
4. Remotely apply the PowerShell DSC metaconfiguration to the machines you want to onboard:
143145

144146
```powershell
145147
$SecurePass = ConvertTo-SecureString -String '<root password>' -AsPlainText -Force

0 commit comments

Comments
 (0)