Capture USMT but deploy using K1000

Hi, we are using the K2000 to capture USMT but are not using the K2000 to deploy it. Is there a way data from the K2000 USMT capture can be deployed to a machine without a Scripted Install or System Image deployment? Can the K1000 be used for this deployment? The reason being Dell is sending us a customized image we just need to capture USMT from existing machine and deploy to a new machine


0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: Hobbsy 2 years ago
Red Belt

Why not stop spending money with Dell and just deploy the images and USMT yourselves? You have an SDA it only takes hours to get it working for you

  • True xD, or contact KACE Pro Services, I'm sure for far less money they will teach you how to setup your Images and do it for you. - Channeler 2 years ago
    • Genius, if only we knew someone from KACE PS........oh hang on, yes .....Me!! ;o) - Hobbsy 2 years ago
  • Hi Hobbsy, thanks for replying. We did try to use the SDA but it kept failing trying to deploy to Windows 10 1809. This is why we are looking to see if there is another way to deploy USMT besides SDA - kace_admin 2 years ago
    • If you would like to setup a call for us to take a look at the issue, then please email me directly and we can get it scheduled, you can at least then make an informed decision - Hobbsy 2 years ago
    • for 1809, your SDA needs to be in version 6.1, also make sure you are using an 1809 based KBE - Channeler 2 years ago
Posted by: Channeler 2 years ago
Red Belt

Top Answer

I believe this is not possible..... out of the box.

The KACE SMA (formerly known as K1000), doesn't have any built in modules\tools for USMT.

That means you will need to write your own BAT or Powershell script to Deploy previously captured states using Microsoft's LoadState Tool, then push the Script via SMA's Scripting Module.


Posted by: rodriguez.adam@healthnow.org 2 years ago
White Belt

At this point we stopped using the K2000 USMT due to UAC causing us issues.  We switched to doing it all in the K1000 with Scripts and a file share.  

We used to use the K2000 to do the capture and use a script we created in the K1000 to load it.  Basically would download the USMT file from the K2000 and place it locally on the Machine you were deploying. We would put it in the root of C:\.  We still do this but instead getting it from the K2000 we get it from the file share.  

The K1000 Script we use contains the dependencies for the Windows ADK for USMT then we call the LoadState executable with these parameters.  "LoadState.exe C:\USMT /i:migapp.xml /i:miguser.xml /c /r:3 /w:10 /l:C:\usmt.log /v:13".  Note, we put the USMT.mig file into C:\USMT\USMT.  

Hope this helps

  • Hi Adam, thanks for replying. What did you mean by "The K1000 Script we use contains the dependencies for the Windows ADK for USMT"? What kind of dependencies have you added besides calling loadstate? Thanks - kace_admin 2 years ago
    • https://docs.microsoft.com/en-us/windows/deployment/usmt/usmt-technical-reference

      Once you install the ADK, Just zip and upload the contents of C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\amd64. The xml's are in there and you can edit them to match the USMT Profile you have set up in the K2000 - rodriguez.adam@healthnow.org 2 years ago
      • Hi Adam, I was able to run loadstate.exe C:\USMT without any parameters on the destination machine and it completed the restore successfully. I did this manually to test if it would be successful

        I am not sure how to move the amd folder to each destination computer using the K1000. Was it a batch file you created? Can you share that file?

        Thanks - kace_admin 2 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