The Updated Bit..

Yo BranchCachers!

Just thought I’d update you on another cool addition to BranchCache in Windows 10. It addresses a common issue when deploying BranchCache – that of Cache size. Previously you could assign the BranchCache Cache size (using netsh in Win7 or PowerShell in Win8/10) as a percentage of disk, or as an absolute value in Mb.

You can still do that, but the good news is that you can now specify a much bigger cache size – safe in the knowledge that if the free disk space on the system start to fill up, the BranchCache Cache will dynamically shrink. Hellz Yeah!

Segments in the cache will be removed based on the ‘last accessed’ date, so that content that is frequently used will be left alone, while the old smelly bits that nobody wants will be kicked out..

Bottom line? Disks are getting bigger, so go ahead and allocate a TON of space to the BranchCache cache on your machines. Then, faggedaboudit!

Want to rezise that cache and just can’t wait cos you’re so damn excited? See this post and get mega-caching like a pro:

How to Resize Them BranchCache Cache Things

cheers, Phil 2Pint


BranchCache – What’s new in Windows 10 you might ask? Well, not a lot on the surface, so the Microsoft marketing deperatment might have a hard time to explain what’s new. But if you look under the hood there are some nice new features in the logging department. Why is this so important? Well it will help to showcase just how great BranchCache is in sharing and reusing content, especially with the de-duplication functionality.

So after downloading a new Windows 10 build you want to check out some of these new capabilities in Windows 10, or maybe you have been trying to find them on new builds but haven’t seen anything. Is it not in there or am I looking in the wrong place? Well the answer is, it’s well hidden.

Open up the Eventlog Viewer, in the View menu` select “Show Debug And Analytic Logs”, then expand the tree to Application And Services Logs -> Microsoft -> Windows -> BranchCacheMonitoring, click on Analytic, then on the right side of the eventvwr, enable the log. Once that is enabled you can see a bunch of events both for server and client side BranchCache operations.

The server side events cover the HTTP integration with events such as incoming HTTP requests, BranchCache aware or not, BranchCache publication, HTTP response modification etc.
The client side has events such as content information adding, data adding, peer discoveries/requests/data retrievals etc. – and as you can see from the above picture – it’s quite verbose!

Ok’ so what does that mumbojumbo translate to? Well you will then be able to report on which client got which piece of data from who. One of the most requested reporting features, people just want to know.

Partner in crime, Phil “Senior” Wilcock has been playing around with these new events and I am sure he will write a little blog post on it anyday now. 🙂

ps. Thanks to GiGi from the Windows Networking team to pointing this out for us. As we missed it as well. 🙂