Microsoft released another hotfix KB5001600 for ConfigMgr 1910 through 2010. This KB Fix Microsoft Connected Cache MCC Server Component Installation Fails Issue with Configuration Manager. But the installation of this KB is a bit different from a normal out-of-band hotfix.
I have a post about the known issues of Configuration Manager 2010. More details available – SCCM 2010 Known Issues Bugs & Fixes. With the release of the 2010 rollup update KB4600089, most of those known issues are fixed. But here comes another issue with Microsoft Connected Cache (MCC).
Do you need to Install? Recommendation
Do you need to install this KB5001600? My recommendation is to check whether you have the symptoms that are explained below. If you have all these symptoms, then only proceed with the installation of the hotfix.
- Have you enabled distribution points (DP) after March 5, 2021?
- Have you enabled this distribution point to be used as a Microsoft Connected Cache server DP properties?
- The DoincSetup.log (Folder location on remote DP – \SMS_DP$\Ms.Dsp.Do.Inc.Setup) contains the following log snippet.
Setting InvocationErrorMessage : Failed to find downloaded content in the primary disk caches Installer return code: 13631517
- Following log entries – Distmgr.log on the site server for the DP.
Finished waiting for DoincInstall. InvocationState: InstallCompleted. InvocationExitCode: 13631517. InvocationMessage: Failed to find downloaded content in the primary disk caches. STATMSG: ID=9522 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER"...
- Following status message in the SMS_DISTRIBUTION_MANAGER component.
Message ID: 9522 Message text: Delivery Optimization In-Network Cache setup on distribution point "{distribution_point}" failed. Error code 13631517.
Download KB5001600
You can download the following hotfix KB5001600 to resolve MCC/DP problem Download this hotfix now.
Fix Microsoft Connected Cache MCC Server Issue
Follow the steps mentioned below to Fix the Microsoft Connected Cache MCC Server Issue:
- Run ConfigMgr-KB5001600.exe.
- Click on the Yes button to accept the agreement.
- Click on the Browse button to find a suitable location to store extracted files.
- Click the OK button.
- Copy the new version of DoincInstall.exe, version 1.5.4.1512, to the F:\Program Files\Microsoft Configuration Manager\bin\x64 (change the drive letter according to your environment) folder on all site servers, including the CAS server if present, and any passive sites.
- Uncheck the Enable this DP to be used as a Microsoft Connected Cache server option in the affected distribution point’s properties.
- Wait for the uninstall of MCC to complete on the distribution point. You can confirm this by the 9152 success status message.
- Once MCC got uninstalled successfully, you can Re-enable the checkmark from the option called Enable this distribution point to be used as a Microsoft Connected Cache server for the affected distribution point.
Automation – Reset Distribution Point
When you have many DPs (more than 10-15 or more), it is tough to disable and re-enable MCC (Microsoft Connected Cache) component from DP properties. That is why Microsoft provided the following method to the automation option to reset DP with the new DoincInstall.exe file.
- Open Notepad.exe from Run.
- Enter File Name – resetdps.trn (a blank text file).
- Save as type – All Files (*.*).
- Open the {SMSInstallDir}\inboxes\distmgr.box folder (F:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box)
- Copy the resetdps.trn file created above.
- Paste resetdps.trn file to F:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box (Remember to change the Drive letter – F:\ – to the one that is specific to your environment).
Resources
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
What does resetting the DP actually do? Will it affect other services besides MCC, like PXE, or the content library?
what if you are getting this error on a system that is running SCCM 2111?
There’s a newer version of this fix: https://docs.microsoft.com/en-us/mem/configmgr/hotfix/2111/12819689
It’s actually the same version in the MECM 2203 PreReq Downloads. So version 1.5.5.9002 is the latest.