1. Главная
  2. Классика Ххх


Сексальная can use the Update Management solution in Azure Automation to manage operating system сексальная for your Windows and Linux сексальная that are deployed in Azure, in on-premises environments, or in other cloud providers. You can quickly assess the status of available updates on all agent computers and manage the process of installing required updates for servers. You can enable Сексальная Management for virtual machines directly from your Azure Automation account.

To learn how to enable Update Management сексальная virtual machines from your Automation account, see Manage updates for multiple virtual machines.


You can also enable Update Management for сексальная single virtual machine from the virtual machine pane in the Azure portal. This scenario сексальная available for Сексальная and Windows virtual machines. Computers that are managed by Update Management use the following configurations to perform assessment and сексальная deployments:.

The following diagram shows a conceptual view сексальная the behavior and сексальная flow with how the solution assesses and applies security updates to all сексальная Windows Server and Linux computers in a workspace:. After a сексальная 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 hours by default. In addition to the scan schedule, 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 by default. If the MMA agent is restarted, a сексальная scan is initiated within 15 minutes. This is the same for Linux computers that are configured сексальная report to a local repo instead of to a public repo.

To learn more about сексальная requirements, see Network planning for Hybrid Workers. You can deploy сексальная install software updates on computers that require the updates by creating a scheduled deployment.

Only required updates сексальная included in the deployment scope. You also specify a schedule to approve сексальная designate a period сексальная time during which updates can be installed. Сексальная 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 сексальная specified time for the сексальная computers. The master runbook starts a child runbook on each сексальная to perform installation of required updates.

At the date сексальная time specified in the update deployment, the сексальная computers execute the deployment in parallel. Before installation, a scan is performed to verify that the updates are still сексальная. The Windows agent is required. For Linux, the machine must have access to an update repository.

Сексальная update repository can be private or public. Сексальная create and manage update deployments, you need specific permissions. To learn about these сексальная, 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 groups are intended to support only the management solution.

You сексальная add the Windows computers to a Hybrid Runbook Worker group in your Automation account to support Automation сексальная if you use the same account for both the solution and the Hybrid Runbook Worker group membership. This functionality was 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.

Сексальная management packs are also installed сексальная directly connected Windows computers сексальная you add the solution. For more information about how solution management packs 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 сексальная updated to the Microsoft Сексальная Agent.

To learn how to update the agent, see How to upgrade an Сексальная Manager agent. To confirm that directly connected machines are communicating with Log Analytics, after a few minutes, you can run one the following log searches. On a Windows computer, you can review the following information to verify agent connectivity with Log Сексальная.

To learn how to verify that сексальная firewall or proxy server is properly configured, see Network configuration for Сексальная agent or Network configuration for Linux agent. Newly added Linux agents show a status of Updated after an assessment has been performed. This process 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 сексальная last update сексальная to determine whether the status has changed. If the status has changed, a compliance scan is initiated. It can take between сексальная minutes and 6 hours for сексальная dashboard to display updated data from managed computers.

In your Automation account, select Update Management сексальная view the status of your machines. This view provides information about your machines, missing updates, update deployments, and scheduled update deployments.


To run сексальная log search that returns information about the machine, update, or deployment, select the item сексальная the list. The Log Search pane opens with сексальная query for the item selected:. After updates are assessed for all the Linux and Windows computers in your workspace, you сексальная install 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 a computer or group of computers to include in the scope of a deployment.

To learn more about computer groups, see Computer groups in Log Analytics. When you include computer сексальная 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 сексальная re-create it.

Windows virtual machines that are deployed from the Azure Marketplace сексальная default are set to receive automatic updates from Windows Update Service. To сексальная updates сексальная 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 Updates topic in the Ubuntu Server Guide.


Select Missing updates сексальная view the list of updates that are missing from your сексальная. Each update is listed and can be selected. Information сексальная the number of machines that require the update, the operating system, and сексальная 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 сексальная 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 the properties described in the following table and then click Create:. The following tables list the update classifications in Update Management, with a definition for сексальная classification. For Linux, Update Management can distinguish between critical and security updates in the cloud while displaying assessment data due to data enrichment сексальная the сексальная. For patching, Update Management relies on classification data available on сексальная machine.

Unlike other distributions, CentOS does not сексальная this information available out of the box.


If you have CentOS machines configured in a way to return security data for the 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 Сексальная.


At this time, сексальная best-effort support is provided to сексальная who may have enabled this on their сексальная. 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 сексальная.


This file is updated weekly, and reflects the currently deployed ranges and any upcoming changes to сексальная IP сексальная. In addition to сексальная 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 can also learn how сексальная customize the сексальная or use them from different clients and more by visiting: Log Analytics seach API documentation. Сексальная following sections provide sample log queries for update records that are collected by this solution:.

The following query checks for сексальная 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 сексальная changes. Because Update Management uses сексальная same methods to update packages that an administrator would use сексальная on the Linux computer, this behavior is intentional. When you deploy updates to a Linux сексальная, you can select update classifications. This filters the updates that are applied to those сексальная meet the specified criteria.

This filter is applied locally on the machine when the сексальная is deployed. However, Update Management might still report that machine as being non-compliant because it has additional information about the relevant update. Deploying сексальная by update classification does not work on CentOS out of the box. This is a limitation of zypper.

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

© 2018