Jump to content


Ironman

USMT and State Migration

Recommended Posts

am having trouble using USMT and SMP.... Attached are screenshot of my settings, however every step in TS runs through as if domain user profiles are captured, but when checking SMP, nothing appears....

 

What needs to be done in order for TS to trigger that there are Domain user profiles to copy...

Also according to documents, that the Step " capture all user profiles " runs the scanstate.exe.

 

Anyone who can help me get this working.

Doc1.doc

Share this post


Link to post
Share on other sites


Well, your task sequence looks good to me. Can you provide us with the smsts.log file? Have you configured the network service account?

 

In the scanstate steps, are you specifying which config xml files to use? And lastly, if you're looking to copy only domain profiles, you'll need to add an additional task sequence variable with applicable scanstate syntax; that being said, I've not had much luck with SCCM's built in USMT task sequence steps.

Share this post


Link to post
Share on other sites

Hi,

 

I keep receiving the below eroors in my scanstate.log. I have changed my USMT to point to \USMT as well as USMT\X86 folders but to no avail. What is preventing copying from going through to SMP.

 

2011-09-22 15:59:51, Info [0x000000] USMT Started at 2011/09/22:15:59:51.104

2011-09-22 15:59:51, Info [0x000000] Command line: C:\_SMSTaskSequence\Packages\A01000E6\x86\scanstate.exe \\nadon.mercantrade.com\SMPSTOREX_F06EC7AA$\0E47F3FB81579566B9E0B7FF456B02D3B445E4A081D96CC70185D33BEA243119 /o /localonly /encrypt /key:**** /c /efs:skip /v:5 /l:C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstateprogress.log /i:C:\_SMSTaskSequence\Packages\A01000E6\x86\MigUser.xml /i:C:\_SMSTaskSequence\Packages\A01000E6\x86\MigApp.xml /i:C:\_SMSTaskSequence\Packages\A01000E6\x86\MigDocs.xml /i:C:\_SMSTaskSequence\Packages\A01000E6\x86\MigSys.xml

2011-09-22 15:59:51, Status [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING'

2011-09-22 15:59:51, Error [0x000000] Script file is not present: 'C:\_SMSTaskSequence\Packages\A01000E6\x86\MigSys.xml'[gle=0x00000006]

2011-09-22 15:59:51, Info [0x000000] Failed.[gle=0x00000006]

2011-09-22 15:59:51, Info [0x000000] An error occurred processing the command line.

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

2011-09-22 15:59:51, Info [0x000000] USMT Completed at 2011/09/22:15:59:51.135[gle=0x00000006]

2011-09-22 15:59:51, Info [0x000000] Entering MigShutdown method

2011-09-22 15:59:51, Info [0x000000] Leaving MigShutdown method

Share this post


Link to post
Share on other sites

It's looking for the "MigSys.xml" config file that is not copied to the DP.

 

Check your scanstate command-line syntax in the "Capture User State" step of the TS - if the "MigSys.xml" file isn't referenced in the command line, then check the SCCM GUI reference to the scanstate/loadstate config files (see below). Make sure that in "Capture User Files and Settings" and in "Restore User Files and Settings" that your config files match in each step. I had a similar issue where I mis-typed "MigApp.xml" as "MigCpp.xml," and it was bombing the loadstate each time.

post-11371-0-96233900-1316704165_thumb.jpg

post-11371-0-17704000-1316704173_thumb.jpg

Share this post


Link to post
Share on other sites

Apparently MigSys.xml is a config file that is only relevant to USMT 3.0 and earlier... you do not need it with 4.0. Remove it from your scanstate/loadstate command line..

Share this post


Link to post
Share on other sites

Bronx Bull is correct..

 

In your task sequence steps for capture and restore you should have either:

 

MigApp.xml & MigUser.xml OR MigApp.xml & MigDocs.xml (You cant use User & Docs together).

 

Additional xml files, such as printers or wallpaper can also be added. You can't add a Config.xml file in my experience though, as it needs a seperate command /config:<filename.xml> rather than /i:<filename.xml> so if you want to use a Config.xml as well it needs to be added to the task sequence variable

OSDMigrateAdditionalCaptureOptions in a seperate step.

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
Reply to this topic...

×   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...