1. Главная
  2. Фут Фетиш


Ыучбсщь can use the Update Management solution in Azure Automation to manage operating system updates for your Windows and Ыучбсщь computers that are deployed in Azure, in on-premises environments, or in other cloud providers. You can quickly assess the status of available ыучбсщь on all agent computers and manage the process of installing required updates for servers. You can enable Update Management for ыучбсщь machines directly from your Azure Automation account.

To learn how to enable Update Management for virtual machines ыучбсщь your Automation account, see Manage updates for multiple virtual machines.

You ыучбсщь also enable Update Management for a single virtual machine from the virtual ыучбсщь pane in the Azure portal. This ыучбсщь 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 with how the solution assesses and applies security updates to all connected Windows Ыучбсщь and Linux computers in a workspace:.

After a computer performs a scan for update compliance, the agent forwards the information in bulk to Azure Log Analytics.


On a Windows computer, the compliance scan is performed every 12 ыучбсщь by default. In addition to the scan ыучбсщь, the scan for update compliance is initiated within 15 minutes if the MMA is restarted, before update installation, and after update installation.

For a Linux computer, the compliance scan is performed every 3 hours ыучбсщь default.


Ыучбсщь the MMA agent is restarted, a ыучбсщь scan is initiated within 15 minutes. This is the same for Linux computers that are configured to report to a local repo instead of to a public repo.

To learn ыучбсщь about these requirements, see Network planning for Hybrid Workers. You can deploy and install software updates on computers that require the updates by creating a scheduled ыучбсщь.

Only required ыучбсщь are included in the deployment scope. You ыучбсщь specify a schedule ыучбсщь approve and designate a period of time during which updates can be installed. Updates are installed ыучбсщь runbooks in Azure Automation. When an update deployment is created, the update deployment creates a schedule that starts a master update runbook at the 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 ыучбсщь time specified in the update deployment, the target computers execute the deployment in parallel. Before installation, a ыучбсщь is performed to verify that the updates are still required.


Ыучбсщь Windows agent is required. For Linux, ыучбсщь machine must have access to an update repository. The update ыучбсщь can be private or public. Ыучбсщь create and manage update deployments, you need specific permissions. Ыучбсщь learn about these permissions, see Role-based access - Update Management. The solution consists of the following resources.

The resources are added to your Automation account. They fail if you try. These ыучбсщь are intended to support only the management solution. You can add the Windows computers to a Hybrid Runbook Worker group in your Automation account to ыучбсщь Automation runbooks if you use the same account for ыучбсщь the solution and the Hybrid Runbook Worker group membership.

This functionality ыучбсщь added in version 7. If your 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 also installed on directly ыучбсщь Windows computers after you add the solution. For more information about how solution management packs ыучбсщь 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.

Ыучбсщь learn how to update the agent, see How to ыучбсщь an Operations Manager agent. To confirm that directly connected machines are communicating with Log Analytics, ыучбсщь a few minutes, you can run one the following log searches. On a Windows computer, you can review the following ыучбсщь to ыучбсщь agent connectivity with Log Analytics:.

Ыучбсщь learn ыучбсщь to verify that the firewall or proxy server is properly configured, see Network ыучбсщь for Windows agent or Network configuration for Ыучбсщь agent. Newly added Linux agents show a status of Updated after an assessment has been performed.

This ыучбсщь can take up to 6 hours. A scan is performed twice per day for each managed Windows computer. Every 15 minutes, the Windows API is called to query for the last update time to determine whether the status has changed. If the status has changed, a compliance scan is initiated. It ыучбсщь 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 ыучбсщь provides information about your machines, missing updates, update deployments, and scheduled update deployments. To run a log ыучбсщь that returns 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 ыучбсщь in your workspace, you can install required updates by creating an update deployment. An update deployment is a scheduled ыучбсщь of required updates for one or more ыучбсщь. You specify the date and time for the deployment and ыучбсщь computer or group of ыучбсщь to include in the scope 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 is evaluated only once, at the time of schedule creation.


To work around this, delete the scheduled update deployment and re-create it. Windows virtual machines that are deployed ыучбсщь the Azure Marketplace by default are set to receive automatic updates from Windows Update Service. Ыучбсщь avoid updates being applied outside of a maintenance window on Ubuntu, reconfigure the Unattended-Upgrade package to disable automatic updates. For information about how to configure the package, see Automatic Ыучбсщь topic in the Ubuntu Server Guide.

Select Missing updates to view ыучбсщь list of updates that are missing from your machines.


ыучбсщь Each update is listed and can be selected. Information about the ыучбсщь of machines ыучбсщь 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 ыучбсщь update deployments in the table to open the Update Deployment Run pane for that update deployment. To create a new update deployment, select Schedule update deployment.

The New Update Deployment pane opens. Enter values for ыучбсщь properties described in the following table and then click Create:.

The following tables list the update ыучбсщь in Update Management, with a definition for each classification. For Linux, Update Management can distinguish between critical and security updates in the cloud while ыучбсщь assessment data due to data enrichment in the ыучбсщь.

For patching, Update Management relies on classification data available on the machine. Unlike other distributions, CentOS does not ыучбсщь this information available out of the box.

Ыучбсщь you have CentOS machines configured ыучбсщь a ыучбсщь to return security data for the following command, Update Management will be able to patch based on classifications.

There is currently no method supported method ыучбсщь enable native classification-data availability on CentOS. At this time, only best-effort support is provided to customers who may have enabled this on their own. The following addresses are required specifically for Update Management.


Communication to these addresses occurs over port For more 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 ыучбсщь, and reflects the currently deployed ranges and any upcoming changes to the IP ranges. In addition to the details that ыучбсщь provided in the Azure portal, you can do searches against the ыучбсщь. On the solution pages, select Log Analytics.

The Log Search pane opens. You can also learn how to customize the queries or use them from different clients and more by visiting: Log Analytics seach API documentation. Ыучбсщь following sections provide sample log queries for update records ыучбсщь are collected by this solution:. The following query checks for a match on either endianness. Ыучбсщь who have invested in System Center Configuration Manager for managing PCs, servers, and mobile devices also ыучбсщь 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 Ыучбсщь version number changes. Because Update Management uses the same methods to 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 classifications. This ыучбсщь the updates that are applied ыучбсщь those that meet the specified criteria.


This filter is applied locally on the machine when the update is deployed. Ыучбсщь, Update Management might still report that machine as being non-compliant because it has additional information about ыучбсщь relevant update.


Ыучбсщь updates by update classification does not work on CentOS out of the box. This is ыучбсщь limitation of zypper.

Похожее видео:

© 2018