mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into do-landing
This commit is contained in:
greg-lindsay
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Updates using forward and reverse differentials
|
||||
description: A technique to produce compact software updates optimized for any origin and destination revision pair
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Introduction to the Windows Insider Program for Business
|
||||
description: In this article, you'll learn about the Windows Insider Program for Business and why IT Pros should join.
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, General Availability Channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -37,7 +37,7 @@ Microsoft recommends that all organizations have at least a few devices enrolled
|
||||
|
||||
The Windows Insider Program doesn't replace General Availability 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
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Evaluate infrastructure and tools
|
||||
manager: laurawi
|
||||
description: Steps to make sure your infrastructure is ready to deploy updates
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows client updates, channels, and tools
|
||||
description: Brief summary of the kinds of Windows updates, the channels they are served through, and the tools for managing them
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
|
||||
BIN
windows/deployment/update/images/waas-mcc-diag-overview.png
Normal file
BIN
windows/deployment/update/images/waas-mcc-diag-overview.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
@ -2,7 +2,7 @@
|
||||
title: Define readiness criteria
|
||||
manager: laurawi
|
||||
description: Identify important roles and figure out how to classify apps
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Define update strategy
|
||||
description: Two examples of a calendar-based approach to consistent update installation
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Determine application readiness
|
||||
manager: laurawi
|
||||
description: How to test your apps to know which need attention prior to deploying an update
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Prepare to deploy Windows
|
||||
description: Final steps to get ready to deploy Windows, including preparing infrastructure, environment, applications, devices, network, capability, and users
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Monthly quality updates (Windows 10/11)
|
||||
description: Learn about Windows monthly quality updates to stay productive and protected.
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: greg-lindsay
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Update Baseline
|
||||
description: Use an update baseline to optimize user experience and meet monthly update goals
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, tools, group policy
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, tools, group policy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
|
||||
@ -3,7 +3,7 @@ title: Policies for update compliance, activity, and user experience
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Explanation and recommendations for settings
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
96
windows/deployment/update/waas-delivery-optimization-faq.md
Normal file
96
windows/deployment/update/waas-delivery-optimization-faq.md
Normal file
@ -0,0 +1,96 @@
|
||||
---
|
||||
title: Delivery Optimization Frequently Asked Questions
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
description: The following is a list of frequently asked questions for Delivery Optimization.
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: carmenf
|
||||
ms.localizationpriority: medium
|
||||
ms.author: carmenf
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Delivery Optimization Frequently Asked Questions
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
## Does Delivery Optimization work with WSUS?
|
||||
|
||||
Yes. Devices will obtain the update payloads from the WSUS server, but must also have an internet connection as they communicate with the Delivery Optimization cloud service for coordination.
|
||||
|
||||
## Which ports does Delivery Optimization use?
|
||||
|
||||
Delivery Optimization listens on port 7680 for requests from other peers by using TCP/IP. The service will register and open this port on the device. The port must be set to accept inbound traffic through your firewall. If you don't allow inbound traffic over port 7680, you can't use the peer-to-peer functionality of Delivery Optimization. However, devices can still successfully download by using HTTP or HTTPS traffic over port 80 (such as for default Windows Update data).
|
||||
|
||||
Delivery Optimization will use Teredo to create peer groups, which include devices across NATs (or any form of internal subnet that uses gateways or firewalls between subnets). For this to work, you must allow inbound TCP/IP traffic over port 3544. Look for a "NAT traversal" setting in your firewall to set this up.
|
||||
|
||||
Delivery Optimization also communicates with its cloud service by using HTTP/HTTPS over port 80.
|
||||
|
||||
## What are the requirements if I use a proxy?
|
||||
|
||||
For Delivery Optimization to successfully use the proxy, you should set up the proxy by using Windows proxy settings or Internet Explorer proxy settings. For details see [Using a proxy with Delivery Optimization](./delivery-optimization-proxy.md). Most content downloaded with Delivery Optimization uses byte range requests. Make sure your proxy allows byte range requests. For more information, see [Proxy requirements for Windows Update](/windows/deployment/update/windows-update-troubleshooting.md).
|
||||
|
||||
## What hostnames should I allow through my firewall to support Delivery Optimization?
|
||||
|
||||
For communication between clients and the Delivery Optimization cloud service: **\*.do.dsp.mp.microsoft.com**.
|
||||
|
||||
**For Delivery Optimization metadata**:
|
||||
|
||||
- *.dl.delivery.mp.microsoft.com
|
||||
- *.emdl.ws.microsoft.com
|
||||
|
||||
**For the payloads (optional)**:
|
||||
|
||||
- *.download.windowsupdate.com
|
||||
- *.windowsupdate.com
|
||||
|
||||
## Does Delivery Optimization use multicast?
|
||||
|
||||
No. It relies on the cloud service for peer discovery, resulting in a list of peers and their IP addresses. Client devices then connect to their peers to obtain download files over TCP/IP.
|
||||
|
||||
## How does Delivery Optimization deal with congestion on the router from peer-to-peer activity on the LAN?
|
||||
|
||||
Starting in Windows 10, version 1903, Delivery Optimization uses LEDBAT to relieve such congestion. For more information, see this post on the [Networking Blog](https://techcommunity.microsoft.com/t5/Networking-Blog/Windows-Transport-converges-on-two-Congestion-Providers-Cubic/ba-p/339819).
|
||||
|
||||
## How does Delivery Optimization handle VPNs?
|
||||
|
||||
Delivery Optimization attempts to identify VPNs by checking the network adapter type and details. A connection will be treated as a VPN if the adapter description contains certain keywords, such as "VPN" or "secure."
|
||||
|
||||
If the connection is identified as a VPN, Delivery Optimization will suspend uploads to other peers. However, you can allow uploads over a VPN by using the [Enable Peer Caching while the device connects via VPN](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy.
|
||||
|
||||
If you have defined a boundary group in Configuration Manager for VPN IP ranges, you can set the [DownloadMode](waas-delivery-optimization-reference.md#download-mode) policy to 0 for that boundary group, to ensure that there will be no peer-to-peer activity over the VPN. When the device is not connected using a VPN, it can still use peer-to-peer with the default of LAN.
|
||||
|
||||
With split tunneling, make sure to allow direct access to these endpoints:
|
||||
|
||||
Delivery Optimization service endpoint:
|
||||
|
||||
- `https://*.prod.do.dsp.mp.microsoft.com`
|
||||
|
||||
Delivery Optimization metadata:
|
||||
|
||||
- `http://emdl.ws.microsoft.com`
|
||||
- `http://*.dl.delivery.mp.microsoft.com`
|
||||
|
||||
Windows Update and Microsoft Store backend services and Windows Update and Microsoft Store payloads
|
||||
|
||||
- `http://*.windowsupdate.com`
|
||||
- `https://*.delivery.mp.microsoft.com`
|
||||
- `https://*.update.microsoft.com`
|
||||
- `https://tsfe.trafficshaping.dsp.mp.microsoft.com`
|
||||
|
||||
For more information about remote work if you're using Configuration Manager, see this post on the [Configuration Manager blog](https://techcommunity.microsoft.com/t5/configuration-manager-blog/managing-patch-tuesday-with-configuration-manager-in-a-remote/ba-p/1269444).
|
||||
|
||||
## How does Delivery Optimization handle networks where a public IP address is used in place of a private IP address?
|
||||
|
||||
Starting with Windows 10, version 1903 or later, Delivery Optimization no longer restricts connections between LAN peers to those using private IP addresses. If you use public IP addresses instead of private IP addresses, you can use Delivery Optimization in LAN mode.
|
||||
|
||||
> [!NOTE]
|
||||
> If you use public IP addresses instead of private in LAN mode, the bytes downloaded from or uploaded to LAN peers with public IP addresses might be reported as coming from Internet peers.
|
||||
58
windows/deployment/update/waas-microsoft-connected-cache.md
Normal file
58
windows/deployment/update/waas-microsoft-connected-cache.md
Normal file
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: What is Microsoft Connected Cache?
|
||||
manager: dougeby
|
||||
description: This article provides information about Microsoft Connected Cache, a software-only caching solution.
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: carmenf
|
||||
ms.localizationpriority: medium
|
||||
ms.author: carmenf
|
||||
ms.collection:
|
||||
- M365-modern-desktop
|
||||
- m365initiative-coredeploy
|
||||
- highpri
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# What is Microsoft Connected Cache?
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many bare-metal servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune.
|
||||
|
||||
Microsoft Connected Cache is a hybrid (mix of on-prem and cloud resources) SaaS solution built as an Azure IoT Edge module and Docker compatible Linux container deployed to your Windows devices. The Delivery Optimization team chose IoT Edge for Linux on Windows (EFLOW) as a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. Microsoft Connected Cache will be a Linux IoT Edge module running on the Windows Host OS.
|
||||
|
||||
Even though your Microsoft Connected Cache scenario is not related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs several functions important to manage Microsoft Connected Cache on your edge device:
|
||||
|
||||
1. Installs and updates Microsoft Connected Cache on your edge device.
|
||||
2. Maintains Azure IoT Edge security standards on your edge device.
|
||||
3. Ensures that Microsoft Connected Cache is always running.
|
||||
4. Reports Microsoft Connected Cache health and usage to the cloud for remote monitoring.
|
||||
|
||||
To deploy a functional Microsoft Connected Cache to your device, you must obtain the necessary keys to provision the Connected Cache instance that communicates with Delivery Optimization services, and enable the device to cache and deliver content. The architecture of Microsoft Connected Cache is described below.
|
||||
|
||||
For more details information on Azure IoT Edge, please see the Azure IoT Edge [documentation](/azure/iot-edge/about-iot-edge).
|
||||
|
||||
## How Microsoft Connected Cache Works
|
||||
|
||||
1. The Azure Management Portal is used to create Microsoft Connected Cache nodes.
|
||||
2. The Microsoft Connected Cache container is deployed and provisioned to the server using the installer provided in the portal.
|
||||
3. Client policy is set in your management solution to point to the IP address or FQDN of the cache server.
|
||||
4. Microsoft end-user devices make range requests for content from the Microsoft Connected Cache node.
|
||||
5. The Microsoft Connected Cache node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
|
||||
6. Subsequent requests from end-user devices for content will now come from cache.
|
||||
7. If the Microsoft Connected Cache node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
|
||||
|
||||
See the following diagram.
|
||||
|
||||
|
||||
|
||||
## Also see
|
||||
|
||||
[Introducing Microsoft Connected Cache](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898)
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Overview of Windows as a service
|
||||
description: Windows as a service is a way to build, deploy, and service Windows. Learn how Windows as a service works.
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Quick guide to Windows as a service (Windows 10)
|
||||
description: In Windows 10, Microsoft has streamlined servicing to make operating system updates simpler to test, manage, and deploy.
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, tools
|
||||
keywords: updates, servicing, current, deployment, General Availability Channel, General Availability Channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
|
||||
Reference in New Issue
Block a user