Категория > Мамочки


You can use the Update Management solution in Azure Automation to manage operating system updates for your Сексигрушка and Linux computers that are сексигрушка in Azure, in on-premises environments, or in other cloud providers.

You can quickly assess the status of available updates сексигрушка all сексигрушка 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 from your Automation account, see Сексигрушка updates for multiple virtual machines.

You can also enable Update Management for a single virtual machine from сексигрушка virtual machine pane сексигрушка 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 сексигрушка flow with how the solution assesses and applies security updates to сексигрушка connected Windows 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 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 сексигрушка update installation. For a Linux computer, the compliance scan is performed every сексигрушка hours by default. If the MMA agent is restarted, a compliance scan is initiated within 15 minutes. This сексигрушка the same for Linux computers that are configured to report to a local repo instead of to a public repo.

To 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 updates are included in the deployment scope. You also specify a сексигрушка to approve and designate a period of time during which updates can сексигрушка installed. Updates are installed by runbooks in Azure Automation. When an update deployment is created, the update deployment сексигрушка a schedule that starts a master update runbook at the specified time for сексигрушка included computers. The master runbook starts a child runbook on сексигрушка agent to perform installation of required сексигрушка.

At the date and time specified in the update deployment, the target computers execute the сексигрушка in parallel.


сексигрушка Before installation, a scan is performed to verify that the updates are still required. The Windows agent is required. For Linux, сексигрушка machine must have access to an update repository.


The update repository can be private or public. Сексигрушка create and manage update deployments, you need specific permissions. To learn about these permissions, see Role-based сексигрушка - 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 сексигрушка 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 the Hybrid Runbook Worker group membership.

This functionality was added in сексигрушка 7. If your Сексигрушка Center Operations Manager management group is connected to a Log Analytics workspace, the following management сексигрушка are installed in Operations Manager. These management packs сексигрушка also installed on directly сексигрушка Windows computers after сексигрушка add the solution.

For more information about how solution management packs are updated, see Connect Operations Manager to Log Analytics. For systems with the Сексигрушка Manger Сексигрушка, to be сексигрушка 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. To confirm that directly connected machines are communicating with Log Analytics, after a few minutes, you can run one the following log searches.

Сексигрушка a Windows computer, you can review сексигрушка following information to verify agent сексигрушка with Log Analytics:. To learn how to verify that the firewall or proxy server is properly configured, see Network configuration for Windows agent сексигрушка Network configuration for Linux agent. Newly added Linux agents show a status of Updated сексигрушка an assessment has been performed. This process can сексигрушка up to 6 hours. A scan is performed сексигрушка per day сексигрушка 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.


Сексигрушка the status has changed, 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 account, select Update Management to view the status сексигрушка your сексигрушка.

This view provides information about your machines, missing updates, update deployments, and scheduled update deployments. To run a log search that returns information about сексигрушка machine, update, or deployment, select the item сексигрушка the list. The Log Search pane opens with a query for the item selected:. Сексигрушка updates are assessed for all the Linux and Windows computers in your workspace, you can сексигрушка required updates сексигрушка creating an update deployment.

An сексигрушка deployment is a scheduled сексигрушка of required updates сексигрушка one or more computers. You specify the date and time for the deployment and a computer сексигрушка group of computers to include in the scope of a deployment. To learn more about computer groups, see Computer groups сексигрушка 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 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 сексигрушка 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 to view the list of updates that are missing from your сексигрушка. Each update is listed and can be selected. Сексигрушка about the number of machines that require the update, the operating system, and a link for more information is shown. The Log search pane сексигрушка more details about the updates. Select сексигрушка Update Deployments tab to сексигрушка the list of existing update deployments.

Select any of the update deployments in the table to open the Update Сексигрушка Run pane for that update deployment. To create сексигрушка new update deployment, select Schedule update deployment. The New Update Deployment pane opens.


Enter values for the properties described in the following table and сексигрушка click Create:. The following tables list the update classifications in Update Management, with a definition сексигрушка each classification. For Linux, Update Management can distinguish сексигрушка critical and security updates in the cloud while displaying assessment data сексигрушка to data enrichment in the cloud.

For patching, Сексигрушка Management relies on classification data available on the machine. Unlike other distributions, CentOS does not have this information available out of the box. If сексигрушка have CentOS machines configured in a way to return security data for the following command, Сексигрушка Management will be able to 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 is provided to customers who сексигрушка have enabled this on their own. The following addresses are required specifically for Update Management.


Communication to these addresses occurs over port 443. For more information about ports that the Сексигрушка Runbook Worker requires, сексигрушка 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 сексигрушка upcoming 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 Сексигрушка pane opens.


You сексигрушка also learn how to customize the queries or сексигрушка them from different clients and more by visiting: Log Analytics seach API documentation. The following sections provide sample log queries сексигрушка update records that are collected by this solution:. The following query checks for a match on either endianness. Customers who have invested in System Сексигрушка Configuration Manager for managing PCs, servers, and mobile devices also rely on the strength and maturity of Configuration Manager сексигрушка 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 сексигрушка that an administrator would сексигрушка locally on the Linux computer, this behavior is intentional. Сексигрушка 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 is applied locally on the machine when the update is deployed. However, Update Management might still report that machine as being non-compliant because it 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