I've upgraded clients from SMS 2003 SP3 to SCCM 2007 SP1.

In the SCCM console some ressources are showing as not being client.

If I look on the machine, I can see that client is installed but the client cannot communicate with the management point.

CCMEXEC.log shows the following error message :

Crypt acquire context failed with 0x8009000f.

Failed to create certificate 8009000f CcmExec 21/04/2009 9:49:10 1948 (0x079C)

CCMDoCertificateMaintenance() failed (0x8009000f).

So, the issue is related to certificate

If I go to C:\documents and settings\all users\Application Data\Microsoft\Crypto\RSA\MachineKeys and delete the file begining by 19c5cf... and then restart the client the problem is solved.

Can someone explain what is happening ?

What can I do to prevent this problem

Kind regards

Are you in native mode? How did you upgrade the client?

No, I'm in mixed mode. I upgraded the client using the "Client push installation wizard"

• Proposed as answer by Shabe Thursday, April 29, 2010 1:59 PM

No, I'm in mixed mode. I upgraded the client using the "Client push installation wizard"

• Proposed as answer by Shabe Thursday, April 29, 2010 1:59 PM

No, I'm in mixed mode. I upgraded the client using the "Client push installation wizard"

• Proposed as answer by Shabe Thursday, April 29, 2010 1:59 PM

No, I'm in mixed mode. I upgraded the client using the "Client push installation wizard"

I am also having the same issue. I too have mixed mode in my environment and I am also having the same issue as mentioned by LMichel. What will happen if we delete the file which starts by 19c5cf?

in Windows 7,

From C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys

Delete the key which starts with 19c...

and restart the SMS AGENT HOST SERVICE.

This will resolve the issue.... :)

In Server 2008 R2 SP1 (when Pushing Out SCCM 2012 clients)

I just added another account to the security (local Administrators) for the key which starts with 19c5cf...

and restarted the SMS AGENT HOST SERVICE.

Thats also resolved the problem. (NETWORK was the only security account on the key file).

• Edited by Arnie52 Wednesday, August 22, 2012 6:01 PM
• Proposed as answer by Les_H Friday, August 02, 2013 6:33 PM

In Server 2008 R2 SP1 (when Pushing Out SCCM 2012 clients)

I just added another account to the security (local Administrators) for the key which starts with 19c5cf...

and restarted the SMS AGENT HOST SERVICE.

Thats also resolved the problem. (NETWORK was the only security account on the key file).

• Edited by Arnie52 Wednesday, August 22, 2012 6:01 PM
• Proposed as answer by Les_H Friday, August 02, 2013 6:33 PM

In Server 2008 R2 SP1 (when Pushing Out SCCM 2012 clients)

I just added another account to the security (local Administrators) for the key which starts with 19c5cf...

and restarted the SMS AGENT HOST SERVICE.

Thats also resolved the problem. (NETWORK was the only security account on the key file).

• Edited by Arnie52 Wednesday, August 22, 2012 6:01 PM
• Proposed as answer by Les_H Friday, August 02, 2013 6:33 PM

I added local administrators and System with access to this file, similar to the other keys in the folder. Restart agent host service, client registered immediated. Also noticed key went from 44 bytes to 4kBytes in size.

I came here from jason"s thread.The account rights is OK.The issue gets resolved only after deletion.I need to do this on many computers.How can i automate this as there is no communication from the clients to MP ?

Hi

I face the same problem with error 0x8009000f, this is taken from CertificateMaintenance.log on one of my machines, how will you know which file to delete in C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys ??

Crypt acquire context failed with 0x8009000f. CertificateMaintenance 30-04-2015 00:21:40 4088 (0x0FF8)
Failed to create certificate 8009000f CertificateMaintenance 30-04-2015 00:21:40 4088 (0x0FF8)
CCMDoCertificateMaintenance() failed (0x8009000f). CertificateMaintenance 30-04-2015 00:21:40 4088 (0x0FF8)
Raising pending event:
instance of CCM_ServiceHost_CertificateOperationsFailure
{
 ClientID = "GUID:914A3E7C-A96F-4439-B36E-FB8D55501FB8";
 DateTime = "20150429222140.301000+000";
 HRESULT = "0x8009000f";
 ProcessID = 4072;
 ThreadID = 4088;
};
 CertificateMaintenance 30-04-2015 00:21:40 4088 (0x0FF8)
CCMDoCertificateMaintenance() raised CCM_ServiceHost_CertificateOperationsFailure status event. CertificateMaintenance 30-04-2015 00:21:40 4088 (0x0FF8).

I run SCCM 2012 SP1 CU5 here.