mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Add periods to alt text
No other changes
This commit is contained in:
Gary Moore
@ -45,17 +45,17 @@ its reverse differential back to the base version. Both forward and reverse
|
||||
differentials are then packaged as an update and distributed to the endpoints
|
||||
running the software to be updated. The update package contents can be symbolized as follows:
|
||||
|
||||
|
||||
|
||||
|
||||
The endpoints that have the base version of the file (V<sub>0</sub>) hydrate the target
|
||||
revision (V<sub>N</sub>) by applying a simple transformation:
|
||||
|
||||
|
||||
|
||||
|
||||
The endpoints that have revision N of the file (V<sub>N</sub>), hydrate the target revision
|
||||
(V<sub>R</sub>) by applying the following set of transformations:
|
||||
|
||||
|
||||
|
||||
|
||||
The endpoints retain the reverse differentials for the software revision they
|
||||
are on, so that it can be used for hydrating and applying next revision update.
|
||||
@ -85,7 +85,7 @@ Windows 10 quality update packages will contain forward differentials from quali
|
||||
|
||||
There can be cases where new files are added to the system during servicing. These files will not have RTM baselines, thus forward and reverse differentials cannot be used. In these scenarios, null differentials will be used to handle servicing. Null differentials are the slightly compressed and optimized version of the full binaries. Update packages can have either forward or reverse differentials, or null differential of any given binary in them. The following image symbolizes the content of a Windows 10 quality update installer:
|
||||
|
||||
|
||||
|
||||
|
||||
### Hydration and installation
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ Microsoft recommends that all organizations have at least a few devices enrolled
|
||||
|
||||
The Windows Insider Program doesn't replace Semi-Annual Channel deployments in an organization. Rather, it provides IT Pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.
|
||||
|
||||
[](images/WIP4Biz_deployment.png)<br>
|
||||
[](images/WIP4Biz_deployment.png)<br>
|
||||
Windows 10 Insider Preview builds enable organizations to prepare sooner for Windows Semi-Annual releases and reduce the overall validation effort required with traditional deployments.
|
||||
|
||||
## Explore new Windows 10 features in Insider Previews
|
||||
|
||||
@ -50,15 +50,15 @@ To be informed about the latest updates and releases, follow us on Twitter [@Win
|
||||
|
||||
The **All versions** tab (the default view) shows all Windows products with access to their posted known issues.
|
||||
|
||||
|
||||
|
||||
|
||||
A known issue is an issue that has been identified in a Windows monthly update or feature update that impacts Windows devices. The **Active and recently resolved** column provides a link to the **Known issues** tab filtered to the version selected. Selecting the **Known issues** tab will show known issues that are active or resolved within the last 30 days.
|
||||
|
||||
|
||||
|
||||
|
||||
The **History** tab shows the history of known issues that have been resolved for up to 6 months.
|
||||
|
||||
|
||||
|
||||
|
||||
The known issue summary provides the following information:
|
||||
|
||||
@ -70,7 +70,7 @@ To be informed about the latest updates and releases, follow us on Twitter [@Win
|
||||
|
||||
Select the **Issue title** to access more information, including a link to the history of all status updates posted while we work on a solution. Here is an example:
|
||||
|
||||
|
||||
|
||||
|
||||
## Status definitions
|
||||
|
||||
@ -91,11 +91,11 @@ In the **Windows release health** experience, every known issue is assigned as s
|
||||
|
||||
The Windows release health page lets you view the history of all status updates posted for a specific known issue. To view all past updates posted for a given issue, select **View history** on the issue detail page.
|
||||
|
||||
|
||||
|
||||
|
||||
A list of all status updates posted in the selected timeframe will be displayed, as shown below. You can expand any row to view the specific information provided in that status update.
|
||||
|
||||
|
||||
|
||||
|
||||
## Frequently asked questions
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ The service is privacy focused and backed by leading industry compliance certifi
|
||||
|
||||
The deployment service complements existing Windows Update for Business capabilities, including existing device policies and [Update Compliance](update-compliance-monitor.md).
|
||||
|
||||
:::image type="content" source="media/wufbds-product-large.png" alt-text="Elements in following text":::
|
||||
:::image type="content" source="media/wufbds-product-large.png" alt-text="Elements in following text.":::
|
||||
|
||||
Windows Update for Business comprises three elements:
|
||||
- Client policy to govern update experiences and timing – available through Group Policy and CSPs
|
||||
@ -42,7 +42,7 @@ Windows Update for Business comprises three elements:
|
||||
|
||||
Unlike existing client policy, the deployment service does not interact with devices directly. The service is native to the cloud and all operations take place between various Microsoft services. It creates a direct communication channel between a management tool (including scripting tools such as Windows PowerShell) and the Windows Update service so that the approval and offering of content can be directly controlled by an IT Pro.
|
||||
|
||||
:::image type="content" source="media/wufbds-interaction-small.png" alt-text="Process described in following text":::
|
||||
:::image type="content" source="media/wufbds-interaction-small.png" alt-text="Process described in following text.":::
|
||||
|
||||
Using the deployment service typically follows a common pattern:
|
||||
1. IT Pro uses a management tool to select devices and approve content to be deployed. This tool could be PowerShell, a Microsoft Graph app or a more complete management solution such as Microsoft Endpoint Manager.
|
||||
|
||||
@ -72,12 +72,12 @@ The Semi-Annual Channel is the default servicing channel for all Windows 10 devi
|
||||
|
||||
| Windows 10 edition | Semi-Annual Channel | Insider Program | Long-Term Servicing Channel |
|
||||
| --- | --- | --- | --- |
|
||||
| Home | | | |
|
||||
| Pro |  |  | |
|
||||
| Enterprise |  | | |
|
||||
| Enterprise LTSB |  | | |
|
||||
| Pro Education |  |  | |
|
||||
| Education |  |  | |
|
||||
| Home | | | |
|
||||
| Pro |  |  | |
|
||||
| Enterprise |  | | |
|
||||
| Enterprise LTSB |  | | |
|
||||
| Pro Education |  |  | |
|
||||
| Education |  |  | |
|
||||
|
||||
## Servicing tools
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ The Windows Update workflow has four core areas of functionality:
|
||||
During the updating process, the Windows Update Orchestrator operates in the background to scan, download, and install updates. It does these actions automatically, according to your settings, and silently so that doesn't disrupt your computer usage.
|
||||
|
||||
## Scanning updates
|
||||
|
||||
|
||||
|
||||
The Windows Update Orchestrator on your PC checks the Microsoft Update server or your WSUS endpoint for new updates at random intervals. The randomization ensures that the Windows Update server isn't overloaded with requests all at the same time. The Update Orchestrator searches only for updates that have been added since the last time updates were searched, allowing it to find updates quickly and efficiently.
|
||||
|
||||
@ -86,14 +86,14 @@ When users start scanning in Windows Update through the Settings panel, the foll
|
||||
- Updates are identified by the different IDs ("ID = 10", "ID = 11") and from the different thread ID numbers.
|
||||
- Windows Update uses the thread ID filtering to concentrate on one particular task.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Identifies service IDs
|
||||
|
||||
- Service IDs indicate which update source is being scanned.
|
||||
|
||||
- The Windows Update engine treats every service as a separate entity, even though multiple services may contain the same updates.
|
||||
|
||||
|
||||
- Common service IDs
|
||||
|
||||
> [!IMPORTANT]
|
||||
@ -120,10 +120,10 @@ Common update failure is caused due to network issues. To find the root of the i
|
||||
> If the search is against WSUS or Configuration Manager, you can ignore warning messages for the Service Locator Service.
|
||||
|
||||
- On sites that only use WSUS or Configuration Manager, the Service Locator Service might be blocked at the firewall. In this case the request will fail, and though the service can’t scan against Windows Update or Microsoft Update, it can still scan against WSUS or Configuration Manager, since it’s locally configured.
|
||||
|
||||
|
||||
|
||||
## Downloading updates
|
||||
|
||||
|
||||
|
||||
Once the Windows Update Orchestrator determines which updates apply to your computer, it will begin downloading the updates, if you have selected the option to automatically download updates. It does operation in the background without interrupting your normal use of the device.
|
||||
|
||||
@ -132,14 +132,14 @@ To ensure that your other downloads aren't affected or slowed down because updat
|
||||
For more information, see [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md).
|
||||
|
||||
## Installing updates
|
||||
|
||||
|
||||
|
||||
When an update is applicable, the "Arbiter" and metadata are downloaded. Depending on your Windows Update settings, when downloading is complete, the Arbiter will gather details from the device, and compare that with the downloaded metadata to create an "action list".
|
||||
|
||||
The action list describes all the files needed from Windows Update, and what the installation agent (such as CBS or Setup) should do with them. The action list is provided to the installation agent along with the payload to begin the installation.
|
||||
|
||||
## Committing Updates
|
||||
|
||||
|
||||
|
||||
When the option to automatically install updates is configured, the Windows Update Orchestrator, in most cases, automatically restarts the device for you after installing the updates. It has to restart the device because it might be insecure, or not fully updated, until it restarts. You can use Group Policy settings, mobile device management (MDM), or the registry (not recommended) to configure when devices will restart after a Windows 10 update is installed.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ Devices must be able to connect to the internet to obtain Dynamic Updates. In so
|
||||
|
||||
You can obtain Dynamic Update packages from the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx). At that site, use the search bar in the upper right to find the Dynamic Update packages for a particular release. For example, you could enter *1809 Dynamic Update x64*, which would return results like this:
|
||||
|
||||
|
||||
|
||||
|
||||
The various Dynamic Update packages might not all be present in the results from a single search, so you might have to search with different keywords to find all of the updates. And you'll need to check various parts of the results to be sure you've identified the needed files. This table shows in **bold** the key items to search for or look for in the results. For example, to find the relevant "Setup Dynamic Update," you'll have to check the detailed description for the download by selecting the link in the **Title** column of the search results.
|
||||
|
||||
|
||||
@ -55,20 +55,20 @@ This is the Bring Your Own Device (BYOD) method--your device will receive Olympi
|
||||
|
||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your device (see [local administrator](https://support.microsoft.com/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||
|
||||
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
3. Click **Connect** and enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Read the **Terms and Conditions**. Click **Accept** to participate in the program.
|
||||
|
||||
@ -94,24 +94,24 @@ This is the Bring Your Own Device (BYOD) method--your device will receive Olympi
|
||||
|
||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your device (see [local administrator](https://support.microsoft.com/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||
|
||||
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
3. Click **Connect**, then click **Join this device to Azure Active Directory**.
|
||||
|
||||
![Joining device to Azure AD]](images/2-3.png)
|
||||
![Joining device to Azure AD.]](images/2-3.png)
|
||||
|
||||
4. Enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
|
||||
6. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ You can use a calendar approach for either a faster twice-per-year cadence or an
|
||||
### Annual
|
||||
Here's a calendar showing an example schedule that applies one Windows 10 feature update per calendar year, aligned with Microsoft Endpoint Manager and Microsoft 365 Apps release cycles:
|
||||
|
||||
[  ](images/annual-calendar.png#lightbox)
|
||||
[  ](images/annual-calendar.png#lightbox)
|
||||
|
||||
This approach provides approximately 12 months of use from each feature update before the next update is due to be installed. By aligning to the Windows 10, version H2 feature update, each release will be serviced for 30 months from the time of availability, giving you more flexibility when applying future feature updates.
|
||||
|
||||
@ -41,7 +41,7 @@ This cadence might be most suitable for you if any of these conditions apply:
|
||||
### Rapid
|
||||
This calendar shows an example schedule that installs each feature update as it is released, twice per year:
|
||||
|
||||
[  ](images/rapid-calendar.png#lightbox)
|
||||
[  ](images/rapid-calendar.png#lightbox)
|
||||
|
||||
This cadence might be best for you if these conditions apply:
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ Queries identify Safeguard IDs for each affected device, giving IT admins a deta
|
||||
On devices that use Windows Update (but not Windows Update for Business), the **Windows Update** page in the Settings app displays a message stating that an update is on its way, but not ready for the device. Instead of the option to download and install the update, users will see this message:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you see this message, it means one or more holds affect your device. When the issue is fixed and the update is safe to install, we’ll release the hold and the update can resume safely.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Delivery Optimization in Update Compliance
|
||||
|
||||
|
||||
The Update Compliance solution provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
||||
|
||||
## Delivery Optimization Status
|
||||
|
||||
@ -17,7 +17,7 @@ ms.custom: seo-marvel-apr2020
|
||||
|
||||
# Feature Update Status
|
||||
|
||||
[  ](images/UC_workspace_FU_status.png#lightbox)
|
||||
[  ](images/UC_workspace_FU_status.png#lightbox)
|
||||
|
||||
The Feature Update Status section provides information about the status of [feature updates](waas-quick-start.md#definitions) across all devices. This section tile in the [Overview Blade](update-compliance-using.md#overview-blade) gives a percentage of devices that are on the latest applicable feature update; [Servicing Channel](waas-overview.md#servicing-channels) is considered in determining applicability. Within this section are two blades; one providing a holistic view of feature updates, the other containing three **Deployment Status** tiles, each charged with tracking the deployment for a different [Servicing Channel](waas-overview.md#servicing-channels).
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
# Needs attention!
|
||||
|
||||
|
||||
|
||||
The **Needs attention!** section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ms.custom: seo-marvel-apr2020
|
||||
|
||||
# Security Update Status
|
||||
|
||||
|
||||
|
||||
|
||||
The Security Update Status section provides information about [security updates](waas-quick-start.md#definitions) across all devices. The section tile within the [Overview Blade](update-compliance-using.md#overview-blade) lists the percentage of devices on the latest security update available. Meanwhile, the blades within show the percentage of devices on the latest security update for each Windows 10 version and the deployment progress toward the latest two security updates.
|
||||
|
||||
|
||||
@ -30,23 +30,23 @@ Update Compliance:
|
||||
## The Update Compliance tile
|
||||
After Update Compliance has successfully been [added to your Azure subscription](update-compliance-get-started.md#add-update-compliance-to-your-azure-subscription), you'll see this tile:
|
||||
|
||||
|
||||
|
||||
|
||||
When the solution is added, data is not immediately available. Data will begin to be collected after data is sent up that belongs to the Commercial ID associated with the device. This process assumes that Windows diagnostic data is enabled and data sharing is enabled as described in [Enrolling devices in Update Compliance](update-compliance-get-started.md#enroll-devices-in-update-compliance). After Microsoft has collected and processed any device data associated with your Commercial ID, the tile will be replaced with the following summary:
|
||||
|
||||
|
||||
|
||||
|
||||
The summary details the total number of devices that Microsoft has received data from with your Commercial ID. It also provides the number of devices that need attention if any. Finally, it details the last point at which your Update Compliance workspace was refreshed.
|
||||
|
||||
## The Update Compliance workspace
|
||||
|
||||
|
||||
|
||||
|
||||
When you select this tile, you will be redirected to the Update Compliance workspace. The workspace is organized with the Overview blade providing a hub from which to navigate to different reports of your devices' data.
|
||||
|
||||
### Overview blade
|
||||
|
||||
|
||||
|
||||
|
||||
Update Compliance's overview blade summarizes all the data Update Compliance provides. It functions as a hub from which you can navigate to different sections. The total number of devices detected by Update Compliance is reported in the title of this blade. What follows is a distribution for all devices as to whether they are up to date on the following items:
|
||||
* Security updates: A device is up to date on quality updates whenever it has the latest applicable quality update installed. Quality updates are monthly cumulative updates that are specific to a version of Windows 10.
|
||||
|
||||
@ -57,7 +57,7 @@ With Windows Update for Business, you can set a device to be on either Windows I
|
||||
|
||||
Starting with Windows 10, version 1703, users can configure the branch readiness level for their device by using **Settings > Update & security > Windows Update > Advanced options**.
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>Users will not be able to change this setting if it was configured by policy.
|
||||
|
||||
@ -211,6 +211,6 @@ Log entries are written to the PowerShell pipeline as objects. To dump logs to a
|
||||
|
||||
Update Compliance provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
||||
|
||||
[  ](images/UC_workspace_DO_status.png#lightbox)
|
||||
[  ](images/UC_workspace_DO_status.png#lightbox)
|
||||
|
||||
For details, see [Delivery Optimization in Update Compliance](update-compliance-delivery-optimization.md).
|
||||
|
||||
@ -39,7 +39,7 @@ For information about setting up Delivery Optimization, including tips for the b
|
||||
|
||||
- Enterprise network throttling: new settings have been added in Group Policy and mobile device management (MDM) to control foreground and background throttling as absolute values (Maximum Background Download Bandwidth in (in KB/s)). These settings are also available in the Windows user interface:
|
||||
|
||||
|
||||
|
||||
|
||||
- Activity Monitor now identifies the cache server used for as the source for Microsoft Connected Cache. For more information about using Microsoft Connected Cache with Configuration Manager, see [Microsoft Connected Cache](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
|
||||
|
||||
|
||||
@ -51,12 +51,12 @@ As Table 1 shows, each combination of servicing channel and deployment group is
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | Build deployment rings for Windows 10 updates (this topic) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | Build deployment rings for Windows 10 updates (this topic) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -88,7 +88,7 @@ In this example, the deferral behavior for updates to Office and other non-Windo
|
||||
|
||||
For Windows 10, version 1607, organizations already managing their systems with a Configuration Manager solution can also have their devices configured for Windows Update for Business (i.e. setting deferral policies on those devices). Such devices will be visible in the Configuration Manager console, however they will appear with a detection state of **Unknown**.
|
||||
|
||||
|
||||
|
||||
|
||||
For more information, see [Integration with Windows Update for Business in Windows 10](/sccm/sum/deploy-use/integrate-windows-update-for-business-windows-10).
|
||||
|
||||
|
||||
@ -62,7 +62,7 @@ When using WSUS to manage updates on Windows client devices, start by configurin
|
||||
|
||||
3. Right-click **Your_Domain**, and then select **Create a GPO in this domain, and Link it here**.
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>In this example, the **Configure Automatic Updates** and **Intranet Microsoft Update Service Location** Group Policy settings are specified for the entire domain. This is not a requirement; you can target these settings to any security group by using Security Filtering or a specific OU.
|
||||
@ -75,13 +75,13 @@ When using WSUS to manage updates on Windows client devices, start by configurin
|
||||
|
||||
7. Right-click the **Configure Automatic Updates** setting, and then click **Edit**.
|
||||
|
||||
|
||||
|
||||
|
||||
8. In the **Configure Automatic Updates** dialog box, select **Enable**.
|
||||
|
||||
9. Under **Options**, from the **Configure automatic updating** list, select **3 - Auto download and notify for install**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
>[!IMPORTANT]
|
||||
> Use Regedit.exe to check that the following key is not enabled, because it can break Windows Store connectivity: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\DoNotConnectToWindowsUpdateInternetLocations
|
||||
@ -98,7 +98,7 @@ When using WSUS to manage updates on Windows client devices, start by configurin
|
||||
>[!NOTE]
|
||||
>The URL `http://CONTOSO-WSUS1.contoso.com:8530` in the following image is just an example. In your environment, be sure to use the server name and port number for your WSUS instance.
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>The default HTTP port for WSUS is 8530, and the default HTTP over Secure Sockets Layer (HTTPS) port is 8531. (The other options are 80 and 443; no other ports are supported.)
|
||||
@ -118,7 +118,7 @@ You can use computer groups to target a subset of devices that have specific qua
|
||||
|
||||
2. Go to *Server_Name*\Computers\All Computers, and then click **Add Computer Group**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Type **Ring 2 Pilot Business Users** for the name, and then click **Add**.
|
||||
|
||||
@ -146,7 +146,7 @@ When new computers communicate with WSUS, they appear in the **Unassigned Comput
|
||||
|
||||
2. Select both computers, right-click the selection, and then click **Change Membership**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the **Set Computer Group Membership** dialog box, select the **Ring 2 Pilot Business Users** deployment ring, and then click **OK**.
|
||||
|
||||
@ -164,7 +164,7 @@ Another way to add multiple computers to a deployment ring in the WSUS Administr
|
||||
|
||||
3. In the search results, select the computers, right-click the selection, and then click **Change Membership**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Select the **Ring 3 Broad IT** deployment ring, and then click **OK**.
|
||||
|
||||
@ -181,7 +181,7 @@ The WSUS Administration Console provides a friendly interface from which you can
|
||||
|
||||
1. Open the WSUS Administration Console, and go to *Server_Name*\Options, and then click **Computers**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. In the **Computers** dialog box, select **Use Group Policy or registry settings on computers**, and then click **OK**.
|
||||
|
||||
@ -205,7 +205,7 @@ Now that WSUS is ready for client-side targeting, complete the following steps t
|
||||
|
||||
5. Right-click the **WSUS – Client Targeting – Ring 4 Broad Business Users** GPO, and then click **Edit**.
|
||||
|
||||
|
||||
|
||||
|
||||
6. In the Group Policy Management Editor, go to Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update.
|
||||
|
||||
@ -215,7 +215,7 @@ Now that WSUS is ready for client-side targeting, complete the following steps t
|
||||
|
||||
9. In the **Target group name for this computer** box, type *Ring 4 Broad Business Users*. This is the name of the deployment ring in WSUS to which these computers will be added.
|
||||
|
||||
|
||||
|
||||
|
||||
> [!WARNING]
|
||||
> The target group name must match the computer group name.
|
||||
@ -232,7 +232,7 @@ Now you’re ready to deploy this GPO to the correct computer security group for
|
||||
|
||||
3. Under **Security Filtering**, remove the default **AUTHENTICATED USERS** security group, and then add the **Ring 4 Broad Business Users** group.
|
||||
|
||||
|
||||
|
||||
|
||||
The next time the clients in the **Ring 4 Broad Business Users** security group receive their computer policy and contact WSUS, they will be added to the **Ring 4 Broad Business Users** deployment ring.
|
||||
|
||||
@ -252,7 +252,7 @@ For clients that should have their feature updates approved as soon as they’re
|
||||
|
||||
3. In the **Add Rule** dialog box, select the **When an update is in a specific classification**, **When an update is in a specific product**, and **Set a deadline for the approval** check boxes.
|
||||
|
||||
|
||||
|
||||
|
||||
4. In the **Edit the properties** area, select **any classification**. Clear everything except **Upgrades**, and then click **OK**.
|
||||
|
||||
@ -266,7 +266,7 @@ For clients that should have their feature updates approved as soon as they’re
|
||||
|
||||
8. In the **Step 3: Specify a name** box, type **Windows 10 Upgrade Auto-approval for Ring 3 Broad IT**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
9. In the **Automatic Approvals** dialog box, click **OK**.
|
||||
|
||||
@ -301,7 +301,7 @@ To simplify the manual approval process, start by creating a software update vie
|
||||
|
||||
5. In the **Step 3: Specify a name** box, type **All Windows 10 Upgrades**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
Now that you have the **All Windows 10 Upgrades** view, complete the following steps to manually approve an update for the **Ring 4 Broad Business Users** deployment ring:
|
||||
|
||||
@ -309,21 +309,21 @@ Now that you have the **All Windows 10 Upgrades** view, complete the following s
|
||||
|
||||
2. Right-click the feature update you want to deploy, and then click **Approve**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the **Approve Updates** dialog box, from the **Ring 4 Broad Business Users** list, select **Approved for Install**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. In the **Approve Updates** dialog box, from the **Ring 4 Broad Business Users** list, click **Deadline**, click **One Week**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. If the **Microsoft Software License Terms** dialog box opens, click **Accept**.
|
||||
|
||||
If the deployment is successful, you should receive a successful progress report.
|
||||
|
||||
|
||||
|
||||
|
||||
6. In the **Approval Progress** dialog box, click **Close**.
|
||||
|
||||
@ -333,12 +333,12 @@ Now that you have the **All Windows 10 Upgrades** view, complete the following s
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or Deploy Windows 10 updates using Windows Server Update Services (this topic)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or Deploy Windows 10 updates using Windows Server Update Services (this topic)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|
||||
|
||||
|
||||
|
||||
@ -204,7 +204,7 @@ For the best experience with Windows Update, follow these guidelines:
|
||||
|
||||
Update Compliance provides a holistic view of operating system update compliance, update deployment progress, and failure troubleshooting for Windows 10 devices. This service uses diagnostic data including installation progress, Windows Update configuration, and other information to provide such insights, at no extra cost and without extra infrastructure requirements. Whether used with Windows Update for Business or other management tools, you can be assured that your devices are properly updated.
|
||||
|
||||
|
||||
|
||||
|
||||
For more information about Update Compliance, see [Monitor Windows Updates using Update Compliance](update-compliance-monitor.md).
|
||||
|
||||
@ -213,9 +213,9 @@ For more information about Update Compliance, see [Monitor Windows Updates using
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | Deploy updates using Windows Update for Business (this topic) </br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | Deploy updates using Windows Update for Business (this topic) </br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
@ -39,8 +39,8 @@ Two methods of peer-to-peer content distribution are available in Windows 10.
|
||||
|
||||
| Method | Windows Update | Windows Update for Business | WSUS | Configuration Manager |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Delivery Optimization |  |  |  |  |
|
||||
| BranchCache |  |  | |  |
|
||||
| Delivery Optimization |  |  |  |  |
|
||||
| BranchCache |  |  | |  |
|
||||
|
||||
> [!NOTE]
|
||||
> Microsoft Endpoint Manager has an additional feature called Client Peer Cache that allows peer-to-peer content sharing between clients you use Microsoft Endpoint Manager to manage, in the same Configuration Manager boundary Group. For more information, see [Client Peer Cache](/configmgr/core/plan-design/hierarchy/client-peer-cache).
|
||||
@ -88,12 +88,12 @@ At this point, the download is complete and the update is ready to be installed.
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | Optimize update delivery for Windows 10 updates (this topic) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)<br/>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)<br/>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | Optimize update delivery for Windows 10 updates (this topic) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)<br/>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)<br/>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -92,7 +92,7 @@ In Windows 10, rather than receiving several updates each month and trying to fi
|
||||
|
||||
**Figure 1**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -184,12 +184,12 @@ With all these options, which an organization chooses depends on the resources,
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | Learn about updates and servicing channels (this topic) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | Learn about updates and servicing channels (this topic) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|
||||
|
||||
|
||||
|
||||
@ -69,7 +69,7 @@ Administrators can use multiple ways to set active hours for managed devices:
|
||||
|
||||
To configure active hours using Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows Update** and open the **Turn off auto-restart for updates during active hours** policy setting. When the policy is enabled, you can set the start and end times for active hours.
|
||||
|
||||
|
||||
|
||||
|
||||
### Configuring active hours with MDM
|
||||
|
||||
@ -89,7 +89,7 @@ For a detailed description of these registry keys, see [Registry keys used to ma
|
||||
>[!NOTE]
|
||||
>To configure active hours manually on a single device, go to **Settings** > **Update & security** > **Windows Update** and select **Change active hours**.
|
||||
>
|
||||
>
|
||||
>
|
||||
|
||||
### Configuring active hours max range
|
||||
|
||||
@ -155,13 +155,13 @@ In the Group Policy editor, you will see a number of policy settings that pertai
|
||||
|
||||
| Policy | Applies to Windows 10 | Notes |
|
||||
| --- | --- | --- |
|
||||
| Turn off auto-restart for updates during active hours |  | Use this policy to configure active hours, during which the device will not be restarted. This policy has no effect if the **No auto-restart with logged on users for scheduled automatic updates installations** or **Always automatically restart at the scheduled time** policies are enabled. |
|
||||
| Always automatically restart at the scheduled time |  | Use this policy to configure a restart timer (between 15 and 180 minutes) that will start immediately after Windows Update installs important updates. This policy has no effect if the **No auto-restart with logged on users for scheduled automatic updates installations** policy is enabled. |
|
||||
| Specify deadline before auto-restart for update installation |  | Use this policy to specify how many days (between 2 and 14) an automatic restart can be delayed. This policy has no effect if the **No auto-restart with logged on users for scheduled automatic updates installations** or **Always automatically restart at the scheduled time** policies are enabled. |
|
||||
| No auto-restart with logged on users for scheduled automatic updates installations |  | Use this policy to prevent automatic restart when a user is logged on. This policy applies only when the **Configure Automatic Updates** policy is configured to perform scheduled installations of updates. <br>There is no equivalent MDM policy setting for Windows 10 Mobile. |
|
||||
| Re-prompt for restart with scheduled installations |  | |
|
||||
| Delay Restart for scheduled installations |  | |
|
||||
| Reschedule Automatic Updates scheduled installations |  | |
|
||||
| Turn off auto-restart for updates during active hours |  | Use this policy to configure active hours, during which the device will not be restarted. This policy has no effect if the **No auto-restart with logged on users for scheduled automatic updates installations** or **Always automatically restart at the scheduled time** policies are enabled. |
|
||||
| Always automatically restart at the scheduled time |  | Use this policy to configure a restart timer (between 15 and 180 minutes) that will start immediately after Windows Update installs important updates. This policy has no effect if the **No auto-restart with logged on users for scheduled automatic updates installations** policy is enabled. |
|
||||
| Specify deadline before auto-restart for update installation |  | Use this policy to specify how many days (between 2 and 14) an automatic restart can be delayed. This policy has no effect if the **No auto-restart with logged on users for scheduled automatic updates installations** or **Always automatically restart at the scheduled time** policies are enabled. |
|
||||
| No auto-restart with logged on users for scheduled automatic updates installations |  | Use this policy to prevent automatic restart when a user is logged on. This policy applies only when the **Configure Automatic Updates** policy is configured to perform scheduled installations of updates. <br>There is no equivalent MDM policy setting for Windows 10 Mobile. |
|
||||
| Re-prompt for restart with scheduled installations |  | |
|
||||
| Delay Restart for scheduled installations |  | |
|
||||
| Reschedule Automatic Updates scheduled installations |  | |
|
||||
|
||||
>[!NOTE]
|
||||
>You can only choose one path for restart behavior.
|
||||
|
||||
@ -32,12 +32,12 @@ The Semi-Annual Channel is the default servicing channel for all Windows 10 devi
|
||||
|
||||
| Windows 10 edition | Semi-Annual Channel | Long-Term Servicing Channel | Insider Program |
|
||||
| --- | --- | --- | --- |
|
||||
| Home |  |  |  |
|
||||
| Pro |  |  |  |
|
||||
| Enterprise |  |  |  |
|
||||
| Enterprise LTSB |  |  |  |
|
||||
| Pro Education |  |  |  |
|
||||
| Education |  |  |  |
|
||||
| Home |  |  |  |
|
||||
| Pro |  |  |  |
|
||||
| Enterprise |  |  |  |
|
||||
| Enterprise LTSB |  |  |  |
|
||||
| Pro Education |  |  |  |
|
||||
| Education |  |  |  |
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
@ -164,12 +164,12 @@ Administrators can disable the "Check for updates" option for users by enabling
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | Assign devices to servicing channels for Windows 10 updates (this topic) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | Assign devices to servicing channels for Windows 10 updates (this topic) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@ This helps simplify servicing. Devices with the original Release to Market (RTM)
|
||||
Windows publishes the new LCU packages for each Windows 10 version (1607, 1709, etc.) on the second Tuesday of each month. This package is classified as a required security update and contains contents from the previous LCU as well as new security, non-security, and Internet Explorer 11 (IE11) fixes. A reboot of the device might be required to complete installation of the update.
|
||||
|
||||
|
||||
|
||||
|
||||
*Figure 1.0 - High level cumulative update model*
|
||||
|
||||
Another benefit of the LCU model is fewer steps. Devices that have the original Release to Market (RTM) version of a release can install the most recent LCU to get up to date in one step, rather than having to install multiple updates with reboots after each.
|
||||
@ -67,7 +67,7 @@ Customers saw the LCU model used for Windows 10 as having packages that were too
|
||||
|
||||
The Monthly Rollup includes new non-security (if appropriate), security updates, Internet Explorer (IE) updates, and all updates from the previous month similar to the Windows 10 model. The Security-only package includes only new security updates for the month. This means that any security updates from any previous month are not included in current month's Security-Only Package. If a Security-Only update is missed, it is missed. Those updates will not appear in a future Security-Only update. Additionally, a cumulative package is offered for IE, which can be tested and installed separately, reducing the total update package size. The IE cumulative update includes both security and non-security fixes following the same model as Windows 10.
|
||||
|
||||
|
||||
|
||||
*Figure 2.0 - Legacy OS security-only update model*
|
||||
|
||||
Moving to the cumulative model for legacy OS versions continues to improve predictability of update quality. The Windows legacy environments which have fully updated machines with Monthly Rollups are running the same baseline against which all legacy OS version updates are tested. These include all of the updates (security and non-security) prior to and after October 2016. Many customer environments do not have all updates prior to this change installed, which leaves some continued fragmentation in the ecosystem. Further, customers who are installing Security-Only Updates and potentially doing so inconsistently are also more fragmented than Microsoft's test environments for legacy OS version. This remaining fragmentation results in issues like those seen when the September 2016 Servicing Stack Update (SSU) was needed for smooth installation of the August 2018 security update. These environments did not have the SSU applied previously.
|
||||
@ -99,7 +99,7 @@ Windows 10 version 1709:
|
||||
- (10B) October 9, 2018 Update Tuesday / B release includes all fixes included in 9B, all fixes in 9C and introduces new security fixes and IE updates. This update is qualified as "Required, Security" and requires a system reboot.
|
||||
All of these updates are cumulative and build on each other for Windows 10. This is in contrast to legacy OS versions, where the 9C release becomes part of the "Monthly Rollup," but not the "Security Only" update. In other words, a Window 7 SP1 9C update is part of the cumulative "Monthly Rollup" but not included in the "Security Only" update because the fixes are qualified as "non-security". This is an important variation to note on the two models.
|
||||
|
||||
|
||||
|
||||
*Figure 3.0 - Preview releases within the Windows 10 LCU model*
|
||||
|
||||
## Previews vs. on-demand releases
|
||||
|
||||
@ -25,7 +25,7 @@ ms.collection: m365initiative-coredeploy
|
||||
In the past, traditional Windows deployments tended to be large, lengthy, and expensive. Windows 10 offers a new approach to deploying both quality and feature updates, making the process much simpler and therefore the planning much more straightforward. With Windows as a service, the methodology around updating Windows has changed, moving away from major upgrades every few years to iterative updates twice per year. Each iteration contains a smaller subset of changes so that they won’t seem like substantial differences, like they do today. This image illustrates the level of effort needed for traditional Windows deployments versus servicing Windows 10 and how it is now spread evenly over time versus spiking every few years.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Windows 10 spreads the traditional deployment effort of a Windows upgrade, which typically occurred every few years, over smaller, continuous updates. With this change, you must approach the ongoing deployment and servicing of Windows differently. A strong Windows 10 deployment strategy begins with establishing a simple, repeatable process for testing and deploying each feature update. Here’s an example of what this process might look like:
|
||||
|
||||
@ -52,12 +52,12 @@ Each time Microsoft releases a Windows 10 feature update, the IT department shou
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | Prepare servicing strategy for Windows 10 updates (this topic) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|  | [Learn about updates and servicing channels](waas-overview.md) |
|
||||
|  | Prepare servicing strategy for Windows 10 updates (this topic) |
|
||||
|  | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) |
|
||||
|  | [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md) |
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)</br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](/mem/configmgr/osd/deploy-use/manage-windows-as-a-service) |
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -72,19 +72,19 @@ A Windows Update for Business administrator can defer or pause updates. You can
|
||||
|
||||
In this example, there are three rings for quality updates. The first ring ("pilot") has a deferral period of 0 days. The second ring ("fast") has a deferral of five days. The third ring ("slow") has a deferral of ten days.
|
||||
|
||||
|
||||
|
||||
|
||||
When the quality update is released, it is offered to devices in the pilot ring the next time they scan for updates.
|
||||
|
||||
##### Five days later
|
||||
The devices in the fast ring are offered the quality update the next time they scan for updates.
|
||||
|
||||
|
||||
|
||||
|
||||
##### Ten days later
|
||||
Ten days after the quality update is released, it is offered to the devices in the slow ring the next time they scan for updates.
|
||||
|
||||
|
||||
|
||||
|
||||
If no problems occur, all of the devices that scan for updates will be offered the quality update within ten days of its release, in three waves.
|
||||
|
||||
@ -92,11 +92,11 @@ If no problems occur, all of the devices that scan for updates will be offered t
|
||||
|
||||
In this example, some problem is discovered during the deployment of the update to the "pilot" ring.
|
||||
|
||||
|
||||
|
||||
|
||||
At this point, the IT administrator can set a policy to pause the update. In this example, the admin selects the **Pause quality updates** check box.
|
||||
|
||||
|
||||
|
||||
|
||||
Now all devices are paused from updating for 35 days. When the pause is removed, they will be offered the *next* quality update, which ideally will not have the same issue. If there is still an issue, the IT admin can pause updates again.
|
||||
|
||||
@ -153,21 +153,21 @@ When **Specify deadlines for automatic updates and restarts** is set (For Window
|
||||
|
||||
- After this period, the user receives this dialog:
|
||||
|
||||
|
||||
|
||||
|
||||
- If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur:
|
||||
|
||||
|
||||
|
||||
|
||||
- **If the restart is still pending after the deadline passes:**
|
||||
|
||||
- Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching:
|
||||
|
||||
|
||||
|
||||
|
||||
- Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification:
|
||||
|
||||
|
||||
|
||||
|
||||
#### I want to manage the notifications a user sees
|
||||
|
||||
|
||||
@ -83,19 +83,19 @@ A Windows Update for Business administrator can defer or pause updates. You can
|
||||
|
||||
In this example, there are three rings for quality updates. The first ring ("pilot") has a deferral period of 0 days. The second ring ("fast") has a deferral of five days. The third ring ("slow") has a deferral of ten days.
|
||||
|
||||
|
||||
|
||||
|
||||
When the quality update is released, it is offered to devices in the pilot ring the next time they scan for updates.
|
||||
|
||||
##### Five days later
|
||||
The devices in the fast ring are offered the quality update the next time they scan for updates.
|
||||
|
||||
|
||||
|
||||
|
||||
##### Ten days later
|
||||
Ten days after the quality update is released, it is offered to the devices in the slow ring the next time they scan for updates.
|
||||
|
||||
|
||||
|
||||
|
||||
If no problems occur, all of the devices that scan for updates will be offered the quality update within ten days of its release, in three waves.
|
||||
|
||||
@ -103,11 +103,11 @@ If no problems occur, all of the devices that scan for updates will be offered t
|
||||
|
||||
In this example, some problem is discovered during the deployment of the update to the "pilot" ring.
|
||||
|
||||
|
||||
|
||||
|
||||
At this point, the IT administrator can set a policy to pause the update. In this example, the admin selects the **Pause quality updates** check box.
|
||||
|
||||
|
||||
|
||||
|
||||
Now all devices are paused from updating for 35 days. When the pause is removed, they will be offered the *next* quality update, which ideally will not have the same issue. If there is still an issue, the IT admin can pause updates again.
|
||||
|
||||
@ -150,21 +150,21 @@ When **Specify deadlines for automatic updates and restarts** is set (For Window
|
||||
|
||||
- After this period, the user receives this dialog:
|
||||
|
||||
|
||||
|
||||
|
||||
- If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur:
|
||||
|
||||
|
||||
|
||||
|
||||
- **If the restart is still pending after the deadline passes:**
|
||||
|
||||
- Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching:
|
||||
|
||||
|
||||
|
||||
|
||||
- Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification:
|
||||
|
||||
|
||||
|
||||
|
||||
#### I want to manage the notifications a user sees
|
||||
|
||||
|
||||
@ -54,7 +54,7 @@ In this example, you use two security groups to manage your updates: **Ring 4 Br
|
||||
|
||||
2. Click the **Policy** workspace. In the middle pane, click **Configuration Policies**, and then click **Add** in the details pane.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the Create a New Policy Wizard, select **Windows\Custom Configuration (Windows 10 Desktop and Mobile and later)**, and then click **Create Policy**.
|
||||
|
||||
@ -69,7 +69,7 @@ In this example, you use two security groups to manage your updates: **Ring 4 Br
|
||||
>[!NOTE]
|
||||
>The OMA-URI settings are case sensitive, so be sure to review [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider) for the proper syntax.
|
||||
|
||||
|
||||
|
||||
|
||||
8. For this deployment ring, you're required to enable only CBB, so click **Save Policy**.
|
||||
|
||||
@ -119,7 +119,7 @@ You have now configured the **Ring 4 Broad business users** deployment ring to e
|
||||
|
||||
Three settings should appear in the **Windows Update for Business – CBB2** policy.
|
||||
|
||||
|
||||
|
||||
|
||||
20. Click **Save Policy**, and then click **Yes** at the **Deploy Policy** prompt.
|
||||
|
||||
@ -141,7 +141,7 @@ In this example, you use three security groups from Table 1 in [Build deployment
|
||||
|
||||
2. Click the **Policy** workspace. In the middle pane, click **Configuration Policies**, and then click **Add** in the details pane.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the Create a New Policy Wizard, select **Windows\Custom Configuration (Windows 10 Desktop and Mobile and later)**, and then click **Create Policy**.
|
||||
|
||||
@ -156,7 +156,7 @@ In this example, you use three security groups from Table 1 in [Build deployment
|
||||
>[!NOTE]
|
||||
>The OMA-URI settings are case sensitive, so be sure to review [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider) for the proper syntax.
|
||||
|
||||
|
||||
|
||||
|
||||
8. Because the **Ring 2 Pilot Business Users** deployment ring receives the CB feature updates after 28 days, in the **OMA-URI Settings** section, click **Add** to add another OMA-URI setting.
|
||||
|
||||
@ -164,7 +164,7 @@ In this example, you use three security groups from Table 1 in [Build deployment
|
||||
10. In the **OMA-URI** box, type **./Vendor/MSFT/Policy/Config/Update/DeferFeatureUpdatesPeriodInDays**.
|
||||
11. In the **Value** box, type **28**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
9. Click **Save Policy**.
|
||||
|
||||
@ -181,7 +181,7 @@ You have now configured the **Ring 2 Pilot Business Users** deployment ring to e
|
||||
|
||||
2. Click the **Policy** workspace. In the middle pane, click **Configuration Policies**, and then click **Add** in the details pane.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the Create a New Policy Wizard, select **Windows\Custom Configuration (Windows 10 Desktop and Mobile and later)**, and then click **Create Policy**.
|
||||
|
||||
@ -205,7 +205,7 @@ You have now configured the **Ring 2 Pilot Business Users** deployment ring to e
|
||||
|
||||
11. In the **Value** box, type **0**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
12. Click **Save Policy**.
|
||||
|
||||
@ -223,7 +223,7 @@ You have now configured the **Ring 4 Broad business users** deployment ring to r
|
||||
|
||||
2. Click the **Policy** workspace. In the middle pane, click **Configuration Policies**, and then click **Add** in the details pane.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the Create a New Policy Wizard, select **Windows\Custom Configuration (Windows 10 Desktop and Mobile and later)**, and then click **Create Policy**.
|
||||
|
||||
@ -255,7 +255,7 @@ You have now configured the **Ring 4 Broad business users** deployment ring to r
|
||||
|
||||
15. In the **Value** box, type **14**, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
16. Click **Save Policy**.
|
||||
|
||||
|
||||
@ -85,7 +85,7 @@ The time stamp indicates the time at which the logging occurs.
|
||||
- Messages are usually in chronological order, but there may be exceptions.
|
||||
- A pause during a sync can indicate a network problem, even if the scan succeeds.
|
||||
- A long pause near the end of a scan can indicate a supersedence chain issue.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Process ID and thread ID
|
||||
@ -93,7 +93,7 @@ The Process IDs and Thread IDs are random, and they can vary from log to log and
|
||||
- The first four hex digits are the process ID.
|
||||
- The next four hex digits are the thread ID.
|
||||
- Each component, such as the USO, Windows Update engine, COM API callers, and Windows Update installer handlers, has its own process ID.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Component name
|
||||
@ -106,7 +106,7 @@ Search for and identify the components that are associated with the IDs. Differe
|
||||
- DataStore - Caching update data locally
|
||||
- IdleTimer - Tracking active calls, stopping service
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### Update identifiers
|
||||
@ -117,7 +117,7 @@ There are different identifiers for the same update in different contexts. It's
|
||||
- Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service
|
||||
- Revision numbers are reused from one update to another (not a unique identifier).
|
||||
- The update ID and revision number are often shown together as "{GUID}.revision."
|
||||
|
||||
|
||||
|
||||
|
||||
##### Revision ID
|
||||
@ -141,7 +141,7 @@ There are different identifiers for the same update in different contexts. It's
|
||||
- Small integers that appear alongside an update ID are revision numbers
|
||||
- Large integers are typically revision IDs
|
||||
- Small integers (especially in Datastore) can be local IDs
|
||||
|
||||
|
||||
|
||||
## Windows Setup log files analysis using SetupDiag tool
|
||||
SetupDiag is a diagnostic tool that can be used for analysis of logs related to installation of Windows Updates. For detailed information, see [SetupDiag](../upgrade/setupdiag.md).
|
||||
@ -32,7 +32,7 @@ Use the following information to get started with Windows Update:
|
||||
## Unified Update Platform (UUP) architecture
|
||||
To understand the changes to the Windows Update architecture that UUP introduces let's start with some new key terms.
|
||||
|
||||
|
||||
|
||||
|
||||
- **Update UI** – The user interface to initiate Windows Update check and history. Available under **Settings --> Update & Security --> Windows Update**.
|
||||
- **Update Session Orchestrator (USO)**- A Windows OS component that orchestrates the sequence of downloading and installing various update types from Windows Update.
|
||||
|
||||
@ -93,11 +93,11 @@ Once the device is in the pending restart state, it will attempt to restart the
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
### Deadline with user engagement
|
||||
|
||||
@ -130,17 +130,17 @@ Before the deadline the device will be in two states: auto-restart period and en
|
||||
|
||||
Notification users get for quality update engaged deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update engaged deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ If you don't need a wave deployment and have a small set of devices to manage, w
|
||||
|Do not allow update deferral policies to cause scans against Windows Update|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not allow update deferral policies to cause scans against Windows Update|State: Disabled|
|
||||
|
||||
## Suggested configuration for a wave deployment
|
||||
|
||||
|
||||
|
||||
## Early validation and testing
|
||||
Depending on your organizational size and requirements you might be able to test feature updates earlier to identify if there are impacts to Line of Business applications. Our recommendation is to enroll a set of devices that are a good representation of your device ecosystem (for example, devices with accounting software or engineering software). Learn more about [different deployment rings](https://insider.windows.com/how-to-pc/#working-with-rings).
|
||||
|
||||
Reference in New Issue
Block a user