FIM CM was unable to decrypt necessary data error

  Troubleshooting Steps: Enable FIM CM Tracing:( ) Enable CAPI Logging: ( ) After looking at the CM logs we seen that the Cm was unable to find the correct certificate. "DOMAIN\USERA" "DOMAIN\USERA" 0x00000F60 0x00000006 Data to be decrypted: MIIDZAYJKoZIhvcNAQcDoIIDVTCCA1ECAQAxggF4MIIBdAIBADBcMEUxEzARBgoJkiaJk/IsZAEZFgNsb2MxGzAZBgoJkiaJk/IsZAE=. "2014-03-19 14:37:27.14 -06" "Microsoft.Clm.Security.Principal.RevertToSelfContext" "Microsoft.Clm.Security.Principal.RevertToSelfContext RevertIfImpersonating()" "DOMAIN\USERA" "DOMAIN\USERA" 0x00000F60 0x00000006 Reverting to the process identity…


FIM Workflow calling PowerShell 3.0 from 2.0 pipeline

In this scenario a customer was trying to use a PowerShell 3.0 cmdlet through a PowerShell custom activity. In this scenario we need to use remoting. I will not cover remoting in this article but provide links for your research. In this case we will be calling the local host of the FIM service machine…


Enabling Windows Installer verbose logging via registry

Recently , I had sever instances were we needed a installer log for change mode for FIM. I had the details but my colleague Peter documented this quite we for us: Thanks Peter