Fix problem with Peer Cache only working via HTTPS since CB 1710
We noticed 2 things making it impossible for us to use Peer Cache:
In CB 1702, we noticed that clients contacting the Peer Cache Source only attempt this via HTTPS.
This doesn't make sense, especially because we (and most of the other customers we know) use HTTP for the entire SCCM infrastructure.
Furthermore, in the client settings the option to switch from HTTPS to HTTP was obviously forgotten - it's missing.
Is the PG aware of this, and can we expect the issues will be fixed in CB 1802?
Kerim Hanif commented
This is not a bug, after 1710 peer cache always uses HTTPS for transport between client and the peer source when downloading content from the peer source. This doesn't require any extra configuration that administrators needs to do, everything happens in the background.
Thomas B commented
We found the cause:
It is something which Microsoft already identified as a bug (and there is no prospects when it will be fixed unfortuneately):
„Customer has SCCM 1710. They wanted to use Peer Cache settings. They created client settings for Peer cache and set it Maximum cache site (MB) to 800MB, Maximum cache size (percentage of disk) 80% (which is 720 MB). However, in SCCM Client console they see the max size of cache in 99999 MB“
So when your cache size is set bigger, the peer cache client wl stop working.
by the way it is not because of HTTPS, because in fact it works without certificate if the above issue is considered