Important ConfigMgr 2012 SP1 Hotfix Released (KB2801987)

There always seems to be a price to pay for jumping on the latest release quickly.  Many who rushed to download and install System Center 2012 Configuration Manager Service Pack 1 got a nasty little surprise in the form of failed client installation and OS deployments.

The problem typically manifests itself in the client deployment logs (%windir%\ccmsetup\ccmsetup.log) with the following error:

Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

InstallFromManifest failed 0×80004005

CcmSetup failed with error code 0×80004005

In the case of an OS deployment, the usual Task Sequence failure screen does not show. Instead, the machine simply reboots in conjunction with the “Setup Windows and ConfigMgr” task and boots directly to the OS, prompting for logon. Viewing the ccmsetup.log file reveals the above error messages.

Microsoft was made aware of the issue and released KB2801987 as a hotfix to resolve it.  The KB article states that the hotfix should be installed prior to installing ConfigMgr 2012 SP1. However, if you have already installed SP1 and are seeing the issue, installing KB2801987 after the fact does appear to resolve the issue.

Microsoft incorporated the hotfix directly into the ConfigMgr 2012 SP1 media as of January 25, 2013. If the media you have for SP1 was downloaded prior to that date, you will need to re-download the updated media.

email

Written by , Posted .
  • http://myITforum.com/myitforumwp/community/members/csimmons/ Chad Simmons

    Some details to know if you have RTM or Refreshed ISO

    RTM
    File Name: SW_DVD5_Sys_Ctr_2012w_SP1_Config_Mgr_EndPt_Protection_MultiLang_-2_X18-84756.ISO
    File Size: 948,314,112
    MD5 Hash: 53e35591d07de3add537de11056afdc2

    Refresh
    File Name: SW_DVD5_SysCtr_2012_w_SP1_Conf_Mgr_and_EndPt_Prot_for_Windows-MultiLang_X18-58783.ISO
    File Size: 948,322,304
    MD5 Hash: 069c24f62a51b7296d54c1529808d64e

  • Ahmad

    Can someone please tell me how to exactly apply the hotfix,is it as simple as run it on all site servers? it did create a package for me under packagesconfiguration manager updates, then what? should i distribute it, deploy it?

    Thanks