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:
- The netsetup.log file shows that the computer removes itself from the domain and then adds itself to WORKGROUP
- This happens when I run my Run Script command as SYSTEM or I specify my Altiris service account for the security context
- This happens if I run USMT from a UNC path, a mapped network drive, or keep all files locally on the computer
- 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?