Release, get your version here: https://2pintsoftware.com/products/branchcache-monitor/ 

This tool supports several new command line options, listed below is the full list of switches:
Query BranchCache service status :
        BCMon.exe /Status
Query BranchCache availability from local CI file :
        BCMon.exe /QueryV2CI <path>
BCMon.exe /QueryV1CI <path>
You can use /DownloadCIFrom… to download a CI.
Query/Request/Inject data into BranchCache to test communication between clients.
        Native BranchCache API calls (Transfers using Microsfoft API’s, queries on all NIC’s):
BCMon.exe /InjectTracer
BCMon.exe /RequestTracer
BCMon.exe /RemoveTracer
Probe requests (see who replies, not using BranchCache API’s).
BCMon.exe /QueryTrace <IPAddress>
This is the same as a the /ProbeRedLeaderV2 cmdline.
Note: This can not be run on the same machine as /Inject was run!
Example: BCMon.exe /QueryTrace 192.168.138.8
Dump BranchCache CI files with the following options:
        BCMon.exe /DumpV2CI <FilePath> /Full
Use /Probe or /ProbeMatch as first parameters on two seperate computers.
        On the first machine run with the /ProbeMatch <IP Address> option to listen for probes on an IP Address
The IP Address should be an IP address that the machine runnin the /ProbeMatch has assigned.
Example: BCmon.exe /ProbeMatch 192.168.1.10
        On the second machine run the same executable with the /Probe <IP Address> command.
Example: BCmon.exe /ProbeV1 192.168.1.20
Example: BCmon.exe /ProbeV2 192.168.1.20
Example: BCmon.exe /Probe 192.168.1.20
Example: BCmon.exe /ProbeBlank 192.168.1.20
        /Probe creates V2 discovery packet.
/ProbeV1 creates V1 discovery packet.
/ProbeV2 creates V2 discovery packet.
/ProbeBlank creates a blank V1 discovery packet that any V1 capable system will reply to.
/ProbeRedLeaderV2 creates a probe to find a StifleR Red Leader using V2 BranchCache.
        If it all works, both command line windows will show data being retrieved and responded to.
The /ProbeMatch option can also be used to listen for other BranchCache discovery packages.
BITS Monitoring usage:
        BCMon.exe /BITS /Analyse [/Probe]
Analyses the past downloads by parsing the BITS Eventlog.
The /Probe option adds WMI \root\twopints:bits_activity for easy access.
        BCMon.exe /BITS /PerformanceData
Views BITS/BranchCache performance counters for analysis.
        BCMon.exe /BITS /Realtime <BITS Job GUID| Name>
BCMon.exe /BITS /RealtimePerFile <BITS Job GUID| Name> [ResultFilename.csv]
Tracks a download in realtime displaying BranchCache usage.
        BCMon.exe /BITS /RealtimeLegend
Display realtime tracking displaying legend.
Displaying the Legend for Realtime monitoring:
        Ok, here it goes, the /Realtime will show live progress-bars of the downloads using * as the progress indicator.
The download will be split into number of character available per line in the console window.
A larger console window will show more granular detail than a small one.
As a chunk is downloaded it will then display progress on screen in a colour depending on BranchCache ratio.
Basically the greener the better, red is bad. Gray means 100% from source/server.
Anything over 85% BranchCache ratio gets this colour:
Anything over 75% BranchCache ratio gets this colour:
Anything over 50% BranchCache ratio gets this colour:
Anything over 20% BranchCache ratio gets this colour:
Anything over 10% BranchCache ratio gets this colour:
Anything over 0% BranchCache ratio gets this colour :
100% from source and no BranchCache gets this colour:
If we are BranchCaching but havent written out data yet a yellow “!” Appears at the current point.
Use /ComparePackages as first parameters to compare multiple packages without downloading them.
        This does not require a CCM client on the machine, but you can specify sitecode and MP on the command line.
Example: BCmon.exe /ComparePackages ABC 192.168.11.30 ABC00003;3 ABC00010;5
Example: BCmon.exe /ComparePackages ABC00003;3 ABC00010;5 ABC000FF;98
Use /QueryCache as first parameters to query for local BranchCache data
        Then you can specify the package ID and we do the rest.
This does not require a CCM client on the machine, but rights to get the retrieve content.
Example: BCmon.exe /QueryCache ABC00003 3 ABC 192.168.11.30
Example: BCmon.exe /QueryCache ABC00003 3
Use /DownloadCIFrom… as first parameters to download a hash
        /DownloadCIFromPackage <PackageId> <version> <folder> [SiteCode] [MP]
/DownloadCIFromBaseURL <URLFolder> <Folder>
/DownloadCIFromSingleURL <URL to single file> <Folder>
Use /VerifyCI as first parameters to check if BranchCache is working on the server
        /VerifyCI <URL>
Example: BcMon.exe /VerifyCI http://sms01.2pstest2.local/iisstart.png
Use /GenerateCI as first parameters to check if BranchCache is working on the server
        /GenerateCI <URL>