I sent the script. Let me know if it does not come through for you.
On Tue, Jul 22, 2014 at 8:40 AM, Giroux, Eric J <[email protected]> wrote: > I have dealt with an issue similar to this after QMM migrated users from > one domain to another. The key for the OSD was to ensure the task sequence > was not running while a migrated user was logged on. Had to add a reboot > prior to USMT steps. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Burke, John > *Sent:* Monday, July 21, 2014 9:48 AM > *To:* [email protected] > *Subject:* [MDT-OSD] Domain AD Migrated via Quest tool - NOW USMT won't > let me work. > > > > Trying to migrate a domain that was still at xp, but the issue likely > occurs windows7 to windows 7 too. The state capture step fails with > 0x8007001a > > > > Capture User State > > State Capture > > 11135 > > The task sequence execution engine failed executing an action > > -2147024870 > > e.log" > /progress:"C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstateprogress.log" > /i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\unsecure.xml" > /i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\MigApp.xml" > /i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\MigDocs.xml/i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\MigUser.xml" > /i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\migEPF.xml" > /i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\MigEEPC.xml" > /i:"C:\_SMSTaskSequence\Packages\NS20015C\x86\Exclude.xml" /nocompress > /hardlink /ui:S-1-5-21-758742814-1263097602-310601177* /ue:QC700406\* > Log messages are being sent to > 'C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstate.log' > Starting the migration process > Error while trying to start the migration process Failed. > Software malfunction or Unknown exception > See the log file for more information. ScanState return code: 26 > USMT returned exit code (0x0000001a). Look USMT log file scanstate.log for > detail error message. > POSDMigrateUserState finished: 0x8007001a > > > > > > working on getting a fresh set of the scanstate logs. I lost the logs > because to get around this i can connect to the system and delete the > Profiles entries in the Profiles registry key or delete the profile from > the system. These users seem to have a new profile that points at an older > profile on the system. > > > > > > anyone run into this kinda thing before? >
