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

You can use the Update Management solution in Azure Automation to manage мегаминет system updates for your Windows and Linux computers мегаминет are deployed in Azure, in on-premises environments, or мегаминет other cloud мегаминет. 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 Update Management for virtual 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 мегаминет. You can also enable Update Management for a single virtual machine from the virtual machine pane in the Мегаминет portal.


This scenario is available for Linux and Windows virtual machines. Computers that are managed by Update Мегаминет 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 Мегаминет Server and Linux computers in a workspace:.

After мегаминет computer performs a scan for update compliance, the agent forwards the information in bulk to Azure Мегаминет Analytics. On a Windows computer, the compliance scan is performed every 12 hours by default. In addition to the scan schedule, the мегаминет 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 мегаминет. This is the same for Linux computers мегаминет are configured to report to a local мегаминет instead of to a public repo. To learn more about these requirements, see Network planning for Hybrid Workers.


Мегаминет can deploy and install software updates on computers that require the updates by creating a scheduled deployment. Only required updates are included in the deployment scope.

You also specify a schedule to approve and designate a period of time during which updates can be installed. 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 the specified time for the included computers. The master мегаминет starts a child runbook on мегаминет agent to perform мегаминет of required updates.

At the date and time specified in the update мегаминет, the target computers execute the deployment in parallel. Мегаминет installation, a scan is performed to verify that the updates are still required.


The Windows agent is required. For Linux, the machine must have access to an update repository. The update repository can be private or public. To create and manage update deployments, you need specific permissions. To learn about these permissions, see Role-based access - Мегаминет Management. The мегаминет consists of the following resources. The resources are added to your Automation мегаминет. They fail if you try. These groups are мегаминет to support only the management solution.

You can add the Windows computers to a Hybrid Runbook Worker group in 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 мегаминет version 7.


If your System Мегаминет 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 мегаминет connected Windows мегаминет after you мегаминет the solution. For more information about how solution мегаминет packs are updated, see Connect Operations Manager to Log Analytics. For systems with the Мегаминет 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 мегаминет upgrade an Operations Manager agent. To confirm that directly connected machines are communicating with Log Analytics, after a few minutes, you can run мегаминет the following log searches. On a Мегаминет computer, you can review the following information to verify agent connectivity with Log Analytics:. To learn how to verify that the firewall or proxy server is properly configured, see Network configuration for Windows agent or Network configuration for Linux agent.

Newly added Linux agents show мегаминет status of Updated after мегаминет 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, мегаминет Windows API is called to query мегаминет the last update time to determine мегаминет the status has changed. If the status has changed, a мегаминет scan is initiated. It can take between 30 minutes and 6 hours for the мегаминет to display updated data from managed computers.

In your Automation account, select Update Management to view the status of your machines. This view provides information мегаминет your machines, missing updates, update deployments, and scheduled update deployments.


Мегаминет run a log search 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 installation of required updates for мегаминет or more computers.

You specify the мегаминет and time for the deployment and a computer or group of computers to include in the scope of a deployment. To learn more мегаминет 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 and re-create it.


Мегаминет virtual machines that are deployed from the Azure Marketplace by default are set to receive мегаминет updates from Windows Update Service. To 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 Updates topic in the Ubuntu Server Guide. Select Missing мегаминет to view the list of updates that мегаминет missing from your machines. Each update is listed and can be selected. Information about the number of machines that require the мегаминет, the operating system, мегаминет a link for more information мегаминет shown. The Log search pane shows more details about the updates.

Select the Update Deployments tab to view мегаминет list of existing update deployments. Select any of the update deployments in the table to open the Update Deployment Run pane for that update deployment. To create a new мегаминет 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 classifications in Update Мегаминет, with a definition for each classification.


For Linux, Update Management can distinguish between мегаминет and security updates in мегаминет cloud while displaying assessment data due to data enrichment in the cloud. For patching, Update Management relies on classification data available on the machine. Unlike other distributions, CentOS мегаминет not have this information available out of the box.

If you have CentOS machines configured in a way to return security data мегаминет the following command, Update Management will be able мегаминет patch based on classifications. There is currently no method supported method to enable native classification-data availability on CentOS.


At this time, only best-effort support мегаминет provided to customers who мегаминет have enabled мегаминет on their own. The following addresses are required specifically for Update Management. Communication to these addresses occurs over мегаминет 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 мегаминет updated weekly, and reflects the currently deployed мегаминет and мегаминет upcoming changes to the IP ranges. In addition to the мегаминет 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 to customize the queries or use them from different мегаминет 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.

Мегаминет 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 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 filters the updates that are applied to those that meet the specified criteria. This filter is мегаминет locally on мегаминет machine when the update is deployed. However, Update Management might still мегаминет that machine as being non-compliant because мегаминет has additional information about the relevant update.

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


This is a limitation of zypper.

© 2018 | nakushetke.ru