SCCM and USMT

[CCampbell]

Hello,

 

In prep for a Windows 7 to Windows 10 migration during the upcoming summer I'm attempting to get the USMT up and running. We're running SCCM 2012 R2.

 

I've followed a good bit of the guides available up until this point and I believe my TS is semi-correct. Basically, for my TS I made a new TS through the Wizard and chose to implement the steps suggested through the Wizard for Migration. I then just customized the rest of it.

 

There was some mention of an XML file needing to be created, but from what I took away I didn't need to do this in R2 or if I simply just wanted all profiles.

 

Seen here:

 

 

Anyway, I ran the TS with that sequence on my test machine that I had some test files on, etc. From what I was able to tell the capture state had worked okay, but going back through the logs I guess I had been wrong.

 

So here are the logs from the test machine--

 

Scan State Log:

 

 

2016-01-26 14:10:53, Info [0x000000] SCANSTATE.EXE Version 6.3.9600.16384[gle=0x000000b7]

2016-01-26 14:10:53, Info [0x000000] USMT Started at 2016/01/26:14:10:53.560

2016-01-26 14:10:53, Info [0x000000] Command line: C:\_SMSTaskSequence\Packages\MP7000B1\scanstate.exe C:\_SMSTaskSequence\UserState /o /localonly /efs:hardlink /c /hardlink /nocompress /l:C:\Windows\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\Windows\CCM\Logs\SMSTSLog\scanstateprogress.log /i:C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migdocs.xml /i:C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migapp.xml

2016-01-26 14:10:53, Error [0x000000] Script file is not present: 'C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migdocs.xml'[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] Failed.[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] An error occurred processing the command line.

Unable to find a script file specified by /i[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] USMT Completed at 2016/01/26:14:10:53.565[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] * USMT error code 28: [gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] | An error occurred processing the command line.[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] | Unable to find a script file specified by /i[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]

 

Load State Log:

 

 

2016-01-26 14:10:53, Info [0x000000] SCANSTATE.EXE Version 6.3.9600.16384[gle=0x000000b7]

2016-01-26 14:10:53, Info [0x000000] USMT Started at 2016/01/26:14:10:53.560

2016-01-26 14:10:53, Info [0x000000] Command line: C:\_SMSTaskSequence\Packages\MP7000B1\scanstate.exe C:\_SMSTaskSequence\UserState /o /localonly /efs:hardlink /c /hardlink /nocompress /l:C:\Windows\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\Windows\CCM\Logs\SMSTSLog\scanstateprogress.log /i:C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migdocs.xml /i:C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migapp.xml

2016-01-26 14:10:53, Error [0x000000] Script file is not present: 'C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migdocs.xml'[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] Failed.[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] An error occurred processing the command line.

Unable to find a script file specified by /i[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] USMT Completed at 2016/01/26:14:10:53.565[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] * USMT error code 28: [gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] | An error occurred processing the command line.[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] | Unable to find a script file specified by /i[gle=0x00000006]

2016-01-26 14:10:53, Info [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]

 

 

Anyway, I guess where I'm at is that I'm just confused as to what is causing my issue. I've looked into Errors 27 and 28 and there's not much more to it that isn't explained in the logs there. Is there something more I need to fix in the TS so that it can reference a script file (probably that darned XML)?

[anyweb]

Script file is not present: 'C:\_SMSTaskSequence\Packages\MP7000B1\amd64\migdocs.xml'[gle=0x00000006]

make sure that the xml file listed above is present in the MP7000B1 package

 

cheers

niall

[CCampbell]

Thanks for the quick reply.

 

I double checked the package, which I had copied from

C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\User State Migration Tool

to my sources folder. Since I'm working with 64 bit systems I was concerned with the amd64 specifically. Migdocs.xml was both present in the above location and my sources folder.. which package MP7000B1 is the USMT package I created.

 

Is there anything else I can check? I found a post on Technet detailing the error, specifically saying;

 

 

 

This error is returned because both scanstate.exe and loadstate.exe assume that the working folder is the current directory -- where the command is execute -- and not the directory wherein the executable is located. Since the XML files do not exist in my profile -- the current directory -- the command fails. To fix the issue, first switch to the directory containing your USMT files using the CD command, or specify full paths to the XML files with each /i.

 

But I was under the assumption that the Task Sequence would account for that.

[CCampbell]

I think I solved it, at least to my knowledge, testing and the logs show.

 

I changed from "All User Profiles" to specific settings and put in the miguser.xml and migapp.xml (with no configuration to either.) Bit more testing to do, but I did a refresh of the machine and the puppies I put on the desktop were retained.