mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 12:53:38 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into updateseeker-7991583
This commit is contained in:
Meghan Stewart
@ -13,6 +13,8 @@
|
||||
items:
|
||||
- name: Set up Delivery Optimization for Windows
|
||||
href: waas-delivery-optimization-setup.md
|
||||
- name: Monitor Delivery Optimization for Windows
|
||||
href: waas-delivery-optimization-monitor.md
|
||||
- name: Configure Delivery Optimization settings using Microsoft Intune
|
||||
href: /mem/intune/configuration/delivery-optimization-windows
|
||||
- name: Resources for Delivery Optimization
|
||||
@ -36,11 +38,13 @@
|
||||
- name: Requirements
|
||||
href: mcc-enterprise-prerequisites.md
|
||||
- name: Deploy Microsoft Connected Cache
|
||||
href: mcc-enterprise-deploy.md
|
||||
href: mcc-enterprise-portal-deploy.md
|
||||
- name: Update or uninstall MCC
|
||||
href: mcc-enterprise-update-uninstall.md
|
||||
- name: Appendix
|
||||
href: mcc-enterprise-appendix.md
|
||||
- name: MCC for Enterprise and Education (early preview)
|
||||
href: mcc-enterprise-deploy.md
|
||||
- name: MCC for ISPs
|
||||
items:
|
||||
- name: MCC for ISPs Overview
|
||||
|
||||
@ -10,6 +10,7 @@ ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Using a proxy with Delivery Optimization
|
||||
|
||||
@ -10,6 +10,7 @@ ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Delivery Optimization client-service communication explained
|
||||
|
||||
BIN
windows/deployment/do/images/ent-mcc-deployment-complete.png
Normal file
BIN
windows/deployment/do/images/ent-mcc-deployment-complete.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
windows/deployment/do/images/ent-mcc-portal-create.png
Normal file
BIN
windows/deployment/do/images/ent-mcc-portal-create.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 144 KiB |
BIN
windows/deployment/do/images/ent-mcc-portal-resource.png
Normal file
BIN
windows/deployment/do/images/ent-mcc-portal-resource.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 96 KiB |
BIN
windows/deployment/do/images/ent-mcc-provisioning.png
Normal file
BIN
windows/deployment/do/images/ent-mcc-provisioning.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
@ -1,6 +1,7 @@
|
||||
---
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.date: 10/18/2022
|
||||
ms.prod: windows-client
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
author: amyzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-deploy
|
||||
|
||||
@ -41,10 +41,10 @@ landingContent:
|
||||
linkLists:
|
||||
- linkListType: how-to-guide
|
||||
links:
|
||||
- text: Delivery Optimization settings
|
||||
- text: Delivery Optimization recommended settings
|
||||
url: waas-delivery-optimization-setup.md#recommended-delivery-optimization-settings
|
||||
- text: Windows PowerShell for Delivery Optimization
|
||||
url: waas-delivery-optimization-setup.md#windows-powershell-cmdlets
|
||||
- text: Monitor Delivery Optimization for Windows
|
||||
url: waas-delivery-optimization-monitor.md
|
||||
- text: Troubleshoot Delivery Optimization
|
||||
url: waas-delivery-optimization-setup.md#troubleshooting
|
||||
- text: Delivery Optimization Frequently Asked Questions
|
||||
|
||||
@ -3,12 +3,13 @@ title: MCC for Enterprise and Education Overview
|
||||
manager: aaroncz
|
||||
description: Overview of Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.topic: article
|
||||
ms.date: 05/09/2023
|
||||
ms.technology: itpro-updates
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education Overview
|
||||
@ -37,9 +38,9 @@ Connected Cache (early preview) supports the following scenarios:
|
||||
|
||||
When clients download cloud-managed content, they use Delivery Optimization from the cache server installed on a Windows server or VM. Cloud-managed content includes the following types:
|
||||
|
||||
- Windows Update for Business: Windows feature and quality updates
|
||||
- Windows updates: Windows feature and quality updates
|
||||
- Office Click-to-Run apps: Microsoft 365 Apps and updates
|
||||
- Client apps: Microsoft Store apps and updates
|
||||
- Client apps: Intune, store apps, and updates
|
||||
- Endpoint protection: Windows Defender definition updates
|
||||
|
||||
For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).
|
||||
|
||||
@ -3,8 +3,9 @@ title: Appendix
|
||||
manager: aaroncz
|
||||
description: Appendix on Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -1,17 +1,18 @@
|
||||
---
|
||||
title: Deploying your cache node
|
||||
title: MCC for Enterprise and Education (early preview)
|
||||
manager: aaroncz
|
||||
description: How to deploy Microsoft Connected Cache (MCC) for Enterprise and Education cache node
|
||||
description: How to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
ms.collection: tier3
|
||||
---
|
||||
|
||||
# Deploying your cache node
|
||||
# Deploying your enterprise cache node
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -129,7 +130,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
|
||||
- Downloads, installs, and deploys EFLOW
|
||||
- Enables Microsoft Update so EFLOW can stay up to date
|
||||
- Creates a virtual machine
|
||||
- Enables the firewall and opens ports 80 and 22 for inbound and outbound traffic. Port 80 is used by MCC, and port 22 is used for SSH communications.
|
||||
- Enables the firewall and opens ports 80 for inbound and outbound traffic. Port 80 is used by MCC.
|
||||
- Configures Connected Cache tuning settings.
|
||||
- Creates the necessary *FREE* Azure resource - IoT Hub/IoT Edge.
|
||||
- Deploys the MCC container to server.
|
||||
|
||||
145
windows/deployment/do/mcc-enterprise-portal-deploy.md
Normal file
145
windows/deployment/do/mcc-enterprise-portal-deploy.md
Normal file
@ -0,0 +1,145 @@
|
||||
---
|
||||
title: Deploying your cache node
|
||||
manager: aaroncz
|
||||
description: How to deploy Microsoft Connected Cache (MCC) for Enterprise and Education cache node
|
||||
ms.prod: windows-client
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
ms.collection: tier3
|
||||
---
|
||||
|
||||
# Deploying your cache node
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
## Create the Microsoft Connected Cache resource
|
||||
|
||||
1. Navigate to Azure portal by using the [following link](https://aka.ms/mcc-enterprise-preview):
|
||||
> [!IMPORTANT]
|
||||
> You must access Azure portal using this link (https://aka.ms/mcc-enterprise-preview) in order to find the correct Microsoft Connected Cache resource.
|
||||
|
||||
|
||||
|
||||
1. In the search bar by **Get Started**, search for `Microsoft Connected Cache for Enterprise`.
|
||||
|
||||
1. Select **Create** to create your Microsoft Connected Cache resource. When prompted, choose the subscription, resource group, and location of your cache node. Also, enter a name for your cache node.
|
||||
1. The creation of the cache node may take a few minutes. After a successful creation, you'll see a “Deployment complete” page as below. Select **Go to resource**.
|
||||
|
||||
|
||||
## Create, provision, and deploy the cache node in Azure portal
|
||||
|
||||
To create, provision, and deploy the cache node in Azure portal, follow these steps:
|
||||
1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise (preview) resource.
|
||||
1. Navigate to **Settings** > **Cache nodes** and select **Create Cache Node**.
|
||||
1. Provide a name for your cache node and select **Create** to create your cache node.
|
||||
1. You may need to refresh to see the cache node. Select the cache node to configure it.
|
||||
1. Fill out the Basics and Storage fields. Enter the cache drive size in GB - this has a minimum size of 50 GB.
|
||||
|
||||
|
||||
Once complete, select **Save** at the top of the page and select **Provision server**.
|
||||
1. To deploy your cache node, download the installer by selecting **Download provisioning package**.
|
||||
1. Run the provided provisioning script - note that this is unique to each cache node.
|
||||
|
||||
## Verify proper functioning MCC server
|
||||
|
||||
#### Verify client side
|
||||
|
||||
Connect to the EFLOW VM and check if MCC is properly running:
|
||||
|
||||
1. Open PowerShell as an Administrator.
|
||||
2. Enter the following commands:
|
||||
|
||||
```powershell
|
||||
Connect-EflowVm
|
||||
sudo -s
|
||||
iotedge list
|
||||
```
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-connect-eflowvm.png" alt-text="Screenshot of running connect-EflowVm, sudo -s, and iotedge list from PowerShell." lightbox="./images/ent-mcc-connect-eflowvm.png":::
|
||||
|
||||
You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edgeHub but not MCC, try this command in a few minutes. The MCC container can take a few minutes to deploy.
|
||||
|
||||
#### Verify server side
|
||||
|
||||
For a validation of properly functioning MCC, execute the following command in the EFLOW VM or any device in the network. Replace <CacheServerIP\> with the IP address of the cache server.
|
||||
|
||||
```powershell
|
||||
wget [http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com]
|
||||
```
|
||||
|
||||
A successful test result will display a status code of 200 along with additional information.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-verify-server-ssh.png" alt-text="Screenshot of a successful wget with an SSH client." lightbox="./images/ent-mcc-verify-server-ssh.png":::
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png":::
|
||||
|
||||
Similarly, enter the following URL from a browser in the network:
|
||||
|
||||
`http://<YourCacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com`
|
||||
|
||||
If the test fails, see the [common issues](#common-issues) section for more information.
|
||||
|
||||
### Monitoring your metrics
|
||||
|
||||
To view the metrics associated with your cache nodes, navigate to the **Overview** > **Monitoring** tab within the Azure portal.
|
||||
|
||||
:::image type="content" source="./images/mcc-isp-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab.":::
|
||||
|
||||
You can choose to monitor the health and performance of all cache nodes or one at a time by using the dropdown menu. The **Egress bits per second** graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
|
||||
|
||||
If you're unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured.
|
||||
|
||||
|
||||
### Intune (or other management software) configuration for MCC
|
||||
|
||||
For an [Intune](/mem/intune/) deployment, create a **Configuration Profile** and include the Cache Host eFlow IP Address or FQDN:
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-intune-do.png" alt-text="Screenshot of Intune showing the Delivery Optimization cache server host names.":::
|
||||
|
||||
## Common Issues
|
||||
|
||||
#### PowerShell issues
|
||||
|
||||
If you're seeing errors similar to this error: `The term Get-<Something> isn't recognized as the name of a cmdlet, function, script file, or operable program.`
|
||||
|
||||
1. Ensure you're running Windows PowerShell version 5.x.
|
||||
|
||||
1. Run \$PSVersionTable and ensure you're running version 5.x and *not version 6 or 7*.
|
||||
|
||||
1. Ensure you have Hyper-V enabled:
|
||||
|
||||
**Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
|
||||
|
||||
**Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)
|
||||
|
||||
#### Verify Running MCC Container
|
||||
|
||||
Connect to the Connected Cache server and check the list of running IoT Edge modules using the following commands:
|
||||
|
||||
```bash
|
||||
Connect-EflowVm
|
||||
sudo iotedge list
|
||||
```
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-iotedge-list.png" alt-text="Screenshot of the iotedge list command." lightbox="./images/ent-mcc-iotedge-list.png":::
|
||||
|
||||
If edgeAgent and edgeHub containers are listed, but not "MCC", you may view the status of the IoT Edge security manager by using the command:
|
||||
|
||||
```bash
|
||||
sudo journalctl -u iotedge -f
|
||||
```
|
||||
|
||||
This command will provide the current status of the starting, stopping of a container, or the container pull and start.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-journalctl.png" alt-text="Screenshot of the output from journalctl -u iotedge -f." lightbox="./images/ent-mcc-journalctl.png":::
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> You should consult the IoT Edge troubleshooting guide ([Common issues and resolutions for Azure IoT Edge](/azure/iot-edge/troubleshoot)) for any issues you may encounter configuring IoT Edge, but we've listed a few issues that we encountered during our internal validation.
|
||||
@ -3,8 +3,9 @@ title: Requirements for Microsoft Connected Cache (MCC) for Enterprise and Educa
|
||||
manager: aaroncz
|
||||
description: Overview of requirements for Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -3,8 +3,9 @@ title: Update or uninstall Microsoft Connected Cache for Enterprise and Educatio
|
||||
manager: aaroncz
|
||||
description: Details on updating or uninstalling Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -3,8 +3,9 @@ title: Cache node configuration
|
||||
manager: aaroncz
|
||||
description: Configuring a cache node on Azure portal
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -9,6 +9,7 @@ ms.topic: article
|
||||
ms.date: 05/09/2023
|
||||
ms.technology: itpro-updates
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Create, configure, provision, and deploy the cache node in Azure portal
|
||||
@ -82,7 +83,7 @@ To set up and enable BGP routing for your cache node, follow the steps below:
|
||||
1. Under **Routing information**, select the routing method you would like to use. For more information, see [Client routing](#client-routing).
|
||||
|
||||
- If you choose **Manual routing**, enter your address range/CIDR blocks.
|
||||
- If you choose **BGP routing**, enter the ASN and IP addresses of the neighborship.
|
||||
- If you choose **BGP routing**, enter the ASN and IP addresses of the neighborship. Use your ASN, the one used to sign up for MCC. MCC will be automatically assigned as the same ASN as the neighbor.
|
||||
> [!NOTE]
|
||||
> **Prefix count** and **IP Space** will stop displaying `0` when BGP is successfully established.
|
||||
|
||||
|
||||
@ -2,8 +2,9 @@
|
||||
metadata:
|
||||
title: Microsoft Connected Cache Frequently Asked Questions
|
||||
description: The following article is a list of frequently asked questions for Microsoft Connected Cache.
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- highpri
|
||||
|
||||
@ -3,8 +3,9 @@ title: MCC for ISPs Overview
|
||||
manager: aaroncz
|
||||
description: Overview for Microsoft Connected Cache for ISPs
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 07/27/2023
|
||||
ms.technology: itpro-updates
|
||||
@ -31,9 +32,9 @@ Microsoft Connected Cache (preview) supports the following scenarios:
|
||||
|
||||
Microsoft Connected Cache uses Delivery Optimization as the backbone for Microsoft content delivery. Microsoft Connected Cache caches the following types:
|
||||
|
||||
- Windows Update for Business: Windows feature and quality updates
|
||||
- Windows updates: Windows feature and quality updates
|
||||
- Office Click-to-Run apps: Microsoft 365 Apps and updates
|
||||
- Client apps: Microsoft Store apps and updates
|
||||
- Client apps: Intune, store apps, and updates
|
||||
- Endpoint protection: Windows Defender definition updates
|
||||
- Xbox: Xbox Game Pass (PC only)
|
||||
|
||||
|
||||
@ -9,6 +9,7 @@ ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Operator sign up and service onboarding for Microsoft Connected Cache
|
||||
|
||||
@ -9,6 +9,7 @@ ms.topic: reference
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Support and troubleshooting
|
||||
|
||||
@ -3,8 +3,9 @@ title: Update or uninstall your cache node
|
||||
manager: aaroncz
|
||||
description: How to update or uninstall your cache node
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -3,8 +3,9 @@ title: Verify cache node functionality and monitor health and performance
|
||||
manager: aaroncz
|
||||
description: How to verify the functionality of a cache node
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -3,8 +3,9 @@ title: Enhancing cache performance
|
||||
manager: aaroncz
|
||||
description: How to enhance performance on a virtual machine used with Microsoft Connected Cache for ISPs
|
||||
ms.prod: windows-client
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: reference
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
|
||||
@ -4,9 +4,9 @@ description: Details on Microsoft Connected Cache (MCC) for Internet Service Pro
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.localizationpriority: medium
|
||||
author: amymzhou
|
||||
ms.author: amyzhou
|
||||
ms.reviewer: carmenf
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: how-to
|
||||
ms.date: 05/20/2022
|
||||
|
||||
@ -1,22 +1,36 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
title: Monitor Delivery Optimization
|
||||
description: How to monitor Delivery Optimization
|
||||
ms.collection:
|
||||
- tier3
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-deploy
|
||||
ms.topic: include
|
||||
ms.date: 07/31/2023
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: reference
|
||||
ms.date: 08/13/2023
|
||||
ms.localizationpriority: medium
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
<!--This file is shared by do/waas-delivery-optimization-setup.md and the update/update-compliance-get-started.md articles -->
|
||||
|
||||
## Monitor Delivery Optimization
|
||||
# Monitor Delivery Optimization
|
||||
|
||||
### Windows PowerShell cmdlets
|
||||
To monitor Delivery Optimization, you can use either the Windows Update for Business Delivery Optimization Report or Windows PowerShell cmdlets.
|
||||
|
||||
## Monitor with Windows Update for Business Delivery Optimization Report
|
||||
|
||||
Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache (MCC), HTTP source/CDN distribution over the past 28 days.
|
||||
|
||||
:::image type="content" source="../update/media/wufb-do-overview.png" alt-text="This screenshot shows the Windows Update for Business report, Delivery Optimization status in Update Compliance." lightbox= "../update/media/wufb-do-overview.png":::
|
||||
|
||||
For details, see [Windows Update for Business Delivery Optimization Report](/windows/deployment/update/wufb-reports-overview).
|
||||
|
||||
## Windows PowerShell cmdlets
|
||||
|
||||
**Starting in Windows 10, version 1703**, you can use new PowerShell cmdlets to check the performance of Delivery Optimization.
|
||||
|
||||
#### Analyze usage
|
||||
### Analyze usage
|
||||
|
||||
`Get-DeliveryOptimizationStatus` returns a real-time snapshot of all current Delivery Optimization jobs.
|
||||
|
||||
@ -112,7 +126,7 @@ Using the `-Verbose` option returns additional information:
|
||||
|
||||
Starting in Windows 10, version 1803, `Get-DeliveryOptimizationPerfSnapThisMonth` returns data similar to data from `Get-DeliveryOptimizationPerfSnap` but limited to the current calendar month.
|
||||
|
||||
#### Manage the Delivery Optimization cache
|
||||
### Manage the Delivery Optimization cache
|
||||
|
||||
**Starting in Windows 10, version 1903:**
|
||||
|
||||
@ -132,7 +146,7 @@ You can now "pin" files to keep them persistent in the cache, only with files th
|
||||
- `-IncludePinnedFiles` deletes all files that are pinned.
|
||||
- `-Force` deletes the cache with no prompts.
|
||||
|
||||
#### Work with Delivery Optimization logs
|
||||
### Work with Delivery Optimization logs
|
||||
|
||||
**Starting in Windows 10, version 2004:**
|
||||
|
||||
@ -183,18 +197,19 @@ The provider is listed as "Default Provider" if it's using the Delivery Optimiza
|
||||
|
||||
The cmdlet returns the following data:
|
||||
|
||||
- BatteryPctToSeed: Corresponds to the [DOMinBatteryPercentageAllowedToUpload](../waas-delivery-optimization-reference.md#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) policy.
|
||||
- BatteryPctToSeed: Corresponds to the [DOMinBatteryPercentageAllowedToUpload](waas-delivery-optimization-reference.md#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) policy.
|
||||
- WorkingDirectory: The local folder containing the Delivery Optimization cache.
|
||||
- MinTotalDiskSize: Corresponds to the [DOMinDiskSizeAllowedToPeer](../waas-delivery-optimization-reference.md#minimum-disk-size-allowed-to-use-peer-caching) policy.
|
||||
- MinTotalRAM: Corresponds to the [DOMinRAMAllowedToPeer](../waas-delivery-optimization-reference.md#minimum-ram-inclusive-allowed-to-use-peer-caching) policy.
|
||||
- VpnPeerCachingAllowed: Corresponds to the [DOAllowVPNPeerCaching](../waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy.
|
||||
- MinTotalDiskSize: Corresponds to the [DOMinDiskSizeAllowedToPeer](waas-delivery-optimization-reference.md#minimum-disk-size-allowed-to-use-peer-caching) policy.
|
||||
- MinTotalRAM: Corresponds to the [DOMinRAMAllowedToPeer](waas-delivery-optimization-reference.md#minimum-ram-inclusive-allowed-to-use-peer-caching) policy.
|
||||
- VpnPeerCachingAllowed: Corresponds to the [DOAllowVPNPeerCaching](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy.
|
||||
- VpnKeywords: List of keywords used to identify a VPN adapter.
|
||||
- SetHoursToLimitDownloadBackground: Corresponds to the [DOSetHoursToLimitBackgroundDownloadBandwidth](../waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth) policy.
|
||||
- SetHoursToLimitDownloadForeground: Corresponds to the [DOSetHoursToLimitForegroundDownloadBandwidth](../waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth) policy.
|
||||
- DownloadMode: Corresponds to the [DODownloadMode](../waas-delivery-optimization-reference.md#download-mode) policy.
|
||||
- DownBackLimitBps: Corresponds to the [DOMaxBackgroundDownloadBandwidth](../waas-delivery-optimization-reference.md#maximum-background-download-bandwidth-in-kbs) policy.
|
||||
- DownloadForegroundLimitBps: Corresponds to the [DOMaxForegroundDownloadBandwidth](../waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs) policy.
|
||||
- DownBackLimitPct: Corresponds to the [DOPercentageMaxBackgroundBandwidth](../waas-delivery-optimization-reference.md#maximum-background-download-bandwidth) policy.
|
||||
- DownloadForegroundLimitPct: Corresponds to the [DOPercentageMaxForegroundBandwidth](../waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth) policy.
|
||||
- MaxUploadRatePct: Corresponds to the [DOMaxUploadBandwidth](../waas-delivery-optimization-reference.md#max-upload-bandwidth) policy (deprecated in Windows 10, version 2004).
|
||||
- UploadLimitMonthlyGB: Corresponds to the [DOMonthlyUploadDataCap](../waas-delivery-optimization-reference.md#monthly-upload-data-cap) policy.
|
||||
- SetHoursToLimitDownloadBackground: Corresponds to the [DOSetHoursToLimitBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth) policy.
|
||||
- SetHoursToLimitDownloadForeground: Corresponds to the [DOSetHoursToLimitForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth) policy.
|
||||
- DownloadMode: Corresponds to the [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) policy.
|
||||
- DownBackLimitBps: Corresponds to the [DOMaxBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth-in-kbs) policy.
|
||||
- DownloadForegroundLimitBps: Corresponds to the [DOMaxForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs) policy.
|
||||
- DownBackLimitPct: Corresponds to the [DOPercentageMaxBackgroundBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth) policy.
|
||||
- DownloadForegroundLimitPct: Corresponds to the [DOPercentageMaxForegroundBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth) policy.
|
||||
- MaxUploadRatePct: Corresponds to the [DOMaxUploadBandwidth](waas-delivery-optimization-reference.md#max-upload-bandwidth) policy (deprecated in Windows 10, version 2004).
|
||||
- UploadLimitMonthlyGB: Corresponds to the [DOMonthlyUploadDataCap](waas-delivery-optimization-reference.md#monthly-upload-data-cap) policy.
|
||||
|
||||
@ -10,6 +10,7 @@ ms.topic: reference
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 07/31/2023
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# Delivery Optimization reference
|
||||
@ -323,7 +324,7 @@ The device can download from peers while on battery regardless of this policy.
|
||||
|
||||
MDM Setting: **DOCacheHost**
|
||||
|
||||
Set this policy to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma-separated, for example: myhost.somerandomhost.com,myhost2.somerandomhost.com,10.10.1.7. **By default, this policy has no value.**
|
||||
Set this policy to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma-separated, for example: myhost.somerandomhost.com,myhost2.somerandomhost.com,10.10.1.7. **By default, this policy has no value.** Delivery Optimization client will connect to the listed Microsoft Connected Cache servers in the order as they are listed. When multiple FQDNs or IP Addresses are listed, the Microsoft Connected Cache server priority order is determined based on the order as they are listed. If the first server fails, it will move the the next one. When the last server fails, it will fallback to the CDN.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> Any value will signify that the policy is set. For example, an empty string ("") isn't considered empty.
|
||||
|
||||
@ -110,17 +110,6 @@ Using MDM, go to **./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/** an
|
||||
|
||||
[Learn more](delivery-optimization-test.md) about Delivery Optimization testing scenarios.
|
||||
|
||||
<!--Using include file, waas-delivery-optimization-monitor.md, for shared content on DO monitoring-->
|
||||
[!INCLUDE [Monitor Delivery Optimization](includes/waas-delivery-optimization-monitor.md)]
|
||||
|
||||
### Monitor with Windows Update for Business Delivery Optimization Report
|
||||
|
||||
Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache (MCC), HTTP source/CDN distribution over the past 28 days.
|
||||
|
||||
:::image type="content" source="/windows/deployment/update/images/wufb-do-overview.png" alt-text="This screenshot shows the Windows Update for Business report, Delivery Optimization status in Update Compliance." lightbox="/windows/deployment/update/images/wufb-do-overview.png":::
|
||||
|
||||
For details, see [Windows Update for Business Delivery Optimization Report](../update/wufb-reports-overview.md).
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section summarizes common problems and some solutions to try.
|
||||
|
||||
@ -12,6 +12,7 @@ ms.collection:
|
||||
- highpri
|
||||
ms.topic: overview
|
||||
ms.date: 12/31/2017
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# What is Delivery Optimization?
|
||||
|
||||
@ -10,6 +10,7 @@ ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 05/09/2023
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# What is Microsoft Connected Cache?
|
||||
|
||||
@ -3,8 +3,9 @@ title: Optimize Windows update delivery
|
||||
description: Two methods of peer-to-peer content distribution are available, Delivery Optimization and BranchCache.
|
||||
ms.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
|
||||
@ -10,6 +10,7 @@ ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.collection: tier3
|
||||
ms.reviewer: mstewart
|
||||
---
|
||||
|
||||
# What's new in Delivery Optimization
|
||||
|
||||
@ -1,14 +1,19 @@
|
||||
---
|
||||
title: How to check Windows release health
|
||||
description: Check the release health status of Microsoft 365 services before you call support to see if there's an active service interruption.
|
||||
ms.date: 06/07/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.reviewer: mstewart
|
||||
ms.topic: how-to
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.collection:
|
||||
- tier2
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 06/07/2023
|
||||
---
|
||||
|
||||
# How to check Windows release health
|
||||
|
||||
@ -1,28 +1,28 @@
|
||||
---
|
||||
title: Create a deployment plan
|
||||
description: Devise the number of deployment rings you need and how you want to populate them
|
||||
description: Devise the number of deployment rings you need and how you want to populate each of the deployment rings.
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.collection:
|
||||
- tier2
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# Create a deployment plan
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
A "service management" mindset means that the devices in your organization fall into a continuum, with the software update process being constantly planned, deployed, monitored, and optimized. And once you use this process for feature updates, quality updates become a lightweight procedure that is simple and fast to execute, ultimately increasing velocity.
|
||||
|
||||
When you move to a service management model, you need effective ways of rolling out updates to representative groups of devices. We’ve found that a ring-based deployment works well for us at Microsoft and many other organizations across the globe. Deployment rings in Windows client are similar to the deployment groups most organizations constructed for previous major revision upgrades. They're simply a method to separate devices into a deployment timeline.
|
||||
When you move to a service management model, you need effective ways of rolling out updates to representative groups of devices. We've found that a ring-based deployment works well for us at Microsoft and many other organizations across the globe. Deployment rings in Windows client are similar to the deployment groups most organizations constructed for previous major revision upgrades. They're simply a method to separate devices into a deployment timeline.
|
||||
|
||||
At the highest level, each “ring” comprises a group of users or devices that receive a particular update concurrently. For each ring, IT administrators set criteria to control deferral time or adoption (completion) that should be met before deployment to the next broader ring of devices or users can occur.
|
||||
At the highest level, each ring comprises a group of users or devices that receive a particular update concurrently. For each ring, IT administrators set criteria to control deferral time or adoption (completion) that should be met before deployment to the next broader ring of devices or users can occur.
|
||||
|
||||
A common ring structure uses three deployment groups:
|
||||
|
||||
@ -31,7 +31,7 @@ A common ring structure uses three deployment groups:
|
||||
- Broad: Wide deployment
|
||||
|
||||
> [!NOTE]
|
||||
> Organizations often use different names for their “rings," for example:
|
||||
> Organizations often use different names for their rings, for example:
|
||||
> - First > Fast > Broad
|
||||
> - Canaries > Early Adopters > Users
|
||||
> - Preview > Broad > Critical
|
||||
@ -45,8 +45,8 @@ There are no definite rules for exactly how many rings to have for your deployme
|
||||
|
||||
There are basically two strategies for moving deployments from one ring to the next. One is service-based, the other project based.
|
||||
|
||||
- "Red button" (service based): Assumes that content is good until proven bad. Content flows until an issue is discovered, at which point the IT administrator presses the “red button” to stop further distribution.
|
||||
- Green button (project based): Assumes that content is bad until proven good. Once all validation has passed, the IT administrator presses the “green button” to push the content to the next ring.
|
||||
- "Red button" (service based): Assumes that content is good until proven bad. Content flows until an issue is discovered, at which point the IT administrator presses the "red button" to stop further distribution.
|
||||
- Green button (project based): Assumes that content is bad until proven good. Once all validation has passed, the IT administrator presses the "green button" to push the content to the next ring.
|
||||
|
||||
When it comes to deployments, having manual steps in the process usually impedes update velocity. A "red button" strategy is better when that is your goal.
|
||||
|
||||
@ -84,7 +84,7 @@ Analytics can help with defining a good Limited ring of representative devices a
|
||||
|
||||
### Who goes in the Limited ring?
|
||||
|
||||
The most important part of this phase is finding a representative sample of devices and applications across your network. If possible, all hardware and all applications should be represented. It's important that the people selected for this ring are using their devices regularly to generate the data you'll need to make a decision for broader deployment across your organization. The IT department, lab devices, and users with the most cutting-edge hardware usually don’t have the applications or device drivers that are truly a representative sample of your network.
|
||||
The most important part of this phase is finding a representative sample of devices and applications across your network. If possible, all hardware and all applications should be represented. It's important that the people selected for this ring are using their devices regularly to generate the data you'll need to make a decision for broader deployment across your organization. The IT department, lab devices, and users with the most cutting-edge hardware usually don't have the applications or device drivers that are truly a representative sample of your network.
|
||||
|
||||
|
||||
During your pilot and validate phases, you should focus on the following activities:
|
||||
@ -93,11 +93,11 @@ During your pilot and validate phases, you should focus on the following activit
|
||||
- Assess and act if issues are encountered.
|
||||
- Move forward unless blocked.
|
||||
|
||||
When you deploy to the Limited ring, you’ll be able to gather data and react to incidents happening in the environment, quickly addressing any issues that might arise. Ensure you monitor for sufficient adoption within this ring. Your Limited ring represents your organization across the board. When you achieve sufficient adoption, you can have confidence that your broader deployment will run more smoothly.
|
||||
When you deploy to the Limited ring, you'll be able to gather data and react to incidents happening in the environment, quickly addressing any issues that might arise. Ensure you monitor for sufficient adoption within this ring. Your Limited ring represents your organization across the board. When you achieve sufficient adoption, you can have confidence that your broader deployment will run more smoothly.
|
||||
|
||||
## Broad deployment
|
||||
|
||||
Once the devices in the Limited ring have had a sufficient stabilization period, it’s time for broad deployment across the network.
|
||||
Once the devices in the Limited ring have had a sufficient stabilization period, it's time for broad deployment across the network.
|
||||
|
||||
### Who goes in the Broad deployment ring?
|
||||
|
||||
|
||||
@ -1,19 +1,24 @@
|
||||
---
|
||||
title: Deploy drivers and firmware updates with Windows Update for Business deployment service.
|
||||
description: Use Windows Update for Business deployment service to deploy driver and firmware updates.
|
||||
title: Deploy drivers and firmware updates
|
||||
titlesuffix: Windows Update for Business deployment service
|
||||
description: Use Windows Update for Business deployment service to deploy driver and firmware updates to devices.
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 06/22/2023
|
||||
---
|
||||
|
||||
# Deploy drivers and firmware updates with Windows Update for Business deployment service
|
||||
<!--7260403, 7512398-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
The Windows Update for Business deployment service is used to approve and schedule software updates. The deployment service exposes its capabilities through the [Microsoft Graph API](/graph/use-the-api). You can call the API directly, through a [Graph SDK](/graph/sdks/sdks-overview), or integrate them with a management tool such as [Microsoft Intune](/mem/intune).
|
||||
|
||||
|
||||
@ -1,20 +1,24 @@
|
||||
---
|
||||
title: Deploy expedited updates with Windows Update for Business deployment service
|
||||
description: Use Windows Update for Business deployment service to deploy expedited updates.
|
||||
title: Deploy expedited updates
|
||||
titlesuffix: Windows Update for Business deployment service
|
||||
description: Learn how to use Windows Update for Business deployment service to deploy expedited updates to devices in your organization.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 02/14/2023
|
||||
---
|
||||
|
||||
# Deploy expedited updates with Windows Update for Business deployment service
|
||||
|
||||
<!--7512398-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
In this article, you will:
|
||||
> [!div class="checklist"]
|
||||
|
||||
@ -1,20 +1,24 @@
|
||||
---
|
||||
title: Deploy feature updates with Windows Update for Business deployment service.
|
||||
description: Use Windows Update for Business deployment service to deploy feature updates.
|
||||
title: Deploy feature updates
|
||||
titlesuffix: Windows Update for Business deployment service
|
||||
description: Use Windows Update for Business deployment service to deploy feature updates to devices in your organization.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 02/14/2023
|
||||
---
|
||||
|
||||
# Deploy feature updates with Windows Update for Business deployment service
|
||||
<!--7512398-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
The Windows Update for Business deployment service is used to approve and schedule software updates. The deployment service exposes its capabilities through the [Microsoft Graph API](/graph/use-the-api). You can call the API directly, through a [Graph SDK](/graph/sdks/sdks-overview), or integrate them with a management tool such as [Microsoft Intune](/mem/intune).
|
||||
|
||||
This article uses [Graph Explorer](/graph/graph-explorer/graph-explorer-overview) to walk through the entire process of deploying a feature update to clients. In this article, you will:
|
||||
|
||||
@ -1,20 +1,24 @@
|
||||
---
|
||||
title: Windows Update for Business deployment service
|
||||
description: Overview of deployment service to control approval, scheduling, and safeguarding of Windows updates
|
||||
title: Overview of the deployment service
|
||||
titlesuffix: Windows Update for Business deployment service
|
||||
description: Overview of deployment service to control approval, scheduling, and safeguarding of Windows updates with the deployment service.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: overview
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 02/14/2023
|
||||
---
|
||||
|
||||
# Windows Update for Business deployment service
|
||||
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
The Windows Update for Business deployment service is a cloud service within the Windows Update for Business product family. It's designed to work with your existing [Windows Update for Business](waas-manage-updates-wufb.md) policies and [Windows Update for Business reports](wufb-reports-overview.md). The deployment service provides control over the approval, scheduling, and safeguarding of updates delivered from Windows Update to managed devices. The service is privacy focused and backed by leading industry compliance certifications.
|
||||
|
||||
Windows Update for Business product family has three elements:
|
||||
|
||||
@ -1,20 +1,24 @@
|
||||
---
|
||||
title: Prerequisites for the Windows Update for Business deployment service
|
||||
description: Prerequisites for using the Windows Update for Business deployment service.
|
||||
title: Prerequisites for the deployment service
|
||||
titlesuffix: Windows Update for Business deployment service
|
||||
description: Prerequisites for using the Windows Update for Business deployment service for updating devices in your organization.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 02/14/2023
|
||||
---
|
||||
|
||||
# Windows Update for Business deployment service prerequisites
|
||||
<!--7512398-->
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
Before you begin the process of deploying updates with Windows Update for Business deployment service, ensure you meet the prerequisites.
|
||||
|
||||
## Azure and Azure Active Directory
|
||||
|
||||
@ -1,22 +1,24 @@
|
||||
---
|
||||
title: Troubleshoot the Windows Update for Business deployment service
|
||||
description: Solutions to common problems with the service
|
||||
title: Troubleshoot the deployment service
|
||||
titlesuffix: Windows Update for Business deployment service
|
||||
description: Solutions to commonly encountered problems when using the Windows Update for Business deployment service.
|
||||
ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.topic: article
|
||||
ms.technology: itpro-updates
|
||||
ms.date: 12/31/2017
|
||||
ms.topic: troubleshooting
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 02/14/2023
|
||||
---
|
||||
|
||||
|
||||
|
||||
# Troubleshoot the Windows Update for Business deployment service
|
||||
|
||||
***(Applies to: Windows 11 & Windows 10)***
|
||||
|
||||
This troubleshooting guide addresses the most common issues that IT administrators face when using the Windows Update for Business [deployment service](deployment-service-overview.md). For a general troubleshooting guide for Windows Update, see [Windows Update troubleshooting](/troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json).
|
||||
|
||||
## The device isn't receiving an update that I deployed
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Manage driver and firmware updates
|
||||
description: This article explains how you can manage driver and firmware updates with Windows Autopatch
|
||||
ms.date: 07/04/2023
|
||||
ms.date: 08/21/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -15,10 +15,7 @@ ms.collection:
|
||||
- tier1
|
||||
---
|
||||
|
||||
# Manage driver and firmware updates (public preview)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This feature is in **public preview**. The feature is being actively developed, and might not be complete. You can test and use these features in production environments and provide feedback.
|
||||
# Manage driver and firmware updates
|
||||
|
||||
You can manage and control your driver and firmware updates with Windows Autopatch. You can choose to receive driver and firmware updates automatically, or self-manage the deployment.
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2023
|
||||
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 08/08/2023
|
||||
ms.date: 08/21/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: whats-new
|
||||
@ -27,7 +27,8 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
|
||||
| Article | Description |
|
||||
| ----- | ----- |
|
||||
| [Exclude a device](../operate/windows-autopatch-exclude-device.md) | Renamed Deregister a device to [Exclude a device](../operate/windows-autopatch-exclude-device.md). Added the [Restore device](../operate/windows-autopatch-exclude-device.md#restore-a-device-or-multiple-devices-previously-excluded) feature |
|
||||
| [Manage driver and firmware updates](../operate/windows-autopatch-manage-driver-and-firmware-updates.md) | General Availability<ul><li>[MC661218](https://admin.microsoft.com/adminportal/home#/MessageCenter)</li></ul> |
|
||||
| [Exclude a device](../operate/windows-autopatch-exclude-device.md) | Renamed Deregister a device to [Exclude a device](../operate/windows-autopatch-exclude-device.md). Added the [Restore device](../operate/windows-autopatch-exclude-device.md#restore-a-device-or-multiple-devices-previously-excluded) feature <ul><li>[MC667662](https://admin.microsoft.com/adminportal/home#/MessageCenter)</li></ul> |
|
||||
| [Device alerts](../operate/windows-autopatch-device-alerts.md) | Added `'InstallSetupBlock'` to the [Alert resolutions section](../operate/windows-autopatch-device-alerts.md#alert-resolutions) |
|
||||
|
||||
## July 2023
|
||||
|
||||
Reference in New Issue
Block a user