Skip to content

Commit 652af79

Browse files
authored
Merge pull request #204443 from MicrosoftDocs/release-updatecenterv2-publicpreview
Release updatecenterv2 publicpreview--scheduled release at 8AM 0f 7/13
2 parents 9d3b29e + 84d5792 commit 652af79

File tree

94 files changed

+2800
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

94 files changed

+2800
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Assessment options in update management center (preview).
3+
description: The article describes the assessment options available in Update management center (preview).
4+
ms.service: update-management-center
5+
ms.date: 04/21/2022
6+
ms.topic: conceptual
7+
author: snehasudhirG
8+
ms.author: sudhirsneha
9+
---
10+
11+
# Assessment options in update management center (preview)
12+
13+
**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
14+
15+
This article provides an overview of the assessment options available by update management center (preview).
16+
17+
Update management center (preview) provides you the flexibility to assess the status of available updates and manage the process of installing required updates for your machines.
18+
19+
## Periodic assessment
20+
21+
Periodic assessment is an update setting on a machine that allows you to enable automatic periodic checking of updates by update management center (preview). We recommend that you enable this property on your machines as it allows update management center (preview) to fetch latest updates for your machines every 24 hours and enables you to view the latest compliance status of your machines. You must register this [feature in your Azure subscription](enable-machines.md#from-the-azure-portal). You can enable this setting using update settings flow as detailed [here](manage-update-settings.md#configure-settings-on-single-vm) or enable it at scale by using [Policy](periodic-assessment-at-scale.md).
22+
23+
:::image type="content" source="media/updates-maintenance/periodic-assessment-inline.png" alt-text="Screenshot showing periodic assessment option." lightbox="media/updates-maintenance/periodic-assessment-expanded.png":::
24+
25+
## Check for updates now/On-demand assessment
26+
27+
Update management center (preview) allows you to check for latest updates on your machines at any time, on-demand. You can view the latest update status and act accordingly. Go to **Updates** blade on any VM and select **Check for updates** or select multiple machines from update management center (preview) and check for updates for all machines at once. For more information, see [check and install on-demand updates](view-updates.md).
28+
29+
## Update assessment scan
30+
You can initiate a software updates compliance scan on a machine to get a current list of operating system updates available.
31+
32+
- **On Windows** - the software update scan is actually performed by the Windows Update Agent.
33+
- **On Linux** - the software update scan is performed using OVAL-compatible tools to test for the presence of vulnerabilities based on the OVAL Definitions for that platform, which is retrieved from a local or remote repository.
34+
35+
In the **Updates (preview)** page, after you initiate an assessment, a notification is generated to inform you the activity has started and another is displayed when it is finished.
36+
37+
:::image type="content" source="media/assessment-options/updates-preview-page.png" alt-text="Screenshot of the Updates (preview) page.":::
38+
39+
40+
The **Recommended updates** section is updated to reflect the OS updates applicable. You can also select **Refresh** to update the information on the page and review the assessment details of the selected machine.
41+
42+
In the **History** section, you can view:
43+
- **Total deployments**—the total number of deployments.
44+
- **Failed deployments**—the number out of the total deployments that failed.
45+
- **Successful deployments**—the number out of the total deployments that were successful.
46+
47+
A list of the deployments created are shown in the update deployment grid and include relevant information about the deployment. Every update deployment has a unique GUID, represented as **Activity ID**, which is listed along with **Status**, **Updates Installed**, and **Time details**. You can filter the results listed in the grid in the following ways:
48+
49+
- Select one of the tile visualizations
50+
- Select a specific time period. Options are: **Last 30 Days**, **Last 15 Days**, **Last 7 Days**, and **Last 24 hrs**. By default, deployments from the last 30 days are shown.
51+
- Select a specific deployment status. Options are: **Succeeded**, **Failed**, **CompletedWithWarnings**, **InProgress**, and **NotStarted**. By default, all status types are selected.
52+
Selecting any one of the update deployments from the list will open the **Assessment run** page. Here, it shows a detailed breakdown of the updates and the installation results for the Azure VM or Arc-enabled server.
53+
54+
In the **Scheduling** section, you can either **create a maintenance configuration** or **attach existing maintenance configuration**. See the section for more information on [how to create a maintenance configuration](scheduled-patching.md#create-a-new-maintenance-configuration) and [how to attach existing maintenance configuration](scheduled-patching.md#attach-a-maintenance-configuration).
55+
56+
57+
## Next steps
58+
59+
* To view update assessment and deployment logs generated by update management center (preview), see [query logs](query-logs.md).
60+
* To troubleshoot issues, see the [Troubleshoot](troubleshoot.md) update management center (preview).
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: Configure Windows Update settings in Update management center (Preview)
3+
description: This article tells how to configure Windows update settings to work with Update management center (Preview).
4+
ms.service: update-management-center
5+
ms.date: 04/21/2022
6+
ms.topic: conceptual
7+
author: SnehaSudhirG
8+
ms.author: sudhirsneha
9+
---
10+
11+
# Configure Windows update settings for update management center (preview)
12+
13+
Update management center (Preview) relies on the [Windows Update client](/windows/deployment/update/windows-update-overview) to download and install Windows updates. There are specific settings that are used by the Windows Update client when connecting to Windows Server Update Services (WSUS) or Windows Update. Many of these settings can be managed by:
14+
15+
- Local Group Policy Editor
16+
- Group Policy
17+
- PowerShell
18+
- Directly editing the Registry
19+
20+
The Update management center (preview) respects many of the settings specified to control the Windows Update client. If you use settings to enable non-Windows updates, the Update management center (preview) will also manage those updates. If you want to enable downloading of updates before an update deployment occurs, update deployment can be faster, more efficient, and less likely to exceed the maintenance window.
21+
22+
For additional recommendations on setting up WSUS in your Azure subscription and to secure your Windows virtual machines up to date, review [Plan your deployment for updating Windows virtual machines in Azure using WSUS](/azure/architecture/example-scenario/wsus).
23+
24+
## Pre-download updates
25+
26+
To configure the automatic downloading of updates without automatically installing them, you can use Group Policy to [configure the Automatic Updates setting](/windows-server/administration/windows-server-update-services/deploy/4-configure-group-policy-settings-for-automatic-updates#configure-automatic-updates) to 3. This setting enables downloads of the required updates in the background, and notifies you that the updates are ready to install. In this way, update management center (Preview) remains in control of schedules, but allows downloading of updates outside the maintenance window. This behavior prevents `Maintenance window exceeded` errors in update management center (preview).
27+
28+
You can enable this setting in PowerShell:
29+
30+
```powershell
31+
$WUSettings = (New-Object -com "Microsoft.Update.AutoUpdate").Settings
32+
$WUSettings.NotificationLevel = 3
33+
$WUSettings.Save()
34+
```
35+
36+
## Configure reboot settings
37+
38+
The registry keys listed in [Configuring Automatic Updates by editing the registry](/windows/deployment/update/waas-wu-settings#configuring-automatic-updates-by-editing-the-registry) and [Registry keys used to manage restart](/windows/deployment/update/waas-restart#registry-keys-used-to-manage-restart) can cause your machines to reboot, even if you specify **Never Reboot** in the **Update Deployment** settings. Configure these registry keys to best suit your environment.
39+
40+
## Enable updates for other Microsoft products
41+
42+
By default, the Windows Update client is configured to provide updates only for Windows. If you enable the **Give me updates for other Microsoft products when I update Windows** setting, you also receive updates for other products, including security patches for Microsoft SQL Server and other Microsoft software. You can configure this option if you have downloaded and copied the latest [Administrative template files](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) available for Windows 2016 and later.
43+
44+
If you have machines running Windows Server 2012 R2, you can't configure this setting through Group Policy. Run the following PowerShell command on these machines:
45+
46+
```powershell
47+
$ServiceManager = (New-Object -com "Microsoft.Update.ServiceManager")
48+
$ServiceManager.Services
49+
$ServiceID = "7971f918-a847-4430-9279-4a52d1efe18d"
50+
$ServiceManager.AddService2($ServiceId,7,"")
51+
```
52+
53+
## Make WSUS configuration settings
54+
55+
Update management center (Preview) supports WSUS settings. You can specify sources for scanning and downloading updates using instructions in [Specify intranet Microsoft Update service location](/windows/deployment/update/waas-wu-settings#specify-intranet-microsoft-update-service-location). By default, the Windows Update client is configured to download updates from Windows Update. When you specify a WSUS server as a source for your machines, the update deployment fails, if the updates aren't approved in WSUS.
56+
57+
To restrict machines to the internal update service, see [do not connect to any Windows Update Internet locations](/windows-server/administration/windows-server-update-services/deploy/4-configure-group-policy-settings-for-automatic-updates#do-not-connect-to-any-windows-update-internet-locations).
58+
59+
## Next steps
60+
61+
Configure an update deployment by following instructions in [Deploy updates](deploy-updates.md).

0 commit comments

Comments
 (0)