Credit: Phil Helming

If BranchCache does not seem to work in the environment, here is a list of items to check:

1. BranchCache Service and Configuration

Ensure that BranchCache is enabled and set to the correct mode (Distributed, Hosted or Local) and BranchCache service is running on the device/s. To verify, follow steps in the Verifying Installation of Workspace ONE Peer Distribution (BranchCache) Profile on Device subsection.

2. No existing policies that disables BranchCache

Profile to enable BranchCache will fail to install if there are existing policies set through GPO or VMware OS Optimization Tool on the device disabling BranchCache. Steps to check these policies are available in the Checking for Policies set through GPO or VMware OS Optimization Tool on the Device to Disable BranchCache section.

3. Expected peer devices in same network subnet when using Distributed Mode

Verify that the devices are in the same subnet. The Workspace ONE UEM Server and CDN do not have to be in the same subnet.

4. Device Firewall Settings
   On the Windows 10 devices, check the firewall settings and verify that the inbound and outbound rules are set to allow the required ports for peer-to-peer communication. Ensure there is no Group Policy overwriting the Firewall exceptions after BranchCache is enabled. See this page for list of required ports to allow: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1907/Peer-to-Peer_Distribution_Management/GUID-4086C330-DE0F-4ADB-9636-C7085E257B3E.html
5. Device Services Server – File Storage Caching Enabled

In the Workspace ONE UEM Console, navigate to Groups & Settings → All Settings → Installation → File Path, check that “File Storage Caching Enabled” is enabled. See this page on how to change the configuration: https://docs.vmware.com/en/VMware-AirWatch/9.3/vmware-airwatch-guides-93/GUID-AW93-FS_Enable_Reports.html

6. Device Services Server – Content Information (Hash) Generation

The initial download request for the application triggers the BranchCache Content Information (hash) to be generated. We recommend admins send the application to one device initially (or a small subset of devices), verify the application is installed and then send to the remaining devices. This provides sufficient time for BranchCache to generate the Content Information for the application on the Device Services server.

Troubleshooting Steps

The following sections provide a set of detailed troubleshooting methods to verify BranchCache is enabled and operational in Workspace ONE UEM.

Verifying Installation of Workspace ONE Peer Distribution (BranchCache) Profile on Device

1. On the device, run Windows PowerShell
2. Type in Get-BCStatus
3. Verify the following status are shown:

*CurrentClientMode will have the following values based on the Peer Distributed Mode selected:

4. Also check in Local Services that BranchCache is in ‘Running’ state
5. If status is incorrect, review Workspace ONE Peer Distribution is enabled from Settings in the Workspace ONE UEM Console. Also check Assignment Group and if this device is a member of the selected Smart Group.

Verifying device policies set through Group Policy or VMware OS Optimization Tool (OSOT) on the Device do not Disable BranchCache

1. On the device, open Registry Editor.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PeerDist\Service.

Group Policy or VMware OSOT creates policy settings in this path. Values seen in the path correspond to the below key-value pairs.

3. If Disabled setting exists:
   1. Check there is no Group Policy Object created to disable BranchCache. BranchCache settings are in Computer Configuration → Administrative Templates → Network → BranchCache. Ensure the setting in Group Policy is set to either Not Configured or Enabled.
   2. Check if using VMware OSOT that BranchCache is unchecked (disabled) in Modifications to Standard Image → Disable Services → BranchCache

Note: Manual editing of this registry key value will not be reflected in Group Policy. The value will be overwritten by any setting applied through GPO.

Verifying Workspace ONE Peer Distribution (BranchCache) Source URL is added in ContentManifest.XML through Registry

1. On the device, open Registry Editor
2. Browse for the AirWatchMDM Key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\AirWatchMDM
3. Take note of the target application Deployment ID from \AppDeploymentAgent\AppManifests. Check against the “Name” and “Version” in that GUID to see that you have the correct ID.
4. Look for the corresponding Deployment ID in \AppDeploymentAgent\ContentManifests then get the value of ContentManifestXML.
5. Verify that Source Type “P2P_BC” is present. The P2P_BC URL should have the AirWatch DeviceServices URL with “p2predirect=true” query parameter.
6. If P2P_BC source is not present, check if CDN is enabled from Settings in the Console. Also check BranchCache profile installation on this device by following steps in the Verifying Installation of BranchCache Profile on Device subsection

Using Event Viewer to track Workspace ONE Peer Distribution (BranchCache) logs

1. On the device, open Windows Event Viewer
2. Navigate to Application and Service Logs → Microsoft → Windows → BranchCache → Operational
3. Here are some log messages observed while using BranchCache

Verifying BITS Job uses the Workspace ONE Peer Distribution (BranchCache) URL

1. On the device, open Windows Event Viewer
2. Navigate to Application and Service Logs → Microsoft → Windows → Bits-Client → Operational
3. Here are some log messages observed while requesting a file through BITS

Using Windows Performance Monitor Counters for Workspace ONE Peer Distribution (BranchCache)

BranchCache status, caching and bytes transfer between server to peer and peer to peer can be monitored through Windows Performance Monitor.

1. On the server and device, open Performance Monitor
2. Create a data collector set from Performance → Data Collector Sets → User Defined
3. Right click to create New → add name → Create Manually
4. Select Performance Counter Alert and click Next
5. Select Add
6. Navigate to BranchCache then add the counters (see table below for commonly used counters and their description) → click Finish
7. Select the new data collector set, right click and click Start to begin monitoring
8. Assign applications/files to the target devices

For a complete list of counters available, please refer to this page: https://technet.microsoft.com/en-us/library/dd637826(v=ws.10).aspx

Checking Cache Size and Location on Server and Desktop

1. On the device, run Windows PowerShell
2. Type in Get-BCStatus
3. Status will show:
   1. HashCache – All information regarding the generated content information
   2. DataCache – All information regarding content shared to the device through peer distribution

Sample below:

            Note:

• Cache Location

By Default, the cache location is as shown on the Sample above. The admin can change the location with the following commands:

Netsh.exe branchcache set localcache

*Use “DEFAULT” in Path to set back to default location 

Verifying Workspace ONE Peer Distribution Enablement through Server Log

1. On the server , open the directory C:\AirWatch\Logs\DeviceServices\
2. View the file: log
3. List of log messages available:

4. Ensure the log level is set to Debug in the web.config for Device Services (C:\AirWatch\\Websites\WanderingWiFi.AirWatch.DeviceServices\Web.config)

Verifying Workspace ONE Peer Distribution Enablement through Device log

1. On the device, open the directory C:\ProgramData\Airwatch\UnifiedAgent\Logs\
2. View the file: log
3. List of log messages available: