deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-14 14:27:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update waas-delivery-optimization.md

Browse Source
This commit is contained in:
MaratMussabekov 2020-10-11 08:32:54 +05:00 committed by GitHub
parent d9f78db07e
commit 9775f9ca51
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
windows/deployment/update/waas-delivery-optimization.md
View File

@ -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. - Clients aren’t able to reach the Delivery Optimization cloud services.
- The cloud service doesn’t see other peers on the network. - 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. - 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. ### 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**. 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. ### The cloud service doesn't see other peers on the network.
If you suspect this is the problem, try these steps: 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. 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