Skip to content

Commit 0344a4d

Browse files
fix typo "yyou"
1 parent 6d7e1c6 commit 0344a4d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/automation-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ In Red Hat Enterprise Linux, the package name to exclude is `redhat-release-serv
3131

3232
When you deploy updates to a Linux machine, you can select update classifications. This option filters the updates that meet the specified criteria. This filter is applied locally on the machine when the update is deployed.
3333

34-
Because Update Management performs update enrichment in the cloud, yyou can flag some updates in Update Management as having a security impact, even though the local machine doesn't have that information. If you apply critical updates to a Linux machine, there might be updates that aren't marked as having a security impact on that machine and therefore aren't applied. However, Update Management might still report that machine as noncompliant because it has additional information about the relevant update.
34+
Because Update Management performs update enrichment in the cloud, you can flag some updates in Update Management as having a security impact, even though the local machine doesn't have that information. If you apply critical updates to a Linux machine, there might be updates that aren't marked as having a security impact on that machine and therefore aren't applied. However, Update Management might still report that machine as noncompliant because it has additional information about the relevant update.
3535

3636
Deploying updates by update classification doesn't work on RTM versions of CentOS. To properly deploy updates for CentOS, select all classifications to make sure updates are applied. For SUSE, selecting ONLY **Other updates** as the classification can cause some additional security updates to be installed if security updates related to zypper (package manager) or its dependencies are required first. This behavior is a limitation of zypper. In some cases, you might be required to rerun the update deployment and then verify the deployment through the update log.
3737

@@ -54,4 +54,4 @@ New-AzAutomationSoftwareUpdateConfiguration -ResourceGroupName $rg -AutomationA
5454
If your question isn't answered here, you can refer to the following sources for additional questions and answers.
5555

5656
- [Azure Automation](https://social.msdn.microsoft.com/Forums/home?forum=azureautomation&filter=alltypes&sort=lastpostdesc)
57-
- [Feedback forum](https://feedback.azure.com/forums/905242-update-management)
57+
- [Feedback forum](https://feedback.azure.com/forums/905242-update-management)

0 commit comments

Comments
 (0)