![]() ![]() Regardless, be careful where you're deploying the SCCM client with BranchCache enabled, it's probably best that you just don't have the BranchCache option enabled for your server client policy or machine collections. What's interesting is that the 2021-07 updates applied fine with Start=4, so I guess 2021-08 had a different dependency that didn't jive with that value. I reran the updates and they were successful after three previously failed attempts. The default value appears to be '3'.Īfter removing the SCCM client a couple months ago, it left behind the BranchCache service, so I stopped and disabled that service to ensure it wasn't going to conflict with the vendor process when I switched that reg value back, I then set the 'Start' value back to '3' and rebooted the servers. 'Start' was set to '4' to work around the issue. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP In the process of figuring that out, then vendor changed a registry value to work around the issue and get their process going: ![]() You will generally see this error during or after installing a cumulative update or any other kind of Windows update. I had recently pushed the SCCM client (with BranchCache enabled) to these test servers and we found that the BranchCache service (installed with the SCCM client) conflicted with a vendor process running on the servers. Specifically, the Windows Update error 0x800f0922 appears when the system is unable to install an update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |