The Realm of the Verbal Processor

Jarvis's Ramblings

Restore User State failed – 00004005

I’ve been troubleshooting an issue with Computer Associations in SCCM. The issue that I have seen multiple times is that the state capture appears to run successfully…there is a USMT file of the size that I expect in the State Migration Point folder. However when I run the state restore, it fails very early in the process. As it is requesting the state store, it fails out with a message that states:

Task Sequence: Restore User State has failed with the error code (0x00004005). Please contact your system administrator or helpdesk operator.

Well…I am my system administrator, and this error is bothering me!

Once I dig into the smsts.log file, I see these errors:

SMP request to “SCCM.fqdn” failed with error: E_SMPERROR_RESTORING_CLIENTID_NOT_FOUND (207)

Request to SMP ‘SCCM.fqdn’ failed with error (Code 0x80004005). Trying next SMP.

FALSE, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1698)

Failed to find an SMP that can serve request after trying 4 attempts.

pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 …

ExecuteRestoreRequestToSMP failed (0x80004005).

ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\main.cpp,80)

OSDSMPClient finished: 0x00004005

Process completed with exit code 16389

I’m taking a wild guess here…and I could be wrong…I’ll be posting on Technet and updating this post when I find out more. My guess is that this is tied to when I created the computer association linking the old computer with the new one. This is a side-by-side migration…replacing a user’s old computer with a new one. I ran the capture TS on her old computer. The errors above are on her new one. I am wondering if it matters when the computer association linking the old to the new is created. I forgot to create that association until after the capture TS had already run on her old computer. That capture TS created an “in-place” association for her old computer. After the capture was complete, I created a side-by-side association. Both of these are tied to the same state location.

I may be completely wrong here (certainly wouldn’t be the first time), but is there anything that the State Capture TS puts into what it uploads that restricts what it will restore to? I.E. does the side-by-side association need to exist before running the Capture TS for it to be able to restore to the new computer?

Another possibility that will be determined when I get the smsts.log off of the old computer (laptop…user has it off site today) is if it fits into the discussion of this thread…where the status message is not received by the site server that the capture process is complete…so the state is not recorded as completed.

[Update: I got the log file from the user this morning. It does fit that thread above. I’m posting to TechNet to see if I can get an answer as to how to automatically resolve this issue. I’ve seen it happen way too frequently.]


May 8, 2008 - Posted by | ConfigMgr


  1. This error usually occurs when the computer association is created AFTER the source machine had it’s user state backed up. Computer associations must be made before user state is ‘stored’. Hope this helps.

    Comment by Jon Lambert | July 21, 2008

  2. Thanks for that comment Jon. That seems to confirm my original “wild guess” that I had earlier dismissed…and had crossed out in the post until this morning.

    Comment by Jarvis | July 21, 2008

  3. Hey there, I know this is a couple of years old, but I am having the same issue. Every time I do a capture of my source it shows up in SCCM as an In-place even though I have created a computer association. When I try to pull down on the new system, it errors saying it cannot find something to restore. How were you able to overcome this issue?

    Comment by James | September 16, 2010

  4. The side-by-side association needs to exist before running the Capture TS for it to be able to restore to the new computer. did you create the association BEFORE running the capture Task sequence?

    If you did, I’m afraid I don’t know. I would post to to see if you can get an answer there.

    Comment by Jarvis | September 17, 2010

  5. Hey Jarvis.

    Long time no see (MMS) Hey, we are migrating from XP to 7, and having some fun with USMT! I think I’ve got in place figured out (advertise bein full os, capture, boot pe, deploy, restore.)

    However, we are replacing about 400 machines, and they will be brand new. You mention that I need to have the side-by-side comp assco in place to restore to the new computer. The new machines would be bare metal. Do I have to get names/MAc addresses for each of them before hand? eyikes. I guess it’s doable.

    Here’s a crazy idea, but I don’t know how to build it. Could I run the USMT capture via an advertised IN Full windows TS and put it somewhere on the network. Then, I want to PXE boot a PC and PICK which user state to restore.

    maybe that’s crazy… Do you have/know of a good guide for side by side (step by step)? I’ve been using some good info from the windows noob site.

    Thanks Jarvis!


    Comment by Henry Bosch | September 24, 2010

  6. Hey Henry…good hearing from you. Good news and bad news. I just spent the last fifteen minutes typing a long response to this message…but then I accidentally clicked elsewhere on the page before posting the reply and lost it all. So…you are going to get a much shorter version of the reply.

    See if you can get a list of the MAC addresses from your computer manufacturer. Most will provide this although you might have to find out who to ask in order to get it. With that you can create a text file for importing the computers in as a group…much easier.

    Short answer to the “PXE boot a PC and pick which user state” question…no. The association has to exist first or it will fail.

    A possible (and completely untested) way you could do it would be to kick off the USMT capture/restore from “run command line” tasks…not using the State Migration Point at all. You would need to create a vbscript wrapper around it to customize the folder that it saved into on a network share (to keep it from overwriting). Then you could create an HTA to allow you to pick which folder to restore from. I don’t like this for two reasons though.
    1. It doesn’t scale. You lose all of the location awareness of ConfigMgr.
    2. I don’t know that it is any easier than simply creating the association in the first place.

    Hope that helps.

    Comment by Jarvis | September 27, 2010

  7. Thanks Jarvis!

    It does help… I’ve now been able to succesfully build my image with refresh/replace scenarios. I think I’ll just have to work out a process for replacement (import the PC’s via text, and then have the deployment guys match who get’s which before they roll).

    Two things left to do now:

    1.) Decide how to handle roaming profiles (I’m tempted to turn them all of, delete em, and turn then back on once the migration is complete). We dont use any redirection, or I’d do that instead.

    2.) customize what USMT brings acrosss. Right now I’ve got it sucking up everything (random folders on the C:\ included).



    Comment by Henry Bosch | September 30, 2010

  8. Thanks Jarvis,

    I’ve same problem, I forgot to create a computer association before capturing user state and now I have about 70 GB of useless data. I also tried to restore manually with loadstate.exe command but the problem here is about the encryption key used bu SCCM. Is there any workaround to recover the encryption key used by SCCM when no computer association is configured or my profile is lost forever?

    Thanks in advanced

    Comment by Tiziano | November 9, 2010

  9. Has the source computer already been formatted? If not, create the association, then re-run the capture.

    I don’t know of a way to use the captured profile if the association wasn’t created ahead of time. although you just got me thinking…perhaps if you reinstalled on the original computer with a restore user state. Doing a re-image doesn’t require an association, so that might work. although a bare metal install creates a new client record, so it might not.

    Your best shot is to re-capture from the source computer. Hopefully that is an option for you.

    Comment by Jarvis | November 9, 2010

  10. The source computer was wiped and reinstalled manually because of a particulary configuration, so no way to re-run the capture, no data to capture :( About the In-Place upgrade i think that the process of the caputer/restore of the profile, in the case of an in-place upgrade, “live” only inside the Task Sequence, something like a variable defined at some point of the task that is lost when TS complete.
    I really think that the profile is lost, but I also think that is easy to make an error that drive to loose important user data.

    Thanks for you support and your readiness answer.


    Comment by Tiziano | November 9, 2010

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: