SCCM 2012 SP1: Agent install problem starting 11th of January 2013

Starting today, it’s not possible to install the SCCM 2012 SP1 Agent! So it’s also not possible anymore to deploy an Operating System!

The problem is the MSI named “MicrosoftPolicyPlatformSetup.msi” in the %InstallDir%\Client\x64 or x86! The file is signed with a certificate, which was valid until yesterday, 10th of January 2013! And the Agent installation checks this certificate…

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

SCCM 2012 without SP1 (Cum Upd 1): The certificate will be available until the 1st of February 2013.

We will blog and twitter when the MS Patch is available…

Kind regards
Chris

  1. #1 by DB on 12/01/2013 - 16:44

    I spent a day trying to understand why all of a sudden packages were no longer installing via OSD. Has anyone seen anything official from MS on this?

  2. #2 by DB on 13/01/2013 - 16:28

    Follow-up to my previous comment:

    If you apply KB2749655 as a workaround, you will be able to deploy your image successfully.

  3. #3 by http://bing.com/ on 26/02/2013 - 04:53

    Ur article, “SCCM 2012 SP1: Agent install problem starting
    11th of January 2013 | SCCMfaq.ch” Accieee was in fact
    definitely worth commenting down here in the comment section!
    Really wanted to say you truly did a good work. Thanks for the post ,Demetria

  1. Client Agent Certificate Problem – Hotfix KB2801987 « SCCMfaq.ch

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 25 other followers

%d bloggers like this: