Skip to content

Commit 1d08961

Browse files
author
Angela Fleischmann
authored
Merge pull request #7106 from paulth1/troubleshoot-microsoft-connected-cache
edit pass: troubleshoot-microsoft-connected-cache
2 parents 36901f1 + 85b0ca5 commit 1d08961

1 file changed

Lines changed: 73 additions & 76 deletions

File tree

‎memdocs/configmgr/core/servers/deploy/configure/troubleshoot-microsoft-connected-cache.md‎

Lines changed: 73 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.localizationpriority: medium
1414

1515
# Troubleshoot Microsoft Connected Cache in Configuration Manager
1616

17-
This article provides technical details about Microsoft Connected Cache in Configuration Manager. Use it to help troubleshoot issues that you may have in your environment. For more information on how it works and how to use it, see [Microsoft Connected Cache in Configuration Manager](../../../plan-design/hierarchy/microsoft-connected-cache.md).
17+
This article provides technical details about Microsoft Connected Cache in Configuration Manager. Use it to help troubleshoot issues that you might have in your environment. For more information on how it works and how to use it, see [Microsoft Connected Cache in Configuration Manager](../../../plan-design/hierarchy/microsoft-connected-cache.md).
1818

1919
## Verify
2020

@@ -24,95 +24,92 @@ Verify this behavior [on a client](#verify-on-a-client) or [on the server](#veri
2424

2525
### Verify on a client
2626

27-
1. On client running a supported version of Windows 10 or later, download cloud-managed content. For more information on the types of content that Connected Cache supports, see [Supported content types](../../../plan-design/hierarchy/microsoft-connected-cache.md#supported-content-types).
28-
29-
2. Open PowerShell and run the following command: `Get-DeliveryOptimizationStatus`
30-
31-
For example:
32-
33-
```PowerShell
34-
PS C:\> Get-DeliveryOptimizationStatus
35-
36-
FileId : ec523d49c4f7c3c4444f0d9b952286ce40fdcee4
37-
FileSize : 549064
38-
TotalBytesDownloaded : 549064
39-
PercentPeerCaching : 0
40-
BytesFromPeers : 0
41-
BytesFromHttp : 0
42-
Status : Caching
43-
Priority : Background
44-
BytesFromCacheServer : 549064
45-
BytesFromLanPeers : 0
46-
BytesFromGroupPeers : 0
47-
BytesFromInternetPeers : 0
48-
BytesToLanPeers : 0
49-
BytesToGroupPeers : 0
50-
BytesToInternetPeers : 0
51-
DownloadDuration : 00:00:00.0780000
52-
HttpConnectionCount : 2
53-
LanConnectionCount : 0
54-
GroupConnectionCount : 0
55-
InternetConnectionCount : 0
56-
DownloadMode : 99
57-
SourceURL : http://au.download.windowsupdate.com/c/msdownload/update/software/defu/2019/09/am_delta_p
58-
atch_1.301.664.0_ec523d49c4f7c3c4444f0d9b952286ce40fdcee4.exe
59-
NumPeers : 0
60-
PredefinedCallerApplication : WU Client Download
61-
ExpireOn : 9/6/2019 8:36:19 AM
62-
IsPinned : False
63-
```
27+
1. On a client running a supported version of Windows 10 or later, download cloud-managed content. For more information on the types of content that Connected Cache supports, see [Supported content types](../../../plan-design/hierarchy/microsoft-connected-cache.md#supported-content-types).
28+
29+
1. Open PowerShell and run the following command: `Get-DeliveryOptimizationStatus`.
30+
31+
For example:
32+
33+
```PowerShell
34+
PS C:\> Get-DeliveryOptimizationStatus
35+
36+
FileId : ec523d49c4f7c3c4444f0d9b952286ce40fdcee4
37+
FileSize : 549064
38+
TotalBytesDownloaded : 549064
39+
PercentPeerCaching : 0
40+
BytesFromPeers : 0
41+
BytesFromHttp : 0
42+
Status : Caching
43+
Priority : Background
44+
BytesFromCacheServer : 549064
45+
BytesFromLanPeers : 0
46+
BytesFromGroupPeers : 0
47+
BytesFromInternetPeers : 0
48+
BytesToLanPeers : 0
49+
BytesToGroupPeers : 0
50+
BytesToInternetPeers : 0
51+
DownloadDuration : 00:00:00.0780000
52+
HttpConnectionCount : 2
53+
LanConnectionCount : 0
54+
GroupConnectionCount : 0
55+
InternetConnectionCount : 0
56+
DownloadMode : 99
57+
SourceURL : http://au.download.windowsupdate.com/c/msdownload/update/software/defu/2019/09/am_delta_p
58+
atch_1.301.664.0_ec523d49c4f7c3c4444f0d9b952286ce40fdcee4.exe
59+
NumPeers : 0
60+
PredefinedCallerApplication : WU Client Download
61+
ExpireOn : 9/6/2019 8:36:19 AM
62+
IsPinned : False
63+
```
6464
6565
Notice that the `BytesFromCacheServer` attribute isn't zero.
6666
67-
If the client isn't configured correctly, or the cache server isn't installed correctly, the Delivery Optimization client falls back to the original cloud source. Then the BytesFromCacheServer attribute will be zero.
67+
If the client isn't configured correctly, or the cache server isn't installed correctly, the Delivery Optimization client falls back to the original cloud source. Then the `BytesFromCacheServer` attribute will be zero.
6868
6969
### Verify on the server
7070
71-
First, verify the registry properties are configured correctly: `HKLM\SOFTWARE\Microsoft\Delivery Optimization In-Network Cache`. For example, the drive cache location is `PrimaryDrivesInput\DOINC-E77D08D0-5FEA-4315-8C95-10D359D59294`, where `PrimaryDrivesInput` can be multiple drives such as `C,D,E`.
71+
First, verify the registry properties are configured correctly: `HKLM\SOFTWARE\Microsoft\Delivery Optimization In-Network Cache`. For example, the drive cache location is `PrimaryDrivesInput\DOINC-E77D08D0-5FEA-4315-8C95-10D359D59294`, where `PrimaryDrivesInput` can be multiple drives, such as `C,D,E`.
7272
7373
Next, use the following method to simulate a client download request to the server with the mandatory headers.
7474
7575
1. Open a 64-bit PowerShell window as an administrator.
76-
2. Run the following command, and replace the name or IP address of your server for `<DoincServer>`:
76+
1. Run the following command, and replace the name or IP address of your server for `<DoincServer>`:
7777
78-
```PowerShell
79-
Invoke-WebRequest -URI "http://<DoincServer>/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
80-
```
78+
```PowerShell
79+
Invoke-WebRequest -URI "http://<DoincServer>/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
80+
```
8181
82-
The output looks similar to the following example:
82+
The output looks similar to the following example:
8383
84-
```PowerShell
85-
PS C:\WINDOWS\system32> Invoke-WebRequest -URI "http://SERVER01.CONTOSO.COM/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
84+
```PowerShell
85+
PS C:\WINDOWS\system32> Invoke-WebRequest -URI "http://SERVER01.CONTOSO.COM/mscomtest/wuidt.gif" -Headers @{"Host"="b1.download.windowsupdate.com"}
8686
8787
88-
StatusCode : 200
89-
StatusDescription : OK
90-
Content : {71, 73, 70, 56...}
91-
RawContent : HTTP/1.1 200 OK
92-
X-HW: 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.at2
93-
.p,1567797125.cds058.se2.p
94-
X-CCC: cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwv...
95-
Headers : {[X-HW, 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.a
96-
t2.p,1567797125.cds058.se2.p], [X-CCC,
97-
cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwvtSBQdT3uPQ5ikBe1ABMbdYIIncem+h5dtcLI6GY=],
98-
[X-CID, 100], [Accept-Ranges, bytes]...}
99-
RawContentLength : 969710
100-
```
88+
StatusCode : 200
89+
StatusDescription : OK
90+
Content : {71, 73, 70, 56...}
91+
RawContent : HTTP/1.1 200 OK
92+
X-HW: 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.at2
93+
.p,1567797125.cds058.se2.p
94+
X-CCC: cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwv...
95+
Headers : {[X-HW, 1567797125.dop019.se2.t,1567797125.cds058.se2.s,1567797125.dop114.at2.r,1567797125.cds079.a
96+
t2.p,1567797125.cds058.se2.p], [X-CCC,
97+
cdP+dRBgUCoZO1mezA9zhg2VwQ7P1JWTh9k+GhfQmu8=_SLwvtSBQdT3uPQ5ikBe1ABMbdYIIncem+h5dtcLI6GY=],
98+
[X-CID, 100], [Accept-Ranges, bytes]...}
99+
RawContentLength : 969710
100+
```
101101
102-
The following attributes indicate success:
102+
The following attributes indicate success:
103103
104-
- `StatusCode : 200`
105-
- `StatusDescription : OK`
104+
- `StatusCode : 200`
105+
- `StatusDescription : OK`
106106
107107
## Log files
108108
109-
- ARR setup log: `%temp%\arr_setup.log`
110-
111-
- Connected Cache server setup log: `SMS_DP$\Ms.Dsp.Do.Inc.Setup\DoincSetup.log` on the distribution point, and `DistMgr.log` on the site server
112-
113-
- IIS operational logs: By default, `%SystemDrive%\inetpub\logs\LogFiles`
114-
115-
- Connected Cache server operational log: `C:\Doinc\Product\Install\Logs`
109+
- **Application Request Routing (ARR) setup log**: `%temp%\arr_setup.log`
110+
- **Connected Cache server setup log**: `SMS_DP$\Ms.Dsp.Do.Inc.Setup\DoincSetup.log` on the distribution point and `DistMgr.log` on the site server
111+
- **Internet Information Services (IIS) operational logs**: By default, `%SystemDrive%\inetpub\logs\LogFiles`
112+
- **Connected Cache server operational log**: `C:\Doinc\Product\Install\Logs`
116113
117114
> [!TIP]
118115
> Among other uses, this log can help you identify connectivity issues with the Microsoft cloud.
@@ -168,15 +165,15 @@ When Configuration Manager installs the Connected Cache component on the distrib
168165
169166
## IIS configurations
170167
171-
The Connected Cache server install makes several modifications to the IIS configuration on the distribution point.
168+
The Connected Cache server installation makes several modifications to the IIS configuration on the distribution point.
172169
173170
### Application request routing
174171
175-
The Connected Cache server installs and configures IIS [Application Request Routing (ARR)](https://www.iis.net/downloads/microsoft/application-request-routing). To avoid potential conflicts, the distribution point can't already have this component installed.
172+
The Connected Cache server installs and configures IIS [Application Request Routing](https://www.iis.net/downloads/microsoft/application-request-routing). To avoid potential conflicts, the distribution point can't already have this component installed.
176173
177174
### Allowed server variables
178175
179-
After you install the Connected Cache server, the default web site has the following *local* server variables:
176+
After you install the Connected Cache server, the default website has the following *local* server variables:
180177
181178
- HTTP_HOST
182179
- QUERY_STRING
@@ -218,20 +215,20 @@ To change the custom header name for each server farm:
218215
219216
1. Open IIS Manager.
220217
1. Select **Server Farms**.
221-
1. Select a server farm and the proxy icon.
218+
1. Select a server farm and the proxy icon.
222219
1. Under **Custom Headers**, change the value `X-Forwarded-For` to `X-Forwarded-For-<custom-name>`.
223220
224221
## Manage server resources
225222
226-
Disk space required for each Connected Cache server may vary, based on your organization's update requirements. 100 GB should be enough space to cache the following content:
223+
Disk space required for each Connected Cache server might vary, based on your organization's update requirements. Disk space of 100 GB should be enough to cache the following content:
227224
228225
- A feature update
229226
- Two to three months of quality and Microsoft 365 Apps updates
230227
- Microsoft Intune apps and Windows inbox apps
231228
232229
The Connected Cache server shouldn't consume much system memory or processor time. After you install the Connected Cache server, if you notice significant process or memory resource consumption, analyze the IIS and ARR log files.
233230
234-
If the IIS and ARR log files take up too much space on the server, there are several methods you can use to manage the log files. For more information, see [Managing IIS Log File Storage](/iis/manage/provisioning-and-managing-iis/managing-iis-log-file-storage#overview).
231+
If the IIS and ARR log files take up too much space on the server, there are several methods you can use to manage the log files. For more information, see [Managing IIS log file storage](/iis/manage/provisioning-and-managing-iis/managing-iis-log-file-storage#overview).
235232
236233
## See also
237234

0 commit comments

Comments
 (0)