deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 20:03:40 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Changed formatting of machine setup to tables

Browse Source
This commit is contained in:
Carmen Forsmann
2022-11-11 08:22:34 -07:00
parent 24a8dc5692
commit 927a4d48c2
1 changed files with 25 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
windows/deployment/do/delivery-optimization-test.md
View File

@ -55,17 +55,19 @@ Several elements that influence overall peering, using Delivery Optimization. Th
#### Test Machine Setup #### Test Machine Setup
* Number of machines used: 2 |Setup Checklist| Value/Explanation
* Hardware: |--------|-------------------------------|
* Two Virtual Machines or physical devices running Windows 10 (21H2) / Windows 11 (21H2) |Number of machines used| 2
* 8-GB RAM / 127-GB Disk |Virtual Machines/physical devices| 2
* Network – ensure the test devices are connected to the same network, one that is representative of the corporate network |Windows OS version | Windows 10 (21H2) and Windows 11 (21H2)
* Apply Policy settings/Windows configurations on each machine: |RAM | 8-GB
* Pause Windows Updates. This controls the test environment so no other content is made available during the test, and potentially altering the outcome of the test. By default, there are four pieces of content available for peering at a given time. The Delivery Optimization client cycles through the available content in the cache. Simply pausing Windows Updates might not be enough in some cases. If there are Microsoft Store Updates, for example, a download can be triggered causing the four caching slots to be filled. If this happens, the second machine may not see peers. Verify there's only one cached content before continuing the test on the second machine. If there are problems and no peering happens, use 'Get-DeliveryOptimizationStatus' on the first machine to return a real-time list of the connected peers. |Disk size | 127-GB
* Ensure all Store apps are up to date |Network | Connected to same network, one that is representative of the corporate network.
* Set Delivery Optimization Download mode = '2' |Pause Windows Updates | This controls the test environment so no other content is made available during the test, and potentially altering the outcome of the test. By default, there are four pieces of content available for peering at a given time. The Delivery Optimization client cycles through the available content in the cache. Simply pausing Windows Updates might not be enough in some cases. If there are Microsoft Store Updates, for example, a download can be triggered causing the four caching slots to be filled. If this happens, the second machine may not see peers. Verify there's only one cached content before continuing the test on the second machine. If there are problems and no peering happens, use 'Get-DeliveryOptimizationStatus' on the first machine to return a real-time list of the connected peers.
* Set Delivery Optimization GroupID = 'GUID'. A GUID is a required value, which can be generated using PowerShell, ‘[[guid]::NewGuid()](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’. |Ensure all Store apps are up to date | This will help prevent any new, unexpected updates to download during testing.
* **If Windows 11 devices** set 'Restrict Peer Selection' policy to '0-NAT'. The default behavior in Windows 11 is set to '2-Local Peer Discovery'. For testing purposes, this needs to be scoped to the NAT. |Delivery Optimization Download mode | 2 (set on each machine)
|Delivery Optimization GroupID | 'GUID' (set on each machine). A GUID is a required value, which can be generated using PowerShell, ‘[[guid]::NewGuid()](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’.
|**If Windows 11 devices** set Delivery Optimization 'Restrict Peer Selection' policy | 0-NAT (set on each machine). The default behavior in Windows 11 is set to '2-Local Peer Discovery'. For testing purposes, this needs to be scoped to the NAT.
#### Test Instructions #### Test Instructions
@ -104,16 +106,18 @@ The following set of instructions will be used for each machine:
#### Test Machine Setup #### Test Machine Setup
* Number of machines used: 3 |Setup Checklist| Value/Explanation
* Hardware: |--------|-------------------------------|
* Three Azure Virtual Machines running Windows 10 (21H2) |Number of machines used| 3
* 8-GB RAM / 127-GB Disk |Virtual Machines| 3
* Network – ensure the test devices are connected to the same network, one that is representative of the corporate network. |Windows OS version | Windows 10 (21H2)
* Apply Policy settings/Windows configurations on each machine: |RAM | 8-GB
* Set Delivery Optimization Download mode = '2' |Disk size|127-GB
* Set Delivery Optimization GroupID = 'GUID'. A GUID is required value which can be generated using PowerShell, ‘[[guid]::NewGuid()](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’ |Network | Connected to same network, one that is representative of the corporate network.
* Set Delivery Optimization policy 'Delay background download from http' = 60 (secs) |Delivery Optimization Download mode| 2 (set on each machine)
* Set Delivery Optimization policy 'Delay foreground download from http = 60 (secs) |Delivery Optimization GroupID| 'GUID' (set on each machine). A GUID is required value which can be generated using PowerShell, ‘[[guid]::NewGuid()](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’
|Delivery Optimization policy 'Delay background download from http' | 60 (set on each machine)
|Delivery Optimization policy 'Delay foreground download from http |60 (set on each machine)
#### Testing Instructions #### Testing Instructions