Jump to content


  • 0
anyweb

using Offline Mode in Windows PE using USMT 4 via a task sequence in SCCM 2007 SP2

Question

hi all,

 

Note: This post has been reproduced in a webcast, so if you'd like to see a video of Offline Mode in WinPE then click here

 

 

 

well this feature in USMT 4 is handy, as it allows you to do a scanstate while in Windows PE in other words, not in the OS so no problems with services running or applications running meaning that you get to backup everything you want without any locked files stopping from doing so.

 

Offline mode does however have some restrictions, read this page on Technet for details of that. To get around these restrictions and to migrate wallpaper see here, to migrate your network printers see here.

 

 

Great, but how do I do Offline Mode in Windows PE using SCCM ?

 

according to Microsoft, we can use the /offlinewindir switch in USMT 4 with scanstate.

 

/offlinewindir: "path to a windows directory"

 

 

This option specifies the offline Windows directory that the ScanState command gathers user state from. The offline directory can be Windows.old when you run the ScanState command in Windows or a Windows directory when you run the ScanState command in Windows PE. This option is incompatible with the /offline option.

 

However, implementing it isn't so straigtforward as you've probably already discovered and documentation about getting it to work within SCCM is as far as I can see pretty much non-existant,

so here courtesy of windows-noob.com is one way of doing it, feel free to show us other ways.

 

The theory behind this:-

 

As the Capture User State Step in a standard task sequence can only run in Windows, we cannot use that step to do our scanstate while in Windows PE, therefore we will use some tricks to run scanstate from WinPE.

 

To do this we create two special packages, the first package contains a batch file which calls the scanstate.exe file and the second package is the entire USMT X86 scanstate files and folders, (note: in this example we are using scanstate from the X86 folder).

 

This means that we create a separate package to the normal USMT4 package and this is only because this example is a workaround or proof of concept to prove that Offline Mode in Windows PE can be done via a Task Sequence in SCCM.

 

Update: If you would like sample code to check for and use the correct USMT architecture in offline mode then see Peters post here

 

 

Get your lab ready

 

