BranchCache and ARDI
Deploying BranchCache to an ARDI server may cause ARDI to be unavailable
Issue Description
When the BranchCache service is running on an ARDI server, you might not be able to access ARDI information.
Explaination
BranchCache is a tool used to share files (often Windows Updates) between systems on a Windows domain.
When installed, it uses TCP port 80 (the port used for standard HTTP/Web communication) to make files available. The issue is that ARDI - like most other web-accessible products - uses that port to communicate on as well.
Because BranchCache is a system process, it has priority - meaning that enabling BranchCache on an ARDI server will result in the port being unavailable to ARDI, meaning you won't be able to access ARDI data.
Unfortunately, BranchCache is often rolled out automatically by IT through Group Policy, meaning that the server will be updated and restarted with BranchCache running without any notice.
To resolve the issue, follow the steps below....
Resolution (Option #1)
1) Login to Windows on your ARDI server as an Administrator
2) Open a Powershell session as an Administrator
3) Type Disable-BC.
4) Open Services, find the apache2 service, right-click and press 'start'
Because driver configuration information may have been unavailable, you might also need to restart the various ARDI services (such as drivers) as well.
Resolution (Option #2)
1) Login to Windows on your ARDI server as an Administrator
2) Find the BranchCache service in the list of services and double-click it.
3) Click Stop to stop the service.
4) Change the start mode from Automatic to Manual and click apply
5) Find the apache2 service, right-click and press 'start'
Because driver configuration information may have been unavailable, you might also need to restart the various ARDI services (such as drivers) as well.