# Verify Cache Server Functionality

Check a Connected Cache node from the host and a Windows client, then inspect Delivery Optimisation activity. The recorded health check expects HTTP 200 and the client check expects an image download.

!!!warning Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
!!!

Verification steps include:

- Cache host functionality
- Run the following command on the cache host server:
- wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com
- If successful, there should be an HTTP response with StatusCode 200.
- Cache host access from clients.
- Visit the following address from a web browser on a Windows client device:
- <http://%5BCacheServer-IP-address%5D/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com>
- If successful, the Windows client device should begin to download a small image file from the Connected Cache node.
- Delivery Optimisation statistics from a client PC
- Settings\>Windows Update\>Advanced Options\>Delivery Optimization\>Activity Monitor

## Expected Outcomes

The source reports historical cache-server results of ~94-95% cache hit rates, with 2-3TB of data weekly served via the cache server rather than the external Windows Update servers.

## Related guidance

- [Topic overview](Introduction.md)
- [Source review status](../../review/Review-status.md)