We need a Windows XP client machine to test scanstate on and you should enable the F8 command prompt option in your boot.wim (you'll need it).

 

 

The Task Sequence

 

You can use this Task Sequence in SCCM by importing it. Please note this task sequence only has the 4 groups in it, if you want the 4 groups plus OSD then use the other Task Sequence further down.

 

Offline Mode in Windows PE using USMT 4.xml

 

The task sequence depends on three packages, the X86 bits from your USMT 4 (ie: copy everything in the X86 folder from C:\Program Files\Windows AIK\Tools\USMT folder. There are two versions, one for 32bit (X86) and one for 64bit (amd64), we are only using the X86 bits in this guide), the Batchfile

 

offline mode references.jpg

 

 

I break up my task sequence into four distinct groups, Set, Create, xcopy and Run

 

SET

 

 

In the Set group I set SystemDrive to c: (otherwise it will try and do this on the windows PE x: drive)

 

set systemdrive variable.jpg

 

Next we set the OSDStateStorePath Task Sequence Variable to %systemdrive%\USMToffline which translates to c:\USMToffline, this directory will store our migration data during scanstate operations and when the new os is being applied.

 

set osdstatestorepath.jpg

 

Finally we set the hardlink load parameters

 

set hardlink load parameters.jpg

 

 

CREATE

 

In the Create group we just create two folders, c:\USMToffline,

 

create usmt offline folder.jpg

 

and c:\USMTbits\X86

 

create usmt bits folder.jpg

 

 

the c:\USMTbits\X86 will store all our scanstate native files.

 

 

XCOPY

 

In the xcopy group we do the clever stuff, we copy the X86 USMT stuff to the newly created folder, and then we copy our batch file for later user.

 

xcopy usmtbits.jpg

 

The batch file itself has the following contents

 

 

@set USMT_WORKING_DIR=%~2%\USMTbits\x86

"%~2\USMTbits\x86\scanstate.exe" "%~1" /c /o /hardlink /efs:hardlink /nocompress /offlinewindir:c:\windows /v:5 /l:%~2\windows\TEMP\SMSTSLog\scanstate.log /progress:%~2\windows\TEMP\SMSTSLog\scanstateprogress.log /i:%~2\USMTbits\x86\miguser.xml /i:%~2\USMTbits\x86\migapp.xml

 

xcopy runscanstate.jpg

 

You can download the batchfile below however you must rename it back to .bat

 

runscanstate-offlinewindir.bat.txt

 

 

RUN

 

The Run group does the actual running of the batch file and passes two variables to the file.

 

do scanstate.jpg

 

 

 

Testing Offline Mode.

 

Create an optional advertisement to a Migrate XP to W7 X86 collection for the Task Sequence and PXE boot your XP client (press F12 first....), select the Task Sequence when the wizard appears,

 

ts wizard welcome.jpg

 

at this point press F8 to bring up the command prompt, you are doing this to verify that your data is getting migrated in OFFLINE mode. So here we can see the command prompt is open.

 

cmd prompt before ts starts.jpg

 

Ok switch back to the TS and start the task sequence. You will see it starts creating the folders, copying the USMT stuff and our batch file(s) and then actually running the scanstate command.

 

copying.jpg

 

do x86 scanstate.jpg

 

Once it is completed your migrated data will now be stored in C:\USMToffline\USMT

 

browse it and verify

 

migrated data stored in usmt offline folder.jpg

 

If you want to see a working SMSTS.log file from the above test see below

 

smsts.log

 

 

Ok now what ?

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

So how will I be able to use your xml files and other associated items if I'm going from windows xp 32 bit to windows 7 64 bit as far as files and folders within the task sequence?

 

Paul

Share this post


Link to post
Share on other sites

  • 0

Thanks for all your helpful SCCM 2007 guides they have been great (understatement) references. I was nearly there and about to celebrate until I noticed that the migrated files have not inherited permissions of their user and that there are padlocks on all of the files that migrate across. For example username JB had a document called letter.txt on their desktop which is migrated across. The document is there but when checking the permissions of the file only myself, administrators and system have full control on it and there are no other permissions meaning it is useless for JB. On checking the parent folder Desktop this has the correct permissions and allows user JB full control.

 

I know I can simply inherit the permissions but that won't be handy when doing this on 1000's of PCs. Is this anything that has been experienced before I couldn't see it on the previous 14 pages.

 

Thanks.

 

Edit : I tested this on Windows 7 to Windows 7 migration, is this specifically XP to Win 7?

 

interesting i havn't seen this behaviour, right now i'm using the bitlocker frontend HTA (which incorporates this functionality), and i've not noticed any padlocks, can you show me a screenshot and are you using Configuration Manager 2012 or 2007 for this ?

Share this post


Link to post
Share on other sites

  • 0

So how will I be able to use your xml files and other associated items if I'm going from windows xp 32 bit to windows 7 64 bit as far as files and folders within the task sequence?

 

Paul

 

easy, use x86 to capture (scanstate) and x64 to restore (loadstate) in terms of USMT.

Share this post


Link to post
Share on other sites

  • 0

This is really helpful post.

 

i followed the process but it is failed in Runscanstate(do X86 Scanstate) with below mentioned error . can you please help me on this

 

Failed to run the action: do X86 Scanstate.

The specified disk or diskette cannot be accessed. (Error: 0000001A; Source: Windows)]LOG]!
***********************************
![LOG[Expand a string: WinPEandFullOS]LOG]!><time="12:42:40.185-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="executionenv.cxx:782">
<![LOG[Executing command line: smsswd.exe /run:M010010D cmd /c runscanstate-offlinewindir.bat %OSDStateStorePath% %systemdrive%]LOG]!><time="12:42:40.185-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="commandline.cpp:827">
<![LOG[[ smsswd.exe ]]LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="main.cpp:289">
<![LOG[PackageID = 'M010010D']LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="main.cpp:318">
<![LOG[baseVar = '', ContinueOnError='']LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="main.cpp:319">
<![LOG[ProgramName = 'cmd /c runscanstate-offlinewindir.bat c:\USMToffline c:']LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="main.cpp:320">
<![LOG[swdAction = '0001']LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="main.cpp:321">
<![LOG[ResolveSource flags: 0x00000000]LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="resolvesource.cpp:3265">
<![LOG[sMSTSPersistContent: . The content for package M010010D will be persisted]LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="resolvesource.cpp:3274">
<![LOG[The package M010010D is found locally in the cache E:\_SMSTaskSequence\Packages\M010010D]LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="resolvesource.cpp:3301">
<![LOG[Resolved source to 'E:\_SMSTaskSequence\Packages\M010010D']LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:449">
<![LOG[set command line: Run command line]LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="0" thread="1192" file="commandline.cpp:731">
<![LOG[Working dir 'c:\USMTbits\']LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:542">
<![LOG[Executing command line: Run command line]LOG]!><time="12:42:40.216-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="commandline.cpp:827">
<![LOG[]LOG]!><time="12:42:40.466-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[c:\USMTbits>"c:\USMTbits\x86\scanstate.exe" "c:\USMToffline" /c /o /hardlink /efs:hardlink /nocompress /offlinewindir:c:\windows /v:5 /l:c:\windows\TEMP\SMSTSLog\scanstate.log /progress:c:\windows\TEMP\SMSTSLog\scanstateprogress.log /i:c:\USMTbits\x86\miguser.xml /i:c:\USMTbits\x86\migapp.xml ]LOG]!><time="12:42:40.466-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[]LOG]!><time="12:42:40.466-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[Process completed with exit code 26]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="commandline.cpp:1123">
<![LOG[]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[canState return code: 26]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:34">
<![LOG[Command line returned 26]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="runcommandline.cpp:565">
<![LOG[Entering ReleaseSource() for E:\_SMSTaskSequence\Packages\M010010D]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="resolvesource.cpp:3616">
<![LOG[reference count 1 for the source E:\_SMSTaskSequence\Packages\M010010D before releasing]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="resolvesource.cpp:3623">
<![LOG[Released the resolved source E:\_SMSTaskSequence\Packages\M010010D]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="InstallSoftware" context="" type="1" thread="1192" file="resolvesource.cpp:3656">
<![LOG[Process completed with exit code 26]LOG]!><time="12:42:40.513-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="12:42:40.529-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="instruction.cxx:3012">
<![LOG[Failed to run the action: do X86 Scanstate.
The specified disk or diskette cannot be accessed. (Error: 0000001A; Source: Windows)]LOG]!><time="12:42:40.529-240" date="06-08-2014" component="TSManager" context="" type="3" thread="1924" file="instruction.cxx:3103">
<![LOG[MP server http://primsccmsrv.newtonXXX.corp.network. Ports 80,443. CRL=false.]LOG]!><time="12:42:40.529-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="utils.cpp:5300">
<![LOG[setting authenticator]LOG]!><time="12:42:40.560-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="utils.cpp:5322">
<![LOG[set authenticator in transport]LOG]!><time="12:42:40.576-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:7751">
<![LOG[sending StatusMessage]LOG]!><time="12:42:40.591-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="libsmsmessaging.cpp:4025">
<![LOG[setting message signatures.]LOG]!><time="12:42:40.607-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:1297">
<![LOG[setting the authenticator.]LOG]!><time="12:42:40.607-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: primsccmsrv.newtonXXX.corp.network:80 CCM_POST /ccm_system/request]LOG]!><time="12:42:40.607-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="12:42:40.951-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:8956">
<![LOG[set a global environment variable _SMSTSLastActionRetCode=26]LOG]!><time="12:42:40.951-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="executionenv.cxx:668">
<![LOG[set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="12:42:40.951-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="12:42:40.951-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="executionenv.cxx:807">
<![LOG[Let the parent group (Run) decides whether to continue execution]LOG]!><time="12:42:40.998-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="instruction.cxx:3212">
<![LOG[Let the parent group (XCopy) decide whether to continue execution]LOG]!><time="12:42:40.998-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="instruction.cxx:2462">
<![LOG[Let the parent group (Offline Scanstate in WinPE) decide whether to continue execution]LOG]!><time="12:42:40.998-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="instruction.cxx:2462">
<![LOG[The execution of the group (Offline Scanstate in WinPE) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="12:42:40.998-240" date="06-08-2014" component="TSManager" context="" type="3" thread="1924" file="instruction.cxx:2425">
<![LOG[Failed to run the last action: do X86 Scanstate. Execution of task sequence failed.
The specified disk or diskette cannot be accessed. (Error: 0000001A; Source: Windows)]LOG]!><time="12:42:40.998-240" date="06-08-2014" component="TSManager" context="" type="3" thread="1924" file="engine.cxx:214">
<![LOG[MP server http://primsccmsrv.newtonXXX.corp.network. Ports 80,443. CRL=false.]LOG]!><time="12:42:41.013-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="utils.cpp:5300">
<![LOG[setting authenticator]LOG]!><time="12:42:41.044-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="utils.cpp:5322">
<![LOG[set authenticator in transport]LOG]!><time="12:42:41.044-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:7751">
<![LOG[sending StatusMessage]LOG]!><time="12:42:41.076-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="libsmsmessaging.cpp:4025">
<![LOG[setting message signatures.]LOG]!><time="12:42:41.091-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:1297">
<![LOG[setting the authenticator.]LOG]!><time="12:42:41.091-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: primsccmsrv.newtonXXX.corp.network:80 CCM_POST /ccm_system/request]LOG]!><time="12:42:41.091-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="12:42:41.326-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="libsmsmessaging.cpp:8956">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="12:45:40.098-240" date="06-08-2014" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="12:45:40.098-240" date="06-08-2014" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:939">
<![LOG[successfully launched command shell.]LOG]!><time="12:45:40.098-240" date="06-08-2014" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
<![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,866)]LOG]!><time="12:57:41.799-240" date="06-08-2014" component="TSManager" context="" type="0" thread="1924" file="tsmanager.cpp:866">
<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="12:57:41.799-240" date="06-08-2014" component="TSManager" context="" type="3" thread="1924" file="tsmanager.cpp:866">
<![LOG[****************************************************************************]LOG]!><time="12:57:41.799-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="tsmanager.cpp:889">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="12:57:41.799-240" date="06-08-2014" component="TSManager" context="" type="3" thread="1924" file="tsmanager.cpp:890">
<![LOG[Cleaning Up.]LOG]!><time="12:57:41.799-240" date="06-08-2014" component="TSManager" context="" type="1" thread="1924" file="tsmanager.cpp:637">
***********************
*****************************************************************************
scanstate log:-
2014-06-08 12:42:40, Info [0x000000] Command line: c:\USMTbits\x86\scanstate.exe c:\USMToffline /c /o /hardlink /efs:hardlink /nocompress /offlinewindir:c:\windows /v:5 /l:c:\windows\TEMP\SMSTSLog\scanstate.log /progress:c:\windows\TEMP\SMSTSLog\scanstateprogress.log /i:c:\USMTbits\x86\miguser.xml /i:c:\USMTbits\x86\migapp.xml
2014-06-08 12:42:40, Status [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING'
2014-06-08 12:42:40, Error [0x000000] Invalid Windows folder for offline gather to start - c:\windows[gle=0x00000003]
2014-06-08 12:42:40, Error [0x000000] Invalid Windows folder for offline gather to start - c:\windows[gle=0x00000003]
2014-06-08 12:42:40, Info [0x000000] Failed.[gle=0x00000006]
2014-06-08 12:42:40, Info [0x000000] Unable to find a valid Windows directory to proceed with requested offline operation;
Check if offline input file is present and has valid entries[gle=0x00000006]
2014-06-08 12:42:40, Info [0x000000] USMT Completed at 2014/06/08:12:42:40.357[gle=0x00000006]
2014-06-08 12:42:40, Info [0x000000] Entering MigShutdown method
2014-06-08 12:42:40, Info [0x000000] Leaving MigShutdown method

Share this post


Link to post
Share on other sites

  • 0

 

interesting i havn't seen this behaviour, right now i'm using the bitlocker frontend HTA (which incorporates this functionality), and i've not noticed any padlocks, can you show me a screenshot and are you using Configuration Manager 2012 or 2007 for this ?

Sorry I haven't got back, I actually sorted this shortly after. I was applying group policy and restarting straight after. I removed these steps and it sorted the issue. I've just incorporated your wnb.xml and it works a treat. Thanks again!

 

Just have some trying to smooth out some teething issues, had lots of problems with the PXE loosing it's boot files from the RemoteInstall \smsboot and some oddity where it can't create the folders on the C: drive when creating the USMT stores prompting incorrect function (Failed to run the action: Create USMT folder to store USMT packages. Incorrect function. (Error: 00000001; Source: Windows)) even creating the folders manually and I'm getting errors when trying to run the manually copied scanstate.bat (Failed to run the last action: Run x86 scanstate. Execution of task sequence failed. The specified disk or diskette cannot be accessed. (Error: 0000001A; Source: Windows)). I'm getting there and I can't thank you enough for your guides!

Share this post


Link to post
Share on other sites

  • 0

Hi guys. We have an Offline refresh USMT TS and our Restore User State step fails. TS is set to Access content from DP. NTFS/Share permissions are ok. I have deleted previous store folders before running the TS again. The Restore User State Step in the Task Sequence is set to use default unmodified MigUser.xml. Any ideas will be much appreciated!

 

smsts.log:

 

Executing command line: "\\DISTRIBUTIONPOINT\PACKAGE\x86\loadstate.exe" "C:\USMToffline" /c /v:5 /l:"C:\Windows\system32\CCM\Logs\SMSTSLog\loadstate.log" /progress:"C:\Windows\system32\CCM\Logs\SMSTSLog\loadstateprogress.log" /i:"\\DISTRIBUTIONPOINT\PACKAGE\x86\MigUser.xml" /hardlink /nocompress OSDUSMT 07/08/2014 05:02:05 p.m. 424 (0x01A8)
Process completed with exit code 27 OSDUSMT 07/08/2014 05:02:05 p.m. 424 (0x01A8)
USMT completed with exit code 27 OSDUSMT 07/08/2014 05:02:05 p.m. 424 (0x01A8)
uExitCode == 0, HRESULT=8007001b (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\main.cpp,384) OSDUSMT 07/08/2014 05:02:06 p.m. 424 (0x01A8)
USMT returned exit code (0x0000001b). Look USMT log file loadstate.log for detail error message. OSDUSMT 07/08/2014 05:02:06 p.m. 424 (0x01A8)

OSDMigrateUserState finished: 0x8007001b OSDUSMT 07/08/2014 05:02:06 p.m. 424 (0x01A8)
Process completed with exit code 2147942427 TSManager 07/08/2014 05:02:06 p.m. 1852 (0x073C)
!--------------------------------------------------------------------------------------------! TSManager 07/08/2014 05:02:06 p.m. 1852 (0x073C)
Failed to run the action: Restore User State.
The drive cannot find the sector requested. (Error: 8007001B; Source: Windows) TSManager 07/08/2014 05:02:06 p.m. 1852 (0x073C)

loadstate.log

 

2014-08-06 17:34:37, Info [0x000000] USMT Started at 2014/08/06:17:34:37.690
2014-08-06 17:34:37, Info [0x000000] Command line: \\DISTRIBUTIONPOINT\XXXXXXX\x86\loadstate.exe C:\USMToffline /c /v:5 /l:C:\Windows\system32\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\Windows\system32\CCM\Logs\SMSTSLog\loadstateprogress.log /nocompress /hardlink
ï2014-08-06 17:34:37, Status [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING'
2014-08-06 17:34:37, Info [0x000000] Failed.[gle=0x00000006]
2014-08-06 17:34:37, Info [0x000000] An error occurred processing the command line.
Invalid store path; check the store parameter and/or file system permissions[gle=0x00000006]

2014-08-06 17:34:37, Info [0x000000] USMT Completed at 2014/08/06:17:34:37.690[gle=0x00000006]
2014-08-06 17:34:37, Info [0x000000] Entering MigShutdown method
2014-08-06 17:34:37, Info [0x000000] Leaving MigShutdown method

Share this post


Link to post
Share on other sites

  • 0
Invalid store path; check the store parameter and/or file system permissions

did you check that ?

 

here's my loadstate command which i completed yesterday successfully for you to compare with

 

 

Untitled.png

 

and C:\USMTOffline does indeed exist

 

usmtoffline.png

Share this post


Link to post
Share on other sites

  • 0
Invalid store path; check the store parameter and/or file system permissions

did you check that ?

 

here's my loadstate command which i completed yesterday successfully for you to compare with

 

 

 

 

 

Thanks sir. I have been able to get it sorted out. I was copying amd64 folder instead of x86, hence the error. If I may, let me ask you another question: I only want to to migrate my domain user profile and its files/folder (C:\users\MYDOMAINUSER\) and not local users.. Nothing fancy, no file exclusions, only my domain user folder.

Logs show that everything works, however, my user profile is not being copied. My loadstate.log shows that my command line is the following:

 

 

\\DISTRIBUTIONPOINT\USMTPACKAGE\x86\loadstate.exe C:\users\public\USMToffline /v:5 /l:C:\Windows\system32\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\Windows\system32\CCM\Logs\SMSTSLog\loadstateprogress.log /i:\\\DISTRIBUTIONPOINT\USMTPACKAGE\x86\MigUser.xml /hardlink /nocompress /ue:*

 

In my TS, the Restore User State step is set to Customize how user profiles are restored, and MigUser.xml is selected (I do not know if this is redundant or not).MigUser.xml is unmodified.

 

Thanks!!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.