This is part 2 of a two part post. In part one I explained how I set up BranchCache on my SCCM distribution point.
This post will demonstrate the methods I used to prove that computers at my branch office were actually using a locally cached version of the application to install from rather than pull it from over the WAN.
- Choose a computer in your branch office that you wish to test will be pulling the content from another computers local cache:
Either open Performance Monitor (type perfmon in the Run menu) directly on that computer or run it on your administration computer and right-click the Performance node and select ‘Connect to another computer’
- Expand the ‘Data Collector Sets’ node and right-click ‘User Defined’ -> New -> Data Collector Set
Give it a meaningful name and select the radio button: ‘Create Manually (Advanced)’:
- Tick ‘Performance Counter’ then click next:
- Click the ‘Add’ button:
- Expand the BranchCache Node, select BITS: Bytes from cache and BITS: Bytes from server then select the Add button. Then Click OK:
- Click Next:
- Accept the default (or change it) save location, change credentials that it will run as if you need to then click finish.
- Right-click your newly defined Data Collector and select Start:
- Now at your branch office, install an application from SCCM on another computer ie the one that you are not monitoring with the data collector set. This will then install from over the WAN and the content will be cached locally on the computers disk. Once you’ve done that, on the computer that we are monitoring, install the same application. This will install it from the content cached locally on the first computer. We can see this by looking at the perfmon logs we just set up for monitoring:
- That’s it! Don’t forget to turn off the perfmon collector set when you’ve finished.