Minor release allowing for future phone tethering capabilities.
This release incorporates important bug fixes.
Fixes issues where system registry is not unmounted properly due to handle still active when using BranchCache version 1 (For Windows 7, yes that still exist).
Resolves a logging issue where a log statement crashes the BCEnabler if port and BCVersion is not specified on the command line. (Not that anyone runs BranchCache on default port 80 right???).
Fixes a cache issue where the NTFS ACL's are not set correct in some circumstances. This leaves the cache dead in the water and BranchCache is not working correctly in the full OS. This issue was introduced in 18.104.22.168 and later versions and the results depends on several factors as disk layout etc. For machines built on these versions, check that the cache is set correct, and if not, the fix is to run the following commands (as an example)
Netsh BranchCache Reset
Netsh BranchCache set service mode=distributed
OSD Toolkit version and BCEnabler binary versions are now being transferred to the full operating system registry under HKLM\Software\2Pint Software\BCEnabler
Release to fix some of the functionality we broke in the 22.214.171.124 release as well as disabling the WinHTTP intergration with BranchCache to help with our customers using ConfigMgr with Enhanced HTTP. (Contact us for more info on this issue)
Fixes regression when cache is present in OS image being applied, which breaks BCEnabler MOVE step.
Fixes for HTTPS ConfigMgr environments where we select the wrong virtual directory to authenticate with.
Improved handling where Turbo takes a second to release file handles. Improved work to troubleshoot hash issues.
WINHTTP is disabled in WinPE to improve reliability in CCMTOKEN scenarios.
Removed last entries for policies for BranchCache.
Fixed issue where BranchCache would cause a BSOD with "CACHE MANAGER" on reboots in WinPE.
Fixed issue where the improved logic to change the cache location causing issues to re-initiate old caches on reboots.
This was a quick release to fix some previous issues in 126.96.36.199 around HTTPS and CCMTOKEN paths and to enable licensing for the Turbo feature.
Turbo - read about the Turbo feature here - https://2pintsoftware.com/the-updated-osd-toolkit-turbo-feature/
Turbo now also work on HTTPS with PKI scenarios
Turbo mode now requires a license key - please see https://2pintsoftware.com/pricing/ for pricing details
Allow HTTPS override in full OS where no Network Access Account is available and BITSACP fails due to lack of credentials, we then redirect to HTTPS on SMS_DP_SMSPKG paths.
Fix for bugs when HTTPS usage in full operating system environments where no Network Access Account is present.
Fix for StifleR Service not started in all scenarios by BCEnabler.exe.
This was a major rework of the OSD Toolkit to improve stability and performance of both the BCEnabler as well as the BITSACP. Please test in QA/Test environments before deploying in production to make sure that all your scenarios are working.
Changes to BCEnabler logic for improved stability
Changes to Firewall transfer rules to full operating system
Fixes bug if version is not specified on the BCEnabler Enable command line
Changes to allow turbo for 5 files, largest first if over 100MB in size
BITSACP: Improved progressbar to also who peer data
Improved support for PSD
Fixed hash issues where small packages might fail
Fixed BCEnabler Move issue when moving from other disks
Improved logging to roll over if log files are over 1MB in size
All logging is now in to the SMSTSLog folder
Improved spelling and grammar in log files, thank you Mikael Nyström for going through all logs
Turbo feature completes download if 100% of files are available locally
The BITSACP.EXE, HashGen.exe and BranchCacheTool.exe are all signed
BITSACP.EXE, HashGen.exe and BranchCacheTool.exe are all moved to full OS disk as part of the BCEnabler MOVE command line options.
This is the 1.9.7 release version of the executables, future binaries and capabilities might differ greatly.
This release contains the following features:
BranchCache WinPE Generator - For creating BranchCache enabled WinPE Images
There are two versions, one x86 and one x64
Both versions can be used to create x86 and x64 images. Only difference is of course that the x86 version of the tool does not run on a x64 system.
To reiterate, the tool architecture has nothing to do with the generated architecture of the boot images.
BITS & BranchCache WinPE Enabler – For enabling BranchCache in WinPE task sequences/command line deployments
Both x86 and x64 versions are included
These are automatically injected into WinPE versions created by the Generator tool.
Initializes BITS and starts dependent services
Alternate Content Provider for WinPE and Task Sequences
BranchCache BITS BranchCache Downloader with BITS & BC Integration (BITSACP.exe)
Both x86 and x64 executables are available, although x86 should work on x64 in most circumstances as well (not in WinPE as syswow is not included)
Runs in both WinPE as well as full OS
Generates the same reporting structure if the BITS Reporter is on the system
//The 2Pint Team
If you are not familiar with BranchCache we recommend that you take a look at our BranchCache page before continuing with this document as it covers several key factors of BranchCache.