Hello, I have a CM site in mixed mode. I've deployed an SMP to a second server in addition to the usual site systems. All prerequistes were met and the SMP log on the server indicates that the SMP installation successfully completed. I have built out a task sequence that includes the 'Request Use State Store' task. When I do so I recieve errors in the smsts.log file as indicated below: SMP request to "sccm_svr2.sccm.com" failed with error: E_SMPERROR_ENCRYPTKEY_EMPTY (103) 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2564) ClientKeyRequestToSMP failed (0x80004005). ClientKeyRequestToSMP( m_sSMPServer, m_uPort, m_ClientInfo, sKeyInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1743) ClientRequestToSMP:oRequest failed. error = (0x80004005). Request to SMP 'sccm_svr2.sccm.com' failed with error (Code 0x80004005). Trying next SMP. Any ideas? Thanks! --g

I really hate to do the ole "Me too" or +1, but i'm running into the same situation and cannot find any docs on how to resolve this. Being in Mixed Mode, I didn't think that I had to have a particular cert for this, and that it would create it automagically. I'm in a VM demo environment, so the Site Server and SMP are the same box. Seems as if the cert would be ok. Anyone out there solving this one

I have heard of other people having the same error, but it usually goes away within a day of the SMP being installed. I have tried to reproduce this issue here without any success. Could you please contact Microsoft Support (http://support.microsoft.com) and work through them to resolve the issue. Thanks, -Bryce

Hi guys, I am also having the same issue - what was the resolution to the issue? I am finding various mentions of the problem but no clear idea of how to proceed....

On the smp, open mmc.exeAdd the certificates snap-in for the computer accountlocate the sms "folder", what do you see?"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

I think I am having the same issue. Here is the situation.Current Config: SCCM 2007 SP1 MDT 2010 WAIK 1.1 Server1: Site Server & SQLServer2: IIS, MP, RP, SUP, DP and State Migration Point (SMP) Error on ConfigMgr Status Message Viewer for Component SMS_STATE_MIGRATION_POINT : "SMS State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer Server2Name. Possible reasons are SMP certificate is not yet signed by Site Server." Registry on Server2 (SMP) HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\SMP\Statestore\SignedSerializedSMPKey has no data. Error on ConfigMgr Status Message Viewer for Task Sequence Advertisement: "The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned." I think what I need to know is how to get the correct SignedSerializedSMPKey value into that registry entry.Please advise.

It usually takes 0-60 minutes after you install SMP on the site server for the signed serialized key to be generated. You can alternatively modify any of the SMP properties after it is installed to speed up the process.

Check the following: 1. Of Course make sure the XP System does not have KB974571 is not installed. 2. Run the Certfix on the XP Client, and all systems actually (from extracted 977203) For the Capture State theTask Sequence , which is its own Task Sequence it must do the following: 1. Request State Store 2. Capture User State 3. Release State Store (this part is not doucmented very well it seems, and was what I had missing...without this you get an error 0x80004005) For the Restore State Note:It should be the last thing in your OSD Task Sequence 1. Restart the Computer Task (use currently installed O/S) 2. Request State Store 3. Restore User State 4. Release State Store I hope the above helps out and sees you through to success!!!David Baur