Crypt acquire context failed with 0x8009000f after upgrade from sms 2003 to SCCM 2007 SP1
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
April 23rd, 2009 5:21am
Are you in native mode? How did you upgrade the client?
April 23rd, 2009 6:24am
No, I'm in mixed mode. I upgraded the client using the "Client push installation wizard"
April 23rd, 2009 6:26am
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?
April 29th, 2010 9:59am
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.... :)Reddy
November 7th, 2011 8:58am
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).
August 24th, 2012 3:21pm