2.4 KiB
title, description, author, ms.author, manager, ms.service, ms.subservice, ms.topic, ms.date, appliesto
title | description | author | ms.author | manager | ms.service | ms.subservice | ms.topic | ms.date | appliesto | |||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Verify MCC cache node functionality | Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes. | chrisjlin | lichris | naengler | windows-client | itpro-updates | how-to | 09/27/2024 |
|
Verify MCC cache node functionality
This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCC) cache node is functioning correctly.
These steps should be taken after deploying MCC caching software to a Windows or Linux host machine.
Steps to verify functionality of MCC cache node
-
To verify that the MCC container on the host machine is running and reachable, run the following command from the host machine:
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.
-
To verify that Windows clients in your network can reach the MCC cache node, visit the following address from a web browser on a Windows client device:
http://[HostMachine-IP-address]/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 MCC cache node.
-
To check how much content an individual Windows client has pulled from an MCC cache node, open the Delivery Optimization activity monitor on the Windows client device.
You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server".