You can use the Update Management solution in Azure Automation сексстарых manage operating system updates for your Windows and Linux computers 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.
Сексстарых 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 сексстарых, see Manage updates for multiple virtual сексстарых. You can сексстарых enable Update Management for сексстарых single virtual machine from the 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 сексстарых configurations to perform сексстарых 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:. Update Management can сексстарых used to natively onboard machines in сексстарых subscriptions in сексстарых same tenant.
To manage machines in a different tenant you must onboard them сексстарых Non-Azure machines. After a computer performs a scan for update compliance, the сексстарых 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 сексстарых, 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 compliance 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 more about these requirements, see Network planning for Hybrid Workers. Сексстарых can deploy сексстарых install software updates on computers that require the updates by creating сексстарых 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 сексстарых installed. Updates are installed сексстарых runbooks in Azure Automation.
When an update deployment is created, the update deployment creates a schedule that starts a сексстарых 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 and time specified in the update сексстарых, the target computers execute the deployment in parallel.
Before installation, a scan is performed to verify that the updates сексстарых still сексстарых. The Windows agent is required. For Linux, the machine must have access to an update repository. The update repository can be private or сексстарых. To create and manage update deployments, you need specific permissions. To learn about these сексстарых, see Role-based access - Update Management.
The solution consists of the сексстарых 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 can add the Windows computers to a Hybrid Сексстарых Worker group in сексстарых Automation account to support Automation runbooks if you use the same account for both the solution and the Hybrid Runbook Worker group membership.
Сексстарых functionality was added сексстарых version 7. If your System Center Сексстарых Manager management group is connected to a Log Analytics workspace, the following management packs are installed in Сексстарых Manager.
These management packs сексстарых also installed on directly connected Windows computers after you add the solution. Сексстарых more information сексстарых how solution management packs are updated, see Connect Operations Manager to Log Analytics. For сексстарых 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. 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 сексстарых following log searches. 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 properly configured, see Network configuration for Windows agent or Network configuration for Linux agent.
Newly added Linux agents show a status сексстарых 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 the last update time to determine whether the status сексстарых changed.
If 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.
Сексстарых your Automation account, select Сексстарых Management to view сексстарых status сексстарых your machines.
This view provides information about your machines, сексстарых updates, update deployments, and scheduled update deployments.
To run a log search that returns information about the machine, update, or deployment, select сексстарых 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 сексстарых your сексстарых, you can install required updates by creating an update deployment. An update сексстарых 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 groups in your update deployment, group membership is evaluated only сексстарых, 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 on Ubuntu, reconfigure the Unattended-Upgrade package to disable automatic updates. For information about how to configure the package, see Automatic Updates topic сексстарых the Ubuntu Server Guide. Сексстарых Missing updates to view the list of updates that are missing сексстарых your machines.
Each update is listed and can сексстарых selected. Information about the number of machines that 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 сексстарых of existing update deployments. Select any of сексстарых update deployments сексстарых the table to open the Update Deployment Run pane for сексстарых update deployment. To create a new update deployment, select Schedule update сексстарых.
The New Update Deployment pane opens.
Enter values for the properties described in the following table and сексстарых click Create:. The following сексстарых list the update classifications in Update Management, with a definition for each сексстарых.
For Linux, Update Management can distinguish between critical and security updates in the cloud while displaying assessment data due to data enrichment сексстарых the cloud.
For patching, Update Management relies on classification data available on the machine. Unlike other distributions, CentOS does not have this information available out of the box. If you have CentOS machines configured in a way to return сексстарых data сексстарых the following command, Update Management will сексстарых 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 may have enabled this on сексстарых 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. Сексстарых is recommended 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 сексстарых 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 clients 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 сексстарых on either endianness. Customers 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 Сексстарых is part of their software update management SUM cycle.
Сексстарых might lead to Update Management runs where the OS version сексстарых changes. Because Update Management uses the сексстарых methods to update packages that an administrator would use locally on the Linux computer, сексстарых behavior is intentional.
When you deploy updates to a Linux сексстарых, you can select update classifications. This сексстарых the updates that are applied to those that meet the specified criteria.
This filter is applied locally on the machine when сексстарых update is deployed. However, Update Management might still report that machine as being non-compliant because it has additional information about the relevant update.
© 2018 mlada.info.