Fix For Error: Failed To Process Configuration Manager Update 0x87d20b15

With the release of version 1710 for System Center Configuration Manager Current Branch on November 20, 2017, I pursued to update my ConfigMgr 1706 site to take advantage of some of the exciting new features, which you can read more here! Use this PowerShell script to enable the early update ring for ConfigMgr 1710.

I tested the update in my test lab and the upgrade to v1710 worked just fine. As usual with my production environment, I always run the prerequisite checker to make sure nothing is flagged as an issue, which in my case all was fine with green checkmarks. However, the actual installation of the update failed on the Installation step for “Upgrade ConfigMgr database” as seen in the screen capture above. The description for the error indicates: [Failed]: Upgrading ConfigMgr database. Check cmupdate.log for details.

The following is an error was seen in the cmupdate.log: Failed to apply update changes 0x87d20b15

I located a blog post by my friend Anoop dated from October 2016 referencing a similar error code where he points to providing the NT Authority/System account in SQL with the sysadmin security role, however that was not the cause of my upgrade failure and the security roles were already defined correctly. The following TechNet thread was a dead end as well.


My post on Twitter as seen above caught the attention of another friend of mine, David James, Director of Engineering for ConfigMgr at Microsoft, who with his team were able to pinpoint the problem in no time at all and quickly provided a solution which resolved my ConfigMgr 1710 upgrade installation hang up. Thanks David and to the ConfigMgr team! The gist of the problem is that my environment had an old compatibility level 100 set for the SQL Server database for the CM_XXX database, and you can find this referenced in the cmupdate.log file. Changing it to 110 fixed the compatibility level needed for ConfigMgr 1710.

Run the following query in SQL Management Studio (please change XXX to your ConfigMgr Site Code) and retry the installation via the Update and Servicing node in the ConfigMgr Admin Console. This also addresses the issue where TRY_CONVERT is not recognized as a built-in SQL function:

ALTER DATABASE CM_XXX SET COMPATIBILITY_LEVEL = 110

SUCCESS!!

Please like & share:

How To Fix: Bitlocker Recovery Key Prompts On Every Reboot

windows-10-bitlocker-featured

There are few reports of users having Bitlocker issues following the October 2016 patches.

The issue: On every reboot, the Bitlocker recovery key is required which is quite disruptive and cumbersome. As a workaround in order to solve this issue, the following steps can be taken:

On the next reboot and once in Windows, reset Bitlocker by disabling and re-enabling it.
In administraive command prompt, do the following:
manage-bde -protectors c:-disable
then do this:
manage-bde -protectors c:-enable

At this time, I’m not certain on which patch is causing the issue but I wanted to share this info to help. You can also discuss in this TechNet post.

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

Repair Windows Update Agent

Windows-Update

Every now and then, you may discover a computer system that is unable to detect or install available software updates from Microsoft or from your internal Windows Server Update Services (WSUS) repository. You’ll find an error such as 8007000E generated and often times running the Windows Update Troubleshooter FixIt tool is sufficient to fix Windows Update errors, but sometimes a manual approach that requires the deletion of the SoftwareDistribution content and re-registering the Windows Update components is needed, and this can be a tedious task. By using a script, this repair task can be automated.

Here are some batch scripts to help  fix a broken Windows Update Agent on a computer system. The scripts can also be run on a remote system using the ‘psexec‘ tool, which is part of the Sysinternals Suite from Microsoft. Copy and paste the content of your desired batch file below into Notepad and save the file with the “.bat” file extension, for example: repair_wua.bat .

Version 1:

Version 2:

Here’s another Windows Update Agent Reset script available on Technet.
The Windows Update Troubleshooter is available here.

Follow me on Twitter (@Hoorge) and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share:

How To Fix Network Print Queue Installation Error 0x0000007e on Windows

Problem:

Adding an HP print queue from a Windows Server 2012 R2 print server on a Windows 7 / Windows 8.1 / Windows 10 system fails with the error:

Solution:

Delete the “BIDI” key from:
HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\<QueueName>\CopyFiles

You can essentially delete the “CopyFiles” key as well.
** Please backup the registry before attempting this fix. **

Please like & share: