Merge branch 'main' into v-smandalika-5694287-B12
@ -19331,6 +19331,36 @@
|
||||
"source_path": "windows/whats-new/windows-11-whats-new.md",
|
||||
"redirect_url": "/windows/whats-new/windows-11-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/waas-delivery-optimization.md",
|
||||
"redirect_url": "/windows/deployment/do/waas-delivery-optimization",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/delivery-optimization-proxy.md",
|
||||
"redirect_url": "/windows/deployment/do/delivery-optimization-proxy",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/delivery-optimization-workflow.md",
|
||||
"redirect_url": "/windows/deployment/do/delivery-optimization-workflow",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/waas-delivery-optimization-reference.md",
|
||||
"redirect_url": "/windows/deployment/do/waas-delivery-optimization-reference",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/waas-delivery-optimization-setup.md",
|
||||
"redirect_url": "/windows/deployment/do/waas-delivery-optimization-setup",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/waas-optimize-windows-10.md",
|
||||
"redirect_url": "/windows/deployment/do/waas-optimize-windows-10",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
@ -90,6 +90,8 @@ The data type is string.
|
||||
Expected value:
|
||||
Set and Execute are functionality equivalent, and each accepts a `Collection` XML snippet (as a string) describing what data to gather and where to upload it. The results are zipped and uploaded to the specified SasUrl. The zipped filename format is "DiagLogs-{ComputerName}-YYYYMMDDTHHMMSSZ.zip".
|
||||
|
||||
With Windows 10 KB5011543, Windows 11 KB5011563 we have added support for an additional element which will determine whether the output file generated by the CSP is a flattened folder structure, instead of having individual folders for each directive in the XML.
|
||||
|
||||
The following is an example of a `Collection` XML.
|
||||
|
||||
``` xml
|
||||
@ -104,6 +106,7 @@ The following is an example of a `Collection` XML.
|
||||
<Command>%windir%\system32\mdmdiagnosticstool.exe -out %ProgramData%\temp\</Command>
|
||||
<FoldersFiles>%ProgramData%\temp\*.*</FoldersFiles>
|
||||
<Events>Application</Events>
|
||||
<OutputFileFormat>Flattened</OutputFileFormat>
|
||||
</Collection>
|
||||
|
||||
```
|
||||
@ -176,6 +179,11 @@ The SasUrl value is the target URI to which the CSP uploads the zip file contain
|
||||
- .evtx
|
||||
- .etl
|
||||
|
||||
- **OutputFileFormat**
|
||||
- Flattens folder structure, instead of having individual folders for each directive in the XML.
|
||||
- The value “Flattened” is the only supported value for the OutputFileFormat. If the OutputFileFormat is absent in the XML, or if explicitly set to something other than Flattened, it will leave the file structure in old structure.
|
||||
|
||||
|
||||
<a href="" id="diagnosticarchive-archiveresults"></a>**DiagnosticArchive/ArchiveResults**
|
||||
Added in version 1.4 of the CSP in Windows 10, version 1903. This policy setting displays the results of the last archive run.
|
||||
|
||||
@ -367,6 +375,7 @@ Added in version 1.4 of the CSP in Windows 10, version 1903. Dynamic node to rep
|
||||
|
||||
Supported operations are Add, Delete, and Get.
|
||||
|
||||
|
||||
Add **Channel**
|
||||
``` xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
|
@ -66,7 +66,7 @@ Installation date of the application. Value type is string. Supported operation
|
||||
<a href="" id="msi-productid-downloadinstall"></a>**MSI/*ProductID*/DownloadInstall**
|
||||
Executes the download and installation of the application. Value type is string. Supported operations are Execute and Get.
|
||||
|
||||
In Windows 10, version 1703 service release, a new tag \<DownloadFromAad\> was added to the \<Enforcement\> section of the XML. The default value is 0 (do not send token). This tag is optional and needs to be set to 1 in case the server wants the download URL to get the AADUserToken.
|
||||
In Windows 10, version 1703 service release, a new tag \<DownloadFromAad\> was added to the \<Enforcement\> section of the XML. The default value is 0 (do not send token). This tag is optional and needs to be set to 1 in case the server wants the download URL to get the AADUserToken.\<TimeOut\> 0 will set the timeout to infinite.
|
||||
|
||||
Here is an example:
|
||||
|
||||
@ -112,7 +112,7 @@ Value type is string. Supported operation is Get.
|
||||
Added in the March service release of Windows 10, version 1607.
|
||||
|
||||
<a href="" id="msi-upgradecode"></a>**MSI/UpgradeCode/_Guid_**
|
||||
Added in the March service release of Windows 10, version 1607. A gateway (or device management server) uses this method to detect matching upgrade MSI product when a Admin wants to update an existing MSI app. If the same upgrade product is installed, then the update is allowed.
|
||||
Added in the March service release of Windows 10, version 1607. A gateway (or device management server) uses this method to detect matching upgrade MSI product when an Admin wants to update an existing MSI app. If the same upgrade product is installed, then the update is allowed.
|
||||
|
||||
Value type is string. Supported operation is Get.
|
||||
|
||||
@ -261,7 +261,7 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
|Name|Description|
|
||||
|--- |--- |
|
||||
|Add|This is required to precede the Exec command.<li>CmdID - Input value used to reference the request. Responses includes this value, which can be use to match the request and response.<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.|
|
||||
|Add|This is required to precede the Exec command.<li>CmdID - Input value used to reference the request. Responses include this value, which can be used to match the request and response.<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.|
|
||||
|Exec|The Exec node includes the parameters and properties requires to locate, download, validate and perform product installation.<li>CmdID - Input value used to reference the request. Responses will include this value which can be used to match request and response.<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.<li>Data - The Data node contains an embedded XML, of type “MsiInstallJob”<li>MsiInstallJob - Contains all information required for the successful download, validation and execution of the MSI installation process (see section at the end of this document for details on this embedded data object).|
|
||||
</table>
|
||||
|
||||
@ -370,7 +370,7 @@ Here is an example of a common response to a request
|
||||
## How to determine which installation context to use for an MSI package
|
||||
|
||||
|
||||
The following tables shows how app targeting and MSI package type (per-user, per machine, or dual mode) are installed in the client.
|
||||
The following tables show how app targeting and MSI package type (per-user, per machine, or dual mode) are installed in the client.
|
||||
|
||||
For Intune standalone environment, the MSI package will determine the MSI execution context.
|
||||
|
||||
|
@ -47,12 +47,12 @@
|
||||
- name: Define your servicing strategy
|
||||
href: update/plan-define-strategy.md
|
||||
- name: Delivery Optimization for Windows client updates
|
||||
href: update/waas-delivery-optimization.md
|
||||
href: do/waas-delivery-optimization.md
|
||||
items:
|
||||
- name: Using a proxy with Delivery Optimization
|
||||
href: update/delivery-optimization-proxy.md
|
||||
href: do/delivery-optimization-proxy.md
|
||||
- name: Delivery Optimization client-service communication
|
||||
href: update/delivery-optimization-workflow.md
|
||||
href: do/delivery-optimization-workflow.md
|
||||
- name: Windows 10 deployment considerations
|
||||
href: planning/windows-10-deployment-considerations.md
|
||||
- name: Windows 10 infrastructure requirements
|
||||
@ -83,7 +83,7 @@
|
||||
- name: Update Baseline
|
||||
href: update/update-baseline.md
|
||||
- name: Set up Delivery Optimization for Windows client updates
|
||||
href: update/waas-delivery-optimization-setup.md
|
||||
href: do/index.yml
|
||||
- name: Configure BranchCache for Windows client updates
|
||||
href: update/waas-branchcache.md
|
||||
- name: Prepare your deployment tools
|
||||
@ -185,7 +185,7 @@
|
||||
- name: Monitor Windows client updates
|
||||
items:
|
||||
- name: Monitor Delivery Optimization
|
||||
href: update/waas-delivery-optimization-setup.md#monitor-delivery-optimization
|
||||
href: do/waas-delivery-optimization-setup.md#monitor-delivery-optimization
|
||||
- name: Monitor Windows Updates
|
||||
items:
|
||||
- name: Monitor Windows Updates with Update Compliance
|
||||
@ -283,7 +283,7 @@
|
||||
- name: Additional Windows Update settings
|
||||
href: update/waas-wu-settings.md
|
||||
- name: Delivery Optimization reference
|
||||
href: update/waas-delivery-optimization-reference.md
|
||||
href: do/waas-delivery-optimization-reference.md
|
||||
- name: Windows client in S mode
|
||||
href: s-mode.md
|
||||
- name: Switch to Windows client Pro or Enterprise from S mode
|
||||
|
@ -72,7 +72,7 @@ Windows PowerShell cmdlets for Delivery Optimization have been improved:
|
||||
- **Get-DeliveryOptimizationLogAnalysis** is a new cmdlet that provides a summary of the activity in your DO log (# of downloads, downloads from peers, overall peer efficiency). Use the **-ListConnections** option to for in-depth look at peer-to-peer connections.
|
||||
- **Enable-DeliveryOptimizationVerboseLogs** is a new cmdlet that enables a greater level of logging detail to assist in troubleshooting.
|
||||
|
||||
Additional improvements in [Delivery Optimization](./update/waas-delivery-optimization.md) include:
|
||||
Additional improvements in [Delivery Optimization](./do/waas-delivery-optimization.md) include:
|
||||
- Enterprise network [throttling is enhanced](/windows-insider/archive/new-for-business#new-download-throttling-options-for-delivery-optimization-build-18917) to optimize foreground vs. background throttling.
|
||||
- Automatic cloud-based congestion detection is available for PCs with cloud service support.
|
||||
- Improved peer efficiency for enterprises and educational institutions with complex networks is enabled with [new policies](/windows/client-management/mdm/policy-csp-deliveryoptimization). This now supports Microsoft 365 Apps for enterprise updates and Intune content, with Microsoft Endpoint Manager content coming soon!
|
||||
|
42
windows/deployment/do/TOC.yml
Normal file
@ -0,0 +1,42 @@
|
||||
- name: Delivery Optimization for Windows client
|
||||
href: index.yml
|
||||
items:
|
||||
- name: Get started
|
||||
items:
|
||||
- name: What is Delivery Optimization
|
||||
href: waas-delivery-optimization.md
|
||||
- name: What's new
|
||||
href: whats-new-do.md
|
||||
|
||||
|
||||
|
||||
- name: Configure Delivery Optimization
|
||||
items:
|
||||
- name: Configure Windows Clients
|
||||
items:
|
||||
- name: Windows Delivery Optimization settings
|
||||
href: waas-delivery-optimization-setup.md#recommended-delivery-optimization-settings
|
||||
- name: Configure Microsoft Endpoint Manager
|
||||
items:
|
||||
- name: Delivery Optimization settings in Microsoft Intune
|
||||
href: /mem/intune/configuration/delivery-optimization-windows
|
||||
|
||||
- name: Microsoft Connected Cache
|
||||
items:
|
||||
- name: MCC overview
|
||||
href: waas-microsoft-connected-cache.md
|
||||
- name: MCC for Enterprise and Education
|
||||
href: mcc-enterprise.md
|
||||
- name: MCC for ISPs
|
||||
href: mcc-isp.md
|
||||
|
||||
- name: Resources
|
||||
items:
|
||||
- name: Set up Delivery Optimization for Windows
|
||||
href: waas-delivery-optimization-setup.md
|
||||
- name: Delivery Optimization reference
|
||||
href: waas-delivery-optimization-reference.md
|
||||
- name: Delivery Optimization client-service communication
|
||||
href: delivery-optimization-workflow.md
|
||||
- name: Using a proxy with Delivery Optimization
|
||||
href: delivery-optimization-proxy.md
|
@ -6,9 +6,9 @@ keywords: updates, downloads, network, bandwidth
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: jaimeo
|
||||
author: carmenf
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.author: carmenf
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
@ -29,12 +29,12 @@ This workflow allows Delivery Optimization to securely and efficiently deliver r
|
||||
2. The authenticity of the content metadata file itself is verified prior to any content being downloaded using a hash that is obtained via an SSL channel from the Delivery Optimization service. The same channel is used to ensure the content is curated and authorized to leverage peer-to-peer.
|
||||
3. When Delivery Optimization pulls a certain piece of the hash from another peer, it verifies the hash against the known hash in the content metadata file.
|
||||
4. If a peer provides an invalid piece, that piece is discarded. When a peer sends multiple bad pieces, it's banned and will no longer be used as a source by the Delivery Optimization client performing the download.
|
||||
5. If Delivery Optimization is unable to obtain the content metadata file, or if the verification of the hash file itself fails, the download will fall back to “simple mode” (pulling content only from an HTTP source) and peer-to-peer won't be allowed.
|
||||
5. If Delivery Optimization is unable to obtain the content metadata file, or if the verification of the hash file itself fails, the download will fall back to "simple mode” (pulling content only from an HTTP source) and peer-to-peer won't be allowed.
|
||||
6. Once downloading is complete, Delivery Optimization uses all retrieved pieces of the content to put the file together. At that point, the Delivery Optimization caller (for example, Windows Update) checks the entire file to verify the signature prior to installing it.
|
||||
|
||||
## Delivery Optimization service endpoint and data information
|
||||
|
||||
|Endpoint hostname|Port|Name|Description|Data sent from the computer to the endpoint
|
||||
|Endpoint hostname | Port|Name|Description|Data sent from the computer to the endpoint
|
||||
|--------------------------------------------|--------|---------------|-----------------------|------------------------|
|
||||
| geover-prod.do.dsp.mp.microsoft.com <br> geo-prod.do.dsp.mp.microsoft.com <br> geo.prod.do.dsp.mp.microsoft.com <br> geover.prod.do.dsp.mp.microsoft.com | 443 | Geo | Service used to identify the location of the device in order to direct it to the nearest data center. | **Profile**: The device type (for example, PC or Xbox) <br> **doClientVersion**: The version of the DoSvc client <br> **groupID**: Group the device belongs to (set with DownloadMode = '2' (Group download mode) + groupID group policy / MDM policies) |
|
||||
| kv\*.prod.do.dsp.mp.microsoft.com | 443| KeyValue | Bootstrap service provides endpoints for all other services as well as device configs. | **countryCode**: The country the client is connected from <br> **doClientVersion**: The version of the DoSvc client <br> **Profile**: The device type (for example, PC or Xbox) <br> **eId**: Client grouping Id <br> **CacheHost**: Cache host id |
|
BIN
windows/deployment/do/images/UC_workspace_DO_status.png
Normal file
After Width: | Height: | Size: 57 KiB |
BIN
windows/deployment/do/images/backicon.png
Normal file
After Width: | Height: | Size: 304 B |
BIN
windows/deployment/do/images/checklistbox.gif
Normal file
After Width: | Height: | Size: 877 B |
BIN
windows/deployment/do/images/checklistdone.png
Normal file
After Width: | Height: | Size: 330 B |
BIN
windows/deployment/do/images/checkmark.png
Normal file
After Width: | Height: | Size: 20 KiB |
BIN
windows/deployment/do/images/crossmark.png
Normal file
After Width: | Height: | Size: 20 KiB |
BIN
windows/deployment/do/images/doneicon.png
Normal file
After Width: | Height: | Size: 410 B |
BIN
windows/deployment/do/images/emcc01.png
Normal file
After Width: | Height: | Size: 447 KiB |
BIN
windows/deployment/do/images/emcc02.png
Normal file
After Width: | Height: | Size: 27 KiB |
BIN
windows/deployment/do/images/emcc03.png
Normal file
After Width: | Height: | Size: 45 KiB |
BIN
windows/deployment/do/images/emcc04.png
Normal file
After Width: | Height: | Size: 79 KiB |
BIN
windows/deployment/do/images/emcc05.png
Normal file
After Width: | Height: | Size: 132 KiB |
BIN
windows/deployment/do/images/emcc06.png
Normal file
After Width: | Height: | Size: 21 KiB |
BIN
windows/deployment/do/images/emcc07.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
windows/deployment/do/images/emcc08.png
Normal file
After Width: | Height: | Size: 36 KiB |
BIN
windows/deployment/do/images/emcc09.5.png
Normal file
After Width: | Height: | Size: 61 KiB |
BIN
windows/deployment/do/images/emcc09.png
Normal file
After Width: | Height: | Size: 109 KiB |
BIN
windows/deployment/do/images/emcc10.png
Normal file
After Width: | Height: | Size: 44 KiB |
BIN
windows/deployment/do/images/emcc11.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
windows/deployment/do/images/emcc12.png
Normal file
After Width: | Height: | Size: 32 KiB |
BIN
windows/deployment/do/images/emcc13.png
Normal file
After Width: | Height: | Size: 66 KiB |
BIN
windows/deployment/do/images/emcc14.png
Normal file
After Width: | Height: | Size: 845 KiB |
BIN
windows/deployment/do/images/emcc15.png
Normal file
After Width: | Height: | Size: 144 KiB |
BIN
windows/deployment/do/images/emcc16.png
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
windows/deployment/do/images/emcc17.png
Normal file
After Width: | Height: | Size: 135 KiB |
BIN
windows/deployment/do/images/emcc18.png
Normal file
After Width: | Height: | Size: 148 KiB |
BIN
windows/deployment/do/images/emcc19.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
windows/deployment/do/images/emcc20.png
Normal file
After Width: | Height: | Size: 73 KiB |
BIN
windows/deployment/do/images/emcc21.png
Normal file
After Width: | Height: | Size: 65 KiB |
BIN
windows/deployment/do/images/emcc22.png
Normal file
After Width: | Height: | Size: 79 KiB |
BIN
windows/deployment/do/images/emcc23.png
Normal file
After Width: | Height: | Size: 86 KiB |
BIN
windows/deployment/do/images/emcc24.png
Normal file
After Width: | Height: | Size: 7.2 KiB |
BIN
windows/deployment/do/images/emcc25.png
Normal file
After Width: | Height: | Size: 206 KiB |
BIN
windows/deployment/do/images/emcc26.png
Normal file
After Width: | Height: | Size: 246 KiB |
BIN
windows/deployment/do/images/emcc27.png
Normal file
After Width: | Height: | Size: 336 KiB |
BIN
windows/deployment/do/images/emcc28.png
Normal file
After Width: | Height: | Size: 71 KiB |
BIN
windows/deployment/do/images/emcc29.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
windows/deployment/do/images/imcc01.png
Normal file
After Width: | Height: | Size: 124 KiB |
BIN
windows/deployment/do/images/imcc02.png
Normal file
After Width: | Height: | Size: 15 KiB |
BIN
windows/deployment/do/images/imcc03.png
Normal file
After Width: | Height: | Size: 22 KiB |
BIN
windows/deployment/do/images/imcc04.png
Normal file
After Width: | Height: | Size: 47 KiB |
BIN
windows/deployment/do/images/imcc05.png
Normal file
After Width: | Height: | Size: 132 KiB |
BIN
windows/deployment/do/images/imcc06.png
Normal file
After Width: | Height: | Size: 21 KiB |
BIN
windows/deployment/do/images/imcc07.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
windows/deployment/do/images/imcc08.png
Normal file
After Width: | Height: | Size: 26 KiB |
BIN
windows/deployment/do/images/imcc09.png
Normal file
After Width: | Height: | Size: 29 KiB |
BIN
windows/deployment/do/images/imcc10.png
Normal file
After Width: | Height: | Size: 32 KiB |
BIN
windows/deployment/do/images/imcc11.png
Normal file
After Width: | Height: | Size: 40 KiB |
BIN
windows/deployment/do/images/imcc12.png
Normal file
After Width: | Height: | Size: 41 KiB |
BIN
windows/deployment/do/images/imcc13.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
windows/deployment/do/images/imcc14.png
Normal file
After Width: | Height: | Size: 33 KiB |
BIN
windows/deployment/do/images/imcc15.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
windows/deployment/do/images/imcc16.png
Normal file
After Width: | Height: | Size: 21 KiB |
BIN
windows/deployment/do/images/imcc17.png
Normal file
After Width: | Height: | Size: 35 KiB |
BIN
windows/deployment/do/images/imcc18.png
Normal file
After Width: | Height: | Size: 7.6 KiB |
BIN
windows/deployment/do/images/imcc19.png
Normal file
After Width: | Height: | Size: 325 KiB |
BIN
windows/deployment/do/images/imcc20.png
Normal file
After Width: | Height: | Size: 54 KiB |
BIN
windows/deployment/do/images/imcc21.png
Normal file
After Width: | Height: | Size: 147 KiB |
BIN
windows/deployment/do/images/imcc22.png
Normal file
After Width: | Height: | Size: 52 KiB |
BIN
windows/deployment/do/images/imcc23.png
Normal file
After Width: | Height: | Size: 47 KiB |
BIN
windows/deployment/do/images/imcc24.png
Normal file
After Width: | Height: | Size: 68 KiB |
BIN
windows/deployment/do/images/imcc25.png
Normal file
After Width: | Height: | Size: 134 KiB |
BIN
windows/deployment/do/images/imcc26.png
Normal file
After Width: | Height: | Size: 7.2 KiB |
BIN
windows/deployment/do/images/imcc27.png
Normal file
After Width: | Height: | Size: 206 KiB |
BIN
windows/deployment/do/images/imcc28.png
Normal file
After Width: | Height: | Size: 53 KiB |
BIN
windows/deployment/do/images/imcc29.png
Normal file
After Width: | Height: | Size: 313 KiB |
BIN
windows/deployment/do/images/imcc30.png
Normal file
After Width: | Height: | Size: 243 KiB |
BIN
windows/deployment/do/images/imcc31.png
Normal file
After Width: | Height: | Size: 94 KiB |
BIN
windows/deployment/do/images/imcc32.png
Normal file
After Width: | Height: | Size: 296 KiB |
BIN
windows/deployment/do/images/imcc33.png
Normal file
After Width: | Height: | Size: 242 KiB |
BIN
windows/deployment/do/images/imcc34.png
Normal file
After Width: | Height: | Size: 221 KiB |
BIN
windows/deployment/do/images/imcc35.png
Normal file
After Width: | Height: | Size: 159 KiB |
BIN
windows/deployment/do/images/imcc36.png
Normal file
After Width: | Height: | Size: 283 KiB |
BIN
windows/deployment/do/images/imcc37.png
Normal file
After Width: | Height: | Size: 189 KiB |
BIN
windows/deployment/do/images/imcc38.png
Normal file
After Width: | Height: | Size: 235 KiB |
BIN
windows/deployment/do/images/imcc39.png
Normal file
After Width: | Height: | Size: 48 KiB |
BIN
windows/deployment/do/images/imcc40.png
Normal file
After Width: | Height: | Size: 328 KiB |
BIN
windows/deployment/do/images/imcc41.png
Normal file
After Width: | Height: | Size: 407 KiB |
BIN
windows/deployment/do/images/imcc42.png
Normal file
After Width: | Height: | Size: 51 KiB |
BIN
windows/deployment/do/images/imcc43.png
Normal file
After Width: | Height: | Size: 158 KiB |
BIN
windows/deployment/do/images/imcc44.png
Normal file
After Width: | Height: | Size: 262 KiB |
BIN
windows/deployment/do/images/imcc45.png
Normal file
After Width: | Height: | Size: 198 KiB |
BIN
windows/deployment/do/images/imcc46.png
Normal file
After Width: | Height: | Size: 233 KiB |
BIN
windows/deployment/do/images/imcc47.png
Normal file
After Width: | Height: | Size: 337 KiB |
BIN
windows/deployment/do/images/imcc48.png
Normal file
After Width: | Height: | Size: 262 KiB |
BIN
windows/deployment/do/images/imcc49.png
Normal file
After Width: | Height: | Size: 262 KiB |
BIN
windows/deployment/do/images/imcc50.png
Normal file
After Width: | Height: | Size: 177 KiB |
BIN
windows/deployment/do/images/imcc51.png
Normal file
After Width: | Height: | Size: 163 KiB |
BIN
windows/deployment/do/images/imcc52.png
Normal file
After Width: | Height: | Size: 294 KiB |
BIN
windows/deployment/do/images/imcc53.png
Normal file
After Width: | Height: | Size: 265 KiB |
BIN
windows/deployment/do/images/waas-mcc-diag-overview.png
Normal file
After Width: | Height: | Size: 122 KiB |
97
windows/deployment/do/index.yml
Normal file
@ -0,0 +1,97 @@
|
||||
### YamlMime:Landing
|
||||
|
||||
title: Delivery Optimization for Windows client # < 60 chars
|
||||
summary: Set up peer to peer downloads for Windows Updates and learn about Microsoft Connected Cache. # < 160 chars
|
||||
|
||||
metadata:
|
||||
title: Delivery Optimization # Required; page title displayed in search results. Include the brand. < 60 chars.
|
||||
description: Learn about using peer to peer downloads on Windows clients and learn about Microsoft Connected Cache. # Required; article description that is displayed in search results. < 160 chars.
|
||||
services: windows-10
|
||||
ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM.
|
||||
ms.subservice: subservice
|
||||
ms.topic: landing-page # Required
|
||||
ms.collection:
|
||||
- windows-10
|
||||
- highpri
|
||||
author: greg-lindsay #Required; your GitHub user alias, with correct capitalization.
|
||||
ms.author: greglin #Required; microsoft alias of author; optional team alias.
|
||||
ms.date: 03/07/2022 #Required; mm/dd/yyyy format.
|
||||
localization_priority: medium
|
||||
|
||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
||||
|
||||
landingContent:
|
||||
# Cards and links should be based on top customer tasks or top subjects
|
||||
# Start card title with a verb
|
||||
# Card (optional)
|
||||
- title: Overview
|
||||
linkLists:
|
||||
- linkListType: overview
|
||||
links:
|
||||
- text: What is Delivery Optimization
|
||||
url: waas-delivery-optimization.md
|
||||
- text: What's new in Delivery Optimization
|
||||
url: whats-new-do.md
|
||||
- text: Microsoft Connected Cache (MCC) overview
|
||||
url: waas-microsoft-connected-cache.md
|
||||
|
||||
|
||||
# Card (optional)
|
||||
- title: Configure Delivery Optimization on Windows clients
|
||||
linkLists:
|
||||
- linkListType: how-to-guide
|
||||
links:
|
||||
- text: Delivery Optimization 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: Troubleshoot Delivery Optimization
|
||||
url: waas-delivery-optimization-setup.md#troubleshooting
|
||||
- text: Submit feedback
|
||||
url: https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app
|
||||
|
||||
# Card (optional)
|
||||
- title: Configure Delivery Optimization on Microsoft Endpoint Manager
|
||||
linkLists:
|
||||
- linkListType: how-to-guide
|
||||
links:
|
||||
- text: Optimize Windows 10 or later update delivery with Configuration Manager
|
||||
url: /mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery#windows-delivery-optimization
|
||||
- text: Delivery Optimization settings in Microsoft Intune
|
||||
url: /mem/intune/configuration/delivery-optimization-windows
|
||||
|
||||
|
||||
# Card
|
||||
- title: Microsoft Connected Cache (MCC) for Enterprise and Education
|
||||
linkLists:
|
||||
- linkListType: deploy
|
||||
links:
|
||||
- text: MCC for Enterprise and Education (Private Preview)
|
||||
url: mcc-enterprise.md
|
||||
- text: Sign up
|
||||
url: https://aka.ms/MSConnectedCacheSignup
|
||||
|
||||
# Card
|
||||
- title: Microsoft Connected Cache (MCC) for Internet Service Providers (ISPs)
|
||||
linkLists:
|
||||
- linkListType: deploy
|
||||
links:
|
||||
- text: MCC for ISPs (Private Preview)
|
||||
url: mcc-isp.md
|
||||
- text: Sign up
|
||||
url: https://aka.ms/MSConnectedCacheSignup
|
||||
|
||||
# Card (optional)
|
||||
- title: Resources
|
||||
linkLists:
|
||||
- linkListType: learn
|
||||
links:
|
||||
- text: Introducing Microsoft Connected Cache
|
||||
url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898
|
||||
- text: Delivery Optimization reference
|
||||
url: waas-delivery-optimization-reference.md
|
||||
- text: Delivery Optimization client-service communication
|
||||
url: delivery-optimization-workflow.md
|
||||
- text: Using a proxy with Delivery Optimization
|
||||
url: delivery-optimization-proxy.md
|
||||
|