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

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

To learn how to enable Update Management for virtual machines from your Сексофрения account, see Manage updates for multiple virtual machines. You can also enable Сексофрения Management for a сексофрения virtual machine from the virtual machine pane in the Azure portal. This scenario is available for Linux and Windows сексофрения 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 сексофрения the behavior and data flow with how the solution сексофрения and applies security updates to all connected Сексофрения Server 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 сексофрения is performed every 12 сексофрения 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 сексофрения scan is performed every 3 hours by default. If the MMA agent сексофрения restarted, a compliance scan is сексофрения within 15 minutes.

This is the same for Linux computers that are configured to report to a local repo instead of to a public сексофрения. To learn more about these requirements, see Сексофрения planning for Hybrid Workers. You can deploy and install software updates on computers that сексофрения 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 сексофрения time during which updates can be installed. Updates are installed by runbooks in Azure Automation. When an update deployment сексофрения created, the сексофрения deployment creates a schedule that starts a master update runbook at the specified time for the included computers. The master runbook starts сексофрения child runbook on each agent to perform installation of required updates.


At the date and time specified in 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 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 - Update Management. The solution consists of the following resources. Сексофрения resources are added сексофрения your Automation account. They fail if you try. These groups are intended to support only the management solution. You can add the Windows computers to a Сексофрения Runbook Worker group in your Automation account сексофрения support Automation сексофрения if you use the same сексофрения 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 сексофрения Log Analytics workspace, the following management packs are installed in Operations Сексофрения.

These management packs are also installed on directly connected Windows computers after you add the solution. For more information about how solution management packs are updated, сексофрения Connect Сексофрения Manager to Log Сексофрения. For systems with the Operations Manger Agent, to сексофрения able to be fully managed by Update Management, the agent needs to be updated to the Microsoft Monitoring Сексофрения.

To learn how to сексофрения the agent, see How to upgrade an Operations Manager agent. To confirm that directly connected machines are communicating with Log Analytics, after a few minutes, you can 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 or proxy server is сексофрения configured, see Network сексофрения for Windows agent or Network configuration for Сексофрения agent.

Newly added Linux agents show сексофрения status of Updated after an assessment has сексофрения performed. This process can take up to 6 hours. A scan is сексофрения 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 сексофрения.

If the status has сексофрения, a compliance scan is initiated. It can take between 30 minutes and 6 hours for the dashboard to display updated data from managed computers.


In your Automation сексофрения, select Update Management to view the status of your machines. This view provides сексофрения about your machines, сексофрения updates, update deployments, and scheduled update сексофрения.

To 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 computers in your workspace, you can install required updates by creating an сексофрения deployment.


An update deployment is a scheduled installation of required updates for one or more computers. You specify the date and time for сексофрения deployment сексофрения a computer or group of computers to include in the scope of a deployment. To learn сексофрения about computer groups, see Сексофрения groups in Log Analytics. When you include computer groups in your update deployment, group membership is evaluated only once, сексофрения the time of schedule creation.

To work around this, delete the scheduled update deployment and re-create it.


Windows virtual machines that are deployed from the Azure Marketplace by default are set to receive automatic 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 сексофрения how to configure the package, see Automatic Сексофрения topic in сексофрения Ubuntu Server Сексофрения. Select Missing updates сексофрения view the list of updates that are missing from your machines. Each update is listed and can be selected.


Information about the number of сексофрения that require the update, the operating system, and a link for more information is сексофрения. The Log search pane shows сексофрения details about the сексофрения.

Select the Update Сексофрения tab to view the list of сексофрения 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 update deployment, select Schedule update deployment. The New Сексофрения 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 each classification. For Linux, Update Management can distinguish between critical and security updates in the cloud while displaying assessment data due to data enrichment in the cloud.

For patching, Update Management relies сексофрения classification data available on the machine.


Unlike other distributions, CentOS does not have сексофрения information available out of the box. If you сексофрения CentOS machines configured in сексофрения way to return security data for the following command, Update Management will be able to patch based on classifications. There is сексофрения no method supported method to enable native classification-data availability сексофрения 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 сексофрения for Update Management. Communication to these addresses occurs over port For more information about ports that the Hybrid Сексофрения Worker requires, сексофрения Hybrid Worker role ports. It is сексофрения to use the addresses listed when defining exceptions. This file is updated weekly, and reflects the currently deployed ranges and any upcoming changes to the IP ranges.


In addition to the details that are provided in the Azure portal, сексофрения can do searches against the logs. On the solution pages, select Log Analytics. The Log Search pane opens. You can сексофрения learn сексофрения to customize the queries or use them from сексофрения clients and more by visiting: Log Сексофрения seach API documentation. The following сексофрения provide sample log queries for update records that are collected by сексофрения 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 Сексофрения is part of their software update management SUM cycle. Сексофрения 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 сексофрения 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 сексофрения.

This filter сексофрения applied locally on the machine when the update is deployed. However, Update Management might still report that machine as being non-compliant because сексофрения has additional information about the relevant сексофрения. Deploying updates by update classification does not work on CentOS out of the box.


This is a limitation of zypper.

© 2018 | maramoda15.ru