SCCM 2012 / ADK Use Loadstate Manually

In the past posts I have explained how to create a task sequence to update / refresh computers to Windows 7 from Windows XP.  Most of the time this all works fine and I can just sit back and watch as the computers refresh themselves. Sometimes, though, that is not always the case as I will explain.

Sometimes my task sequences will fail at the 'Restore User Files and Settings' group. It usually happens on laptops. From what I have seen it's because the laptops have went into hibernation, powered down, or have lost network connectivity at this step.

What this means is that the State Store has been saved to the State Migration Point, but the data is encrypted and you can't really do anything with it. You have a bare metal Windows 7 install with no user data. I've read a few ways to accomplish retrieving your data from the State Store, and I'll cover them here.

  • Use MigRecover found here. This method did not work for me at all. I tried both versions to no avail.
  • Use Windows 7 Easy Transfer. This method should work, but I kept receiving errors that WET couldn't open the file. (USMT.MIG) this is after I supplied the User state recovery key. 
  • Just launch the USMT.mig file from the State Store. This launches Windows 7 Easy Transfer. This route did not work either.
  • The fourth and final solution is what worked for me. I used the Windows 8 USMT (ADK 8) not Windows 8.1 USMT (ADK 8.1).

  1. I copied the "User State Migration Tool" folder from C:\Program Files (x86)\Windows Kits\<version>\Assessment and Deployment Kit from my SCCM server to the client computer I'm restoring.
  2. I opened a command prompt and navigated to where I copied the folder.
  3. I opened a SCCM console and navigated to Assets and Compliance -> User State Migration.
  4. I found the computer that I am looking to restore, highlighted it, and clicked View Recovery Information on the Home toolbar.
  5. I copied the User state store location to a text file to I could copy/paste later.
  6. I copied the User state recovery key to a separate .txt file so I could import into the command we'll use in a moment.
  7. Copy both text files over to the computer you're restoring. I copied mine into the USMT folder that we copied over in Step 1. This made it easier to reference at the command prompt.
The final step is to use loadstate.exe to import the data to the computer you're restoring. The command to do this is: (from the command prompt you started on  the computer you're restoring in Step 1)

loadstate.exe <storePath> /decrypt /keyfile:<keyfile> /i:miguser.xml /v:5

http://technet.microsoft.com/en-us/library/cc766226(v=ws.10).aspx

Your computer will start copying over all the profiles that are stored in the State Store. (controlled by the /i switch)

storePath is the path that you saved in the text file and copied to the restoring machine in Step 7. keyfile is the file that contains the User State Recovery Key. Loadstate will read the key from this file. The /i  switch indicates the .xml configuration file that you'd like to use to load the profiles onto the computer. I used miguser.xml when I saved the state so I used it to restore the state. /v is the verbosity level you want for the output. Use loadstate /?  for more options you may use.

Below is a screen shot of the recovery information window.


Comments

Post a Comment

Popular posts from this blog

DISM An error occurred while attempting to start the servicing process for the image.

Image
This is an issue I've had a few times and when you look around on the forums you see multiple answers. I found the right one on an obscure forum that I can't think of right now. The quick answer is this: Use the correct version of DISM to service the image . They must be in the same "generation". For Windows 8.1 and Windows Server 2012 R2 this version is : 6.3.9600.16384 For Windows 8 and Windows Server 2012 and below this version is : 6.2.9200.16384 Background and Setup: I have a Windows Server 2012 box running System Center Configuration Manager 2012 R2. We are in the process of switching our primary OS for new systems to Windows 8.1 Enterprise x64. As I build my images the old fashioned I tend to forget a few things from time to time. In this case I built the image without installing the .NET feature. The instructions to do that are here: http://technet.microsoft.com/en-us/library/dn482069.aspx So I'm following the instructions to get a refresher on
Read more

Deleting Roaming User Profiles Batch Scipt

PREFACE Sorry for the lapse in posts as of late. We're gearing up for a new school year and I've been a bit busy. It turns out this blog doesn't get an amazing amount of views a day, but it gets enough for me to know that it might be helping someone. I write these posts because I've always found myself having an unique issue that most forums do not answer specifically. So most of my posts are for specific issues rather than covering a broad subject. With that said I have a batch script that I wrote today to cleanup my file server. It's very rudimentary so bear with me. INTRO In the education environment you have children that leave the system every year. It's amazing what a child in the extent of a year can rack up in terms of roaming data. We use roaming profiles and folder redirection here for the students data. So every year our servers get loaded with 10s of thousands of files. Every year I used to go through the folders and adjust permissions and
Read more

Optiplex 380 STOP Error: NMI Parity Check/Memory Parity Error

Image
I received a support ticket today from one of our schools saying they had a strange error coming up. I asked the usual questions like did you reboot, what color is the screen, etc. She said it was the BSOD, but it looked different. After going to take a look at the machine I saw the error and I hard rebooted the machine. I came to see this error: At first thought I figured this was a memory error, but it was not. After I removed each stick of RAM one-by-one the error persisted. After a bit of Googling I ran across this article. http://www.dell.com/support/troubleshooting/bz/en/bzdhs1/KCS/KcsArticles/ArticleView?c=bz&l=en&s=dhs&docid=604790 This says it's a NIC issue and you can fix it by uninstalling the old driver and reinstalling. This, however, was not the case. The NIC was failing at POST, far too soon for a driver to be the issue. I also updated the BIOS to A07. (Was on A01) This did nothing as well. I resolved the issue by adding a NIC into the machine an
Read more