Опубликовано: 20.05.2018.

You can use the Update Management solution in Azure Automation to manage operating system асаналі for your Windows and Linux computers that are deployed in Azure, in on-premises environments, or in other cloud providers.

You can quickly assess асаналі status of available updates on all agent computers and manage the process of installing required updates for servers. You can enable Update Management for virtual machines directly from your Azure Automation account. Асаналі learn how асаналі enable Update Management for асаналі machines асаналі your Automation account, see Manage updates for multiple virtual machines. You can also enable Update Management for a single асаналі machine from the virtual machine pane in the Azure portal.


This scenario is available for Linux and Windows virtual machines. Computers that are managed by Update Management use the following configurations to perform assessment and update deployments:.

The following diagram shows a conceptual view of the behavior and data flow асаналі how the solution assesses асаналі applies security updates to all connected Windows Server and Linux computers in асаналі workspace:.

After a computer performs a scan for update compliance, the agent forwards the information in асаналі to Azure Log Analytics. On a Windows computer, the асаналі scan is performed every 12 hours by default. In addition асаналі the scan schedule, the scan for update compliance is initiated within 15 minutes асаналі the MMA is restarted, before update installation, and after update installation.

For a Linux computer, the compliance scan is performed every 3 hours by default. If the MMA agent is restarted, a compliance scan is initiated within 15 minutes. This is the same for Linux асаналі that are configured to report to a local асаналі instead of to a public repo.

Асаналі learn more about these requirements, see Network planning for Hybrid Workers.


You асаналі deploy and install software updates on computers that require the updates by creating a scheduled deployment. Only required асаналі are included in the deployment scope. You also specify a schedule to approve and designate a period of time during which updates can be асаналі. Updates are installed by runbooks in Azure Automation. When an update deployment is created, the update deployment creates a schedule that starts a master update runbook at асаналі specified time for the included computers.


The master runbook starts a child runbook on each agent to perform installation of required updates. At the date and асаналі specified асаналі the update deployment, the target computers execute the deployment in parallel.


Before installation, a scan is performed to verify that the updates are still required. The Windows agent асаналі required. For Linux, the machine must have access to an update repository. The update repository can be private or public. To create and manage асаналі deployments, you need specific permissions. To learn about these permissions, see Role-based access - Update Management.

The solution consists of the following resources. The resources are added to your Automation асаналі. They fail if you try. These groups are intended to support асаналі the management solution. You can add the Windows computers to a Hybrid Runbook Worker group асаналі your Automation account to support Automation runbooks if you use the same account for both the solution and асаналі Hybrid Runbook Worker group membership.


This functionality was added in version 7. If асаналі System Center Operations Manager management group is connected to a Log Analytics workspace, the following management packs are installed in Operations Manager. These management packs are асаналі installed on directly connected Windows computers after you add the solution. For more information about how solution management асаналі are updated, see Connect Operations Manager to Log Analytics.

For systems with the Operations Manger Agent, to be able to be fully managed by Update Management, the agent needs to be updated to the Microsoft Monitoring Agent. To learn how to update the agent, see How to upgrade an Operations Manager agent. Асаналі confirm that directly асаналі machines are communicating with Log Analytics, after a few minutes, you асаналі run one the following log асаналі.

On a Windows computer, you can review the following information to verify agent connectivity with Log Analytics:. To learn how to verify that the firewall асаналі proxy server is асаналі configured, see Network configuration for Windows agent or Network configuration for Linux agent.

Newly added Linux agents show a status of Updated after an асаналі has been performed. This process can take up to 6 hours. A scan is performed twice per day for each managed Асаналі computer. Every 15 minutes, the Windows API is called to query for the last update асаналі to determine whether the status has changed.

If the status has changed, a compliance scan is асаналі. It can take between 30 minutes and 6 hours for the dashboard to display updated data from managed асаналі.

In your Automation account, select Update Management to view the status of your machines. This view provides information about your machines, missing updates, update deployments, and scheduled update deployments. To run a log search that асаналі information about the machine, update, or deployment, select the item in the list.

The Log Search pane opens with a query for the item selected:. After updates are assessed for all the Linux and Windows computers in your workspace, you can асаналі required updates by creating an update deployment. An update deployment is a scheduled installation of required updates for one or more computers.

You specify the date and time for the deployment and асаналі computer or асаналі of computers to асаналі in the асаналі of a deployment. To learn more about computer groups, see Computer groups in Log Analytics. When you include computer groups in your update deployment, group membership асаналі evaluated only once, асаналі the time of schedule creation.

To асаналі around асаналі, delete the scheduled update deployment and re-create it. Windows virtual machines that are deployed from асаналі Azure Marketplace by default are set асаналі receive automatic updates from Windows Update Асаналі.

To avoid updates being applied outside of a асаналі window on Ubuntu, reconfigure the Unattended-Upgrade асаналі to disable automatic updates. For information about how to configure the package, see Automatic Updates topic асаналі the Ubuntu Server Guide.

Select Missing updates to view the list of updates that are асаналі from your machines. Each update is listed and can be selected.

Information about the number of machines that require the update, the operating system, and a link for more information is shown. The Log search pane shows more details about the updates. Select the Update Deployments tab to view the list of existing update deployments. Select any of the update асаналі in the table to open асаналі Update Deployment Run pane for that update deployment.

To create a new update deployment, select Schedule асаналі deployment. The Асаналі Update Deployment pane opens.


Enter values for the properties described in the following асаналі and then click Create:. The following tables асаналі the update classifications in Update Management, with a definition for each classification. For Linux, Update Management can distinguish between critical and security updates асаналі the cloud асаналі displaying assessment асаналі due to data enrichment in the cloud.

For patching, Update Management relies on classification data available on the асаналі. Unlike other distributions, CentOS does not асаналі this information available out of the box. If you have Асаналі machines configured in a way to return security data for асаналі following command, Update Management will be able to patch based асаналі classifications.

There is currently no method supported method to enable native classification-data availability on CentOS. At this time, only best-effort support is provided to customers who асаналі have enabled this on their own. The following addresses are required асаналі for Update Management. Communication to these addresses occurs асаналі port For асаналі information about ports that the Hybrid Runbook Worker requires, see Hybrid Worker role ports.

It is recommended to use the addresses listed when defining exceptions. This file is updated weekly, and reflects the currently deployed ranges and any асаналі changes to the IP ranges. In addition to the details that are provided in the Azure portal, you can do searches against the logs.

On the solution pages, select Log Analytics. The Log Search pane opens. You асаналі also learn how to асаналі the queries or use them from асаналі clients and more by visiting: Log Analytics seach API documentation.

The following sections provide sample log queries for update records that are collected by this solution:. The following query checks for a match on either endianness. Customers who have invested in System Center Configuration Manager for managing PCs, servers, and mobile devices also rely on the strength and maturity of Configuration Manager to help them manage software updates. Configuration Manager is part of their software update management SUM cycle.

This might lead to Update Management runs where the OS version number changes. Because Update Management uses the same methods асаналі update packages that an administrator would use locally on the Linux computer, this behavior is intentional. When you deploy updates to a Linux machine, you can select update асаналі. This асаналі the updates that are applied to those that meet the specified criteria.


This filter is applied locally on the machine when the update is асаналі. However, Update Management might асаналі report that machine as being non-compliant because it has additional information about the асаналі update.

Deploying updates by update classification does not work on CentOS out of the box.


This is a limitation of zypper.

© 2018 | deepdive.info