From 9775f9ca518c20aaf16787cb19bee4a9a4377e79 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Sun, 11 Oct 2020 08:32:54 +0500 Subject: [PATCH 1/7] Update waas-delivery-optimization.md --- .../deployment/update/waas-delivery-optimization.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 77c469b79d..9e420e620d 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -193,6 +193,7 @@ If you don’t see any bytes coming from peers the cause might be one of the fol - Clients aren’t able to reach the Delivery Optimization cloud services. - The cloud service doesn’t see other peers on the network. - Clients aren’t able to connect to peers that are offered back from the cloud service. +- None of the computers on the network are peering. ### Clients aren't able to reach the Delivery Optimization cloud services. @@ -204,7 +205,6 @@ If you suspect this is the problem, try these steps: 3. If **DownloadMode** is 99 it could indicate your device is unable to reach the Delivery Optimization cloud services. Ensure that the Delivery Optimization hostnames are allowed access: most importantly **\*.do.dsp.mp.microsoft.com**. - ### The cloud service doesn't see other peers on the network. If you suspect this is the problem, try these steps: @@ -223,6 +223,15 @@ If you suspect this is the problem, try a Telnet test between two devices on the 2. Run the test. For example, if you are on device with IP 192.168.8.12 and you are trying to test the connection to 192.168.9.17 run **telnet 192.168.9.17 7680** (the syntax is *telnet [destination IP] [port]*. You will either see a connection error or a blinking cursor like this /_. The blinking cursor means success. +### None of the computers on the network are peering + +If you suspect this is the problem, check Delivery Optimization settings that could limit participation in Peer Caching. Check following settings in assigned group policies, local group policies and MDM policies, whether they are too restrictive: + +- Minimum RAM (inclusive) allowed to use Peer Caching +- Minimum disk size allowed to use Peer Caching +- Enable Peer Caching while the device connects via VPN +- Allow uploads while the device is on battery while under set Battery level + From 8034fda3ed2a47056f605cb7f316e3b8e4d0ed48 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 12 Oct 2020 09:40:03 +0500 Subject: [PATCH 2/7] Update windows/deployment/update/waas-delivery-optimization.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/update/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 9e420e620d..9051fde57c 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -225,7 +225,7 @@ If you suspect this is the problem, try a Telnet test between two devices on the ### None of the computers on the network are peering -If you suspect this is the problem, check Delivery Optimization settings that could limit participation in Peer Caching. Check following settings in assigned group policies, local group policies and MDM policies, whether they are too restrictive: +If you suspect this is the problem, check Delivery Optimization settings that could limit participation in Peer Caching. Check whether the following settings in assigned group policies, local group policies, and MDM policies are too restrictive: - Minimum RAM (inclusive) allowed to use Peer Caching - Minimum disk size allowed to use Peer Caching From 4655fb01438d225a84e82da1b3bdde4bbc6624f6 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 12 Oct 2020 09:59:59 +0500 Subject: [PATCH 3/7] Update windows/deployment/update/waas-delivery-optimization.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/update/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 9051fde57c..2176e4545b 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -227,7 +227,7 @@ If you suspect this is the problem, try a Telnet test between two devices on the If you suspect this is the problem, check Delivery Optimization settings that could limit participation in Peer Caching. Check whether the following settings in assigned group policies, local group policies, and MDM policies are too restrictive: -- Minimum RAM (inclusive) allowed to use Peer Caching +- Minimum RAM (inclusive) allowed to use Peer Caching. - Minimum disk size allowed to use Peer Caching - Enable Peer Caching while the device connects via VPN - Allow uploads while the device is on battery while under set Battery level From e2c92ed14b5e7d9a4e40147bfdb49e6d8293ef8c Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 12 Oct 2020 10:00:07 +0500 Subject: [PATCH 4/7] Update windows/deployment/update/waas-delivery-optimization.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/update/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 2176e4545b..0b72208001 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -228,7 +228,7 @@ If you suspect this is the problem, try a Telnet test between two devices on the If you suspect this is the problem, check Delivery Optimization settings that could limit participation in Peer Caching. Check whether the following settings in assigned group policies, local group policies, and MDM policies are too restrictive: - Minimum RAM (inclusive) allowed to use Peer Caching. -- Minimum disk size allowed to use Peer Caching +- Minimum disk size allowed to use Peer Caching. - Enable Peer Caching while the device connects via VPN - Allow uploads while the device is on battery while under set Battery level From b8711edafd7b10950a355c4ad946c84c271512d1 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 12 Oct 2020 10:00:14 +0500 Subject: [PATCH 5/7] Update windows/deployment/update/waas-delivery-optimization.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/update/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 0b72208001..58dffde87b 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -230,7 +230,7 @@ If you suspect this is the problem, check Delivery Optimization settings that co - Minimum RAM (inclusive) allowed to use Peer Caching. - Minimum disk size allowed to use Peer Caching. - Enable Peer Caching while the device connects via VPN -- Allow uploads while the device is on battery while under set Battery level +- Allow uploads when the device is on battery while under the set battery level. From 4c9deba8d979f29cd454f8ef34d499fde7df3538 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Mon, 12 Oct 2020 10:00:23 +0500 Subject: [PATCH 6/7] Update windows/deployment/update/waas-delivery-optimization.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/update/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 58dffde87b..f54ac455eb 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -229,7 +229,7 @@ If you suspect this is the problem, check Delivery Optimization settings that co - Minimum RAM (inclusive) allowed to use Peer Caching. - Minimum disk size allowed to use Peer Caching. -- Enable Peer Caching while the device connects via VPN +- Enable Peer Caching while the device connects via VPN. - Allow uploads when the device is on battery while under the set battery level. From e6e5bd607217be3b61e1cf516f7db6f9b249c47c Mon Sep 17 00:00:00 2001 From: Jaime Ondrusek Date: Mon, 12 Oct 2020 10:20:15 -0700 Subject: [PATCH 7/7] Update waas-delivery-optimization.md Correcting language. Do not use "peer" as a verb--that means "to look at closely." --- .../update/waas-delivery-optimization.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index f54ac455eb..359a306462 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -193,7 +193,7 @@ If you don’t see any bytes coming from peers the cause might be one of the fol - Clients aren’t able to reach the Delivery Optimization cloud services. - The cloud service doesn’t see other peers on the network. - Clients aren’t able to connect to peers that are offered back from the cloud service. -- None of the computers on the network are peering. +- None of the computers on the network are getting updates from peers. ### Clients aren't able to reach the Delivery Optimization cloud services. @@ -223,14 +223,14 @@ If you suspect this is the problem, try a Telnet test between two devices on the 2. Run the test. For example, if you are on device with IP 192.168.8.12 and you are trying to test the connection to 192.168.9.17 run **telnet 192.168.9.17 7680** (the syntax is *telnet [destination IP] [port]*. You will either see a connection error or a blinking cursor like this /_. The blinking cursor means success. -### None of the computers on the network are peering +### None of the computers on the network are getting updates from peers -If you suspect this is the problem, check Delivery Optimization settings that could limit participation in Peer Caching. Check whether the following settings in assigned group policies, local group policies, and MDM policies are too restrictive: +If you suspect this is the problem, check Delivery Optimization settings that could limit participation in peer caching. Check whether the following settings in assigned group policies, local group policies, are MDM policies are too restrictive: -- Minimum RAM (inclusive) allowed to use Peer Caching. -- Minimum disk size allowed to use Peer Caching. -- Enable Peer Caching while the device connects via VPN. -- Allow uploads when the device is on battery while under the set battery level. +- Minimum RAM (inclusive) allowed to use peer caching +- Minimum disk size allowed to use peer caching +- Enable peer caching while the device connects using VPN. +- Allow uploads when the device is on battery while under the set battery level