This article shows you how to enable Content Distribution reporting in ConfigMgr so that you can monitor the success of BranchCache and 2Pint Products.
It assumes that you have Reporting Services installed and configured correctly.
Reporting Server Configuration.
The following steps should be carried out on the Primary Site server.
Enable Pre-Release Features.
In order to use pre-release features, you must give consent to use Pre-release features from within the Configuration Manager console before you can select and enable their use.
To give consent, in the console go to Administration > Site Configuration > Sites, and then from the Ribbon, choose Hierarchy Settings. On the General tab, choose Consent to use Pre-Release features.
Then, navigate to Administration > Cloud Services > Updates and Servicing > Features node of the console. In the Features node choose the Client Peer Cache feature and then choose Turn on.
Note – Although you mayl not be using the Peer Cache feature fully it is required in order to enable the Client Data Sources Dashboard, which is also used to display BranchCache statistics.
Check that the Client Data Sources Dashboard is enabled by navigating to the Monitoring > Overview > Distribution Status node of the console.
Once the above server settings are configured, the ConfigMGr clients systems will report their Client Data Sources history up to the ConfigMgr site – which will then populate the Client Data Sources dashboard. However, the clients by default will only report this data every 24 hours, which may be sufficient for a production environment, but for testing purposes this needs to be reconfigured using TriggerHappy.exe.
Set the Client Data Reporting Interval
TriggerHappy.exe is a 2Pint .NET executable that can set the Content Transfer Manager Client Data reporting interval. This is the interval at which Content Transfer Manager will send up aggregated Client Data Sources information to the SCCM site. That data is used for those BranchCache & Peer Cache Client Data dashboards and reports.
Usage: TriggerHappy.exe nn - where nn is the desired interval (in minutes) for CTM to report Client Data Sources up to the ConfigMgr site.
You can run this manually or simply create a Package/Program to execute this on the test clients.
Verifying the results: Once you have run the .exe open up the Content Transfer Manager Log. You should see the following line:
This client will report download history every nn min.
Step: Verifying the Results
Once the above settings have been implemented, simply deploy a test package/application/software update to the test systems.
Once the deployment is complete, the clients will report their client data sources and you should see the results in the dashboard – like the image below.