Video Screencast Help

USMT and DS 6.9 -Strange Problem

Created: 10 Feb 2013 • Updated: 22 Feb 2013 | 2 comments
This issue has been solved. See solution.

I know that some people in here use USMT for personality migration and I've run into an issue that seemingly nobody has talked about anywhere.  Ever.  So i thought I'd try here (even the Google has no record of this!).

When I run my loadstate.exe command after blowing the Windows 7 image down as the process completes successfully.  However, when I reboot for the first time the computer then reboots itself immediately and removes itself from my domain.

Here's what I know:

  1. The netsetup.log file shows that the computer removes itself from the domain and then adds itself to WORKGROUP
  2. This happens when I run my Run Script command as SYSTEM or I specify my Altiris service account for the security context
  3. This happens if I run USMT from a UNC path, a mapped network drive, or keep all files locally on the computer
  4. This happens with USMT4 as well as USMT5

Here's the kicker.  If run the exact same commandline that I have in my Run Script task from a command prompt on the computer loadstate processes the same but the computer does NOT get kicked out of the domain.

For right now my workaround is that I have to run loadstate, reboot, and then trigger a configure task to add the computer to the domain.  However, that's about 3 more reboots than I believe should be necessary.

FWIW, I'm running DS6.9SP5 MR1.

Has anyone encountered this?

Comments 2 CommentsJump to latest comment

BBC's picture


I have been using USMT for quite some time now to migrate clients from XP x32 to Windows 7 x64 without any issues, so am wondering if you could share the command line you use?

The one I use is the below, just as an example and the task being called off our DS is running in standard, means System account.

loadstate.exe C:\Disney\MIG\USMT /v:5 /c /uel:180 /hardlink /nocompress

It might also be worth checking the XML files being used as the issue could be hidden in there.


HighTower's picture

Thanks for the reply.

In a really round about way I found that writing the captured MIG file to a Ghost-preserved directory on the disc was causing the problems.  How or why?  I have no idea.

Once I worked around that we started getting other undesirable outcomes like USMT creating unwanted desktop icons for Control Panel and Libraries that I could not resolve.  It would also not capture user wallpaper even after using the modifications for the custom.xml file that Microsoft has published.

So, after fighting with USMT for nearly a month I hung it up last night and got PCT working within 2.5 hours.  I'm happily migrating personalities now and I'm not looking back.