UPDATE: Microsoft has now released a hot fix this issue. Read about it here: Good news: ConfigMgr 2012 SP1 client hotfix for MicrosoftPolicyPlatformSetup.msi error available
Here’s another issue that is becoming a bit more common as more folks are rolling out SP1 for ConfigMgr 2012, and one you should be aware of as there is no “fix” yet, just a workaround.
From ghostofdre in the forums:
I was having trouble installing the CM12 SP1 client (upgraded yesterday) on a Windows 8 Desktop (Machine previously had no SCCM client). I pinned down the problem to the following error in the ccmsetup log file on the client.
Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101 ccmsetup 11/01/2013 1:03:50 PM 4928 (0x1340)
I had a look at the MSI on my site servers client source directory went into the details tab and selected the details on the name if the signer. From there I brought up the certificate information and noticed the certificate had expired on the 11/01/2013 (*Australian Date format DD/MM/YYYY) which is today. It’s the same for the x86 and i386 client directories.
I successfully got the client installed by manually installing that particular MSI. Just wondering if anyone else is seeing this since SP1? I haven’t tried any other client installs.
So far there is no solution other than the workaround that ghostofdre describes, i.e., performing a manual client installation.