I've noticed an issue with the last two cumulative updates for MIM CM that I've tried, including the recently released KB3134725. It appears that updated version of "Microsoft.Clm.PerfCounters.exe" is not signed with a strong name which ends up causing the installation to rollback (at least on Windows Server 2012 R2). If I disable strong name validation for the assembly via the registry, the installation completes successfully but I can hardly imagine that this was the desired configuration.
Here is the output of the 'sn.exe' command from the Windows SDK on the extracted file in the updated MSP and the file from the original MIM installation disk, respectively:
C:\>sn -vf "<path to extracted MSP files>\VL\Microsoft.Clm.PerfCounters.exe"
Microsoft (R) .NET Framework Strong Name Utility Version 3.5.30729.1
Copyright (c) Microsoft Corporation. All rights reserved.
<path to extracted MSP files>\VL\Microsoft.Clm.PerfCounters.exe is a delay-signed or test-signed assembly
C:\>sn.exe -vf "C:\Program Files\Microsoft Forefront Identity Manager\2010\Certificate Management\Bin\Microsoft.Clm.PerfCounters.exe"
Microsoft (R) .NET Framework Strong Name Utility Version 3.5.30729.1
Copyright (c) Microsoft Corporation. All rights reserved.
Assembly 'C:\Program Files\Microsoft Forefront Identity Manager\2010\Certificate Management\Bin\Microsoft.Clm.PerfCounters.exe'is valid
Does anyone know if Microsoft is aware of this issue and working on a patch?
Bryan Berns