shineknox 3 Posted July 20, 2016 Report post Posted July 20, 2016 I've ran into a road block with using USMT on SCCM 2012 R2 version 5.00.8239.1000 and build number 8239. I've made the computer associations before running the capture and the capture works. It only fails when I run the restore task sequence. The source is a windows 7 machine and the destination is running windows 10. The whole process fails when restoring to my windows 10 machine. This is a side by side backup and restore. We are running Win 10 ADK on the SCCM server. Here are some of the errors listed. SMP Root share info response is empty OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1717) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) Request to SMP 'http://servername_of_DP_MP.domain.com'failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) FALSE, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1657) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2866) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ExecuteRestoreRequestToSMP failed (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ExecuteRestoreRequestToSMP(migInfoFromMP), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2931) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ExecuteRestoreRequest failed (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) ExecuteRestoreRequest(), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\main.cpp,84) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) OSDSMPClient finished: 0x00004005 OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054) Process completed with exit code 16389 TSManager 7/20/2016 3:55:14 PM 5232 (0x1470) Thanks, Sunshine Quote Share this post Link to post Share on other sites
shineknox 3 Posted July 20, 2016 Report post Posted July 20, 2016 I was successful with moving a windows 7 profile to a windows 10 machine, using a different machine. The error seemed to be related to two of my test machines; I have a pool of 8 test machines. Is there pre-checks I can setup to make sure there is no issues with machines client? The bad thing about it is that it reports fine in SCCM, but seems to be an error at the client level not thinking it's registered with SCCM. Thanks, Sunshine Baines Quote Share this post Link to post Share on other sites
shineknox 3 Posted July 21, 2016 Report post Posted July 21, 2016 I've deleted the computer account in Active Directory and removed the record from SCCM. I re-imaged the machine and new records were created in both Active Directory and SCCM. I'm still receiving the error below when I try to do a machine policy retrieval. Error: Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client. If the client is not yet registered, this is expected behavior. execmgr 7/21/2016 9:36:01 AM 3740 (0x0E9C) Can not find client site settings execmgr 7/21/2016 9:36:01 AM 3740 (0x0E9C) Not really sure what is going on here. The record in SCCM seems to match up with the client. Thanks Sunshine Quote Share this post Link to post Share on other sites
shineknox 3 Posted July 25, 2016 Report post Posted July 25, 2016 I created another DP with site migration point enabled and still a no go. List of errors below: SMP Root share info response is empty OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4) ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4) ExecuteRestoreRequestToSMP failed (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4) ExecuteRestoreRequest failed (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4) Failed to run the action: Request State Store. Unknown error (Error: 00004005; Source: Unknown) TSManager 7/25/2016 11:23:10 AM 3292 (0x0CDC) Task Sequence Engine failed! Code: enExecutionFail TSManager 7/25/2016 11:23:10 AM 3292 (0x0CDC) The weird thing is that the capture state is working. Any help would be greatly appreciated. Thanks Sunshine Quote Share this post Link to post Share on other sites
shineknox 3 Posted July 25, 2016 Report post Posted July 25, 2016 I love talking to myself. Does anyone use SCCM? Quote Share this post Link to post Share on other sites
shineknox 3 Posted July 26, 2016 Report post Posted July 26, 2016 YO!!!! bump!! Quote Share this post Link to post Share on other sites
anyweb 478 Posted July 26, 2016 Report post Posted July 26, 2016 hi when doing the state restore, what is logged in your loadstate.log, can you attach it here please ? Quote Share this post Link to post Share on other sites
shineknox 3 Posted July 26, 2016 Report post Posted July 26, 2016 Thanks for the assistance. I checked the loadstate.log on the client and it never writes to it. I'm guessing it needs to get past the request state first. thanks for the help. Quote Share this post Link to post Share on other sites
anyweb 478 Posted July 26, 2016 Report post Posted July 26, 2016 would you be willing for me to do a remote session on a virtual client so that i can see what happens ? I use teamviewer Quote Share this post Link to post Share on other sites
shineknox 3 Posted August 1, 2016 Report post Posted August 1, 2016 I appreciate the help. I was able to find a work around by deleting the keys located under ‘HKLM:\SOFTWARE\Microsoft\SystemCertificates\SMS\Certificates*’ on the client side and reboot the machine. Then the restores/captures work as expected. You have any ideas why this could be happening? Thanks Sunshine 1 Quote Share this post Link to post Share on other sites
shineknox 3 Posted August 1, 2016 Report post Posted August 1, 2016 One thing i can't stand about forums is no one responding back to how they fixed their issue. I hope this helps someone down the road. I just got off the phone with support and this was their fix as well. They said it's a client side issue with certificates being corrupt. ERROR: Error. Status code 500 returned OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Received 1231 byte response. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) pReply != NULL, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2391) OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) SMP Root share info response is empty OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1717) OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Request to SMP 'http://myservername.domain.com'failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Sleeping for 60 seconds before next attempt to locate an SMP. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Retry number 2 OSDSMPClient 7/25/2016 4:26:28 PM 5656 (0x1618) Microsoft's response ++ It looks like there is certificate issues while performing the restoration task. ++ Please run following command under PowerShell (As Admin ) · Remove-Item -Path ‘HKLM:\SOFTWARE\Microsoft\SystemCertificates\SMS\Certificates\*’ -force; · restart-service ccmexec Sunshine 1 1 Quote Share this post Link to post Share on other sites
BThomson1984 0 Posted August 1, 2017 Report post Posted August 1, 2017 A year to the day. :-) This post has been extremely helpful, thank you. We're on 2012rw SP1, and having exactly the same issues (we need to upgrade), however in the meantime, this has worked for us. Thanks Quote Share this post Link to post Share on other sites
TeachesGeeks 0 Posted January 28, 2019 Report post Posted January 28, 2019 Created an account just to say thanks Sunshine. Had this issue today and after a ton of bad fix suggestions, I found this and it immediately fixed the issue. Thank you! Quote Share this post Link to post Share on other sites