Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
Have a problem with Capture User State, XP->Win7 using MDT 2012

Answered Have a problem with Capture User State, XP->Win7 using MDT 2012

  • Mittwoch, 23. Mai 2012 13:17
     
     
    Anmelden
    0

    Setup:  MDT 2012 is installed on a Win7 Pro desktop.  I normally create and deploy (via LTI) base images (OS and apps that are common throughout the company) that the other techs then configure for the individual user.  Migration of user files and settings is done via Windows Easy Transfer (WET).  I have no problems running the Standard Client T.S. to create and then deploy images.  My Share names are:

    \\<host name>\MDT2012-FirstDS$  Deployment Share
    \\<host name>\Logs   For copies of the deployment logs (I don't remember why I didn't use a '$' in the share name)
    \\<host name>\UserMig  For user files and settings via USMT ( - ditto above - )
    \\<host name>\PC-Backup  For backing up the computer I'm replacing ( - ditto above - )

    Situation:  I had extra time yesterday, so I thought I'd try the Replace Task Sequence to migrate the user's info.  She had an old Dell running XP with Adobe Creative Suite 5 as the primary app suite.  However, the T.S. failed almost immediately when  cscript.exe "%SCRIPTROOT%\ZTIUserState.wsf" /capture began running.  I searched for the errors but had no luck (maybe I used the wrong search terms).

    Here is my Bootstrap.ini:
    [Settings]
    Priority=Default

    [Default]
    DeployRoot=\\<hostname>\MDT2012-FirstDS$

    Here's the CustomSettings.ini:
    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
      OSInstall=Y
      _SMSTSOrgName=PC-Network Support
      SLShare=\\<hostname>\Logs
      EventService=http://<hostname>:9800
      WSUSServer=http://<FQDN of WSUS Server>

      SkipCapture=NO
      
      SkipBitLocker=YES
      PrepareWinRE=NO

      SkipProductKey=YES

      SkipComputerBackup=YES
      BackupDir=%COMPUTERNAME%
      BackupShare=\\<hostname>\PC-Backup
      ComputerBackupLocation=NETWORK
     
      ScanStateArgs=/v:5 /o /c /uel:90 /ui:<domain>\*
      LoadStateArgs=/v:5 /c /lac /uel:90 /ui:<domain>\*

      SkipUserData=YES
      UDDir=%COMPUTERNAME%
      UDShare=\\<hostname>\UserMig
      UserDataLocation=NETWORK

      SkipFinalSummary=NO

    Here are the snips of errors from SMSTS.log:

    Executing command line: cscript.exe "%SCRIPTROOT%\ZTIUserState.wsf" /capture
    Process completed with exit code 5456
    !-----------------------------------------------------------------!
    Failed to run the action: Captuire User State. Unknown error (Error: 00001550; Source: Unknown)
    Sending a status message .....
    Executing in non SMS standalone mode. Ignoring send a task execution message request
    Set a global environment variable _SMSTSLastActionRetCode=5456
    Set a global environment variable _SMSTSLastActionSucceeded=false
    Clear local default environment
    Let the parent group (State Capture) decides whether to continue execution
    The execution of the group (State Capture) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Capture User State. Execution of task sequence failed. Unknown error (Error: 00001550, Source: Unknown)
    Sending a status message ...
    Cleaning up task sequence folder
    Delete file W(sVolumeIDFile.c_str(), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp.508)
    Successfully unregistered Task Sequencing Environment COM Interface
    Command line for extension .exe is "%1" %*
    Set command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister
    etc.

    Here's a snip from the end of the BDD.log:

    Unable to yield a target Partition (Special Recovery option for Litetouch)
    DestinationDisk and Partition did not yield a target Partition.
    FAILURE (5456): Unable to determine Destination Disk, Partition, and/or Drive.  See BDD.LOG for more information.
    Event 41002 sent: FAILURE (5456): Unable to determine Destination Disk, Partition, and/or Drive.  See BDD.LOG for more information.
    Command completed, return code = -2147467259
    Litetouch deployment failed, Return Code = -2147467259 0x80004005
    Event 41014 sent: Litouch deployment failed, Return Code = -2147467259 0x80004005
    etc.

    My question is:  What was it I did wrong?


    Mike

    south-central Nebraska

     

Alle Antworten

  • Mittwoch, 23. Mai 2012 13:50
     
     
    Anmelden
    1

    Couple of things.

    1. The subject of this thread says - XP to Windows 7 using MDT 2010? Are you trying to do a Hardlink Migration from XP to Windows 7 and retain the old machine? I ask this because it is not clear to me. Are you planning to use OLD hardware or copy the data to the network and install Windows 7 on a new hardware and then restore data.

    2. The other strange thing is the logs. One section of the log pasted is "Failed to run the action: Captuire User State. "
    I see the typo on the word Capture (Captuire). Assuming something happened while pasting the logs.

    3. Do you see the USMTCapture.log in the logs folder?

    4. I see that you specified ComputerBackupLocation property in CustomSettings.ini. I am sure you are aware that this would create wim file for that computer? Are you really trying to accomplish this? The ComputerBackupLocation property is different to UserDataLocation.

    5. Lastly, if this is the first time you are experimenting with automating the UserDataCapture etc, then you would want to start testing this with minimum and only required properties in CS.ini. This will help you save time.


    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Mittwoch, 23. Mai 2012 14:25
     
     
    Anmelden
    0

    Thanks for the questions.  I'm still new to MDT - I started using MDT Update 1 last fall and learned how to use it by reading posts on this forum, and the accompanying documentation.  In answer to your questions ....

    (1) I am trying to copy the user's files and settings from an old computer to deploy to a new one.  My intent is to have the T.S. place her data in the "UserMig" share and then have another T.S. move it to the new computer.

    (2)  It's a typo; I had to type it all out as I couldn't figure a way to copy multiple lines when the log files are open in Trace32.exe.

    (3) The only logs are: DDD.LOG, NetSetup.LOG, smsts.log, and wpeinit.log.

    (4) I wasn't sure about ComputerbackupLocation either, but I found this in the Using the Microsoft Deployment Toolkit document (page 61):

    Table 18. Information for Completing the Deployment Wizard for the Replace Computer Deployment Scenario for Saving User State Migration Data Using LTI

      

    On this wizard page

           		  

    Do this

      

    Select a task sequence to execute on this   computer

    Select the task sequence you created for the target   computer in the Replace Computer deployment scenario to save the user state   migration data.

    Specify where to save your data and   settings.

    In the Location box, type the fully   qualified path to the location in which you want to store the user state   migration data. This location must be accessible to the new target computer.

    Specify where to save a complete computer   backup

    Click Specify a location, and then type   the fully qualified path to the location in which you want to store the   backup.

    Note   This   backup is for use in restoring user state migration data that might have been   missed, not as a rollback method for the target computer. If you want to have   rollback capability for the target computer, perform a full backup using your   organization’s backup software.

    See where I highlighted?  It implies (I thought) that you SHOULD do this when capturing and then deploying user data.

    (5)  Good point, and I'd considered it.  But I get so few chances to work with a "live" machine with real user data that I thought I'd give it a try.  When this failed yesterday, I immediately downloaded and used WET to move the users over to the new machine and get them back on-line.  My intent was to learn from the process even if it failed.  Unfortunately, the errors weren't straightforeward for a new guy like me, and I had to ask my question(s) in this forum.

    Thanks in advance to all for your inout and comments.  I intend to learn from tbhis episode.


    Mike

    south-central Nebraska

     
  • Mittwoch, 30. Mai 2012 18:54
     
     
    Anmelden
    0

    I tried again with a stripped-down CS.ini, but had the same error:

    FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information. ZTIUserState 5/30/2012 1:39:41 PM 0 (0x0000)

    Here's the CS.ini:

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
      OSInstall=Y
      SLShare=\\<host name>\Logs$
      EventService=http://<host name>:9800

      SkipAdminPassword=YES
     
      SkipCapture=NO
      SkipProductKey=YES

      UDShare=\\<host name>\usermig$
      UDDir=%COMPUTERNAME%
      UserDataLocation=NETWORK

      ScanStateArgs=/v:5 /o /c /uel:90 /ui:<domain>\*
      LoadStateArgs=/v:5 /c /lac /uel:90 /ui:M<domain>\*

    I'm using the Standard Client Replace Task Sequence.  I created it following the Samples Guide as my 'guide' for this test (Replacing an Existing Computer with a New Computer Using Lite Touch Installation, starting on page 91).  I didn't touch the TS after I created it.

    What did I do wrong?


    Mike

    south-central Nebraska

     
  • Donnerstag, 31. Mai 2012 15:22
     
     
    Anmelden
    0

    Just in case it's a Permissions problem, here's what I've got for the DS$ and for the UserMig$ shares on my Win7 Pro SP1 machine that hosts MDT 2012:

    DS$ - Share button -> Administrators (Owner), Domain Users and myself (Read/Write)
    DS$ - Advanced Sharing button -> Everyone (Full Control)

    UserMig$ - Share button -> myself (Owner), Domain Admins & <group I belong to> (Read/Write)
    UserMig$ - Advanced Sharing button -> Everyone (Read), Authenticated Users and <group I belong to> (Full Control)


    Mike

    south-central Nebraska

     
  • Freitag, 1. Juni 2012 14:05
     
     
    Anmelden
    0

    I created a new T.S. - using Client Standard Replace template - with minimal CS.ini entries.  Still got the same error.  Maybe it'd help with a few images:

    Here's my DS Boot folder:

    Here's a snip of the Boot.ini:
    [Settings]
    Priority=Default

    [Default]
    DeployRoot=\\<hostname>\MDT2012-FirstDS$

    And a snip of the CS.ini:
    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
      OSInstall=Y
      SLShare=\\<hostname>\Logs$
      EventService=http://<hostname>:9800

      SkipAdminPassword=YES
     
      SkipCapture=NO
      SkipProductKey=YES
      SkipAppsOnUpgrade=YES

      UDShare=\\<hostname>\UserMig$
      UDDir=%COMPUTERNAME%
      UserDataLocation=NETWORK

      ScanStateArgs=/v:5 /o /c
      LoadStateArgs=/v:5 /c /lac

    And here's the TS (I did NOT change it in any way:

    So ... any ideas out there?


    Mike

    south-central Nebraska

     
  • Freitag, 1. Juni 2012 15:49
     
     
    Anmelden
    0

    I found a post awhile back on testing of the CustomSettings.ini file, so I ran the following from a command prompt:

    "cscript.exe <deploy_root>\Scripts\ZTIGather.wsf /rulesfile:<path>\myCustomSettings.ini"

    Came up clean - no errors.


    Mike

    south-central Nebraska

     
  • Freitag, 1. Juni 2012 17:41
     
     
    Anmelden
    0

    Here's a couple other things I tried since my last post.

    I created a new DS and new UserMig shared folder.  Followed the documentation to the letter.  Copied over Win7 Pro x86, WinPE x86 drivers, and created the Replace TS.  CS.ini was just like in the doc.  Boot.ini wasn't touched.

    It crashed with the same errors.

    For the heck of it, I tried this from a newly configured laptop that hadn't been issued yet to a user. 

    It, too, crashed with the same errors.

    What am I missing????


    Mike

    south-central Nebraska

     
  • Freitag, 1. Juni 2012 19:02
     
     
    Anmelden
    0

    One more item that might be a clue in this mystery.

    My MDT 2012 host, as I've mentioned, is running Windows 7 Pro w/SP1 (x86).  The internal hard-drive (250GB) is configured:

    • OEM Partition
    • RECOVERY Volume (System, Active, Primary Partition)
    • OS Volume (C:) (Boot, Page File, Crash Dump, Primary Partition)

    I also have an external hard-drive (250GB) connected by USB 2.0 for backups and VM's to create my images.


    Mike

    south-central Nebraska

     
  • Montag, 4. Juni 2012 17:49
     
     
    Anmelden
    0

    Another failure, but possibly valuable information obtained.

    ==================================
    I decided to start with a clean slate; I imaged a new Win7 Pro on bare-metal, joined it to the domain, updated it via WSUS and then downloaded/installed WAIK 2.0 and MDT 2012.  Using the documentation, I created a DS, two TS's (one to capture the user data and one to deploy the image and user data), added WinPE 3.0 and make/model drivers, copied over an image I've deployed many times, then tried it on a WinXP box with live user data. 

    For unknown reasons, the TS asked for a destination for the user data.  I thought that if I had this in CS.ini that it wouldn't prompt me:

    SkipUserData=YES
    UDShare=\\<hostname of Win7 PC>\UserMig
    UDDir=%COMPUTERNAME%
    UDLocation=NETWORK

    I entered the same info on the UDShare line.  The next screen asked whether I wanted to do a computer backup; I chose 'no'. Clicked OK a couple times and then it ran less than 30 seconds and bombed on the UserState /Capture step - can't determine the destination disk or partition.

    I'll check the copied over image's Unattend.xml file, but I think I'm missing something - and the MDT documentation is too, as I'm trying to follow it to the letter. 


    Mike

    south-central Nebraska

     
  • Montag, 4. Juni 2012 18:42
     
     
    Anmelden
    0

    Boy this is frustrating! As a follow-on to the last post, I used a Win7 install disk as my install image and left al else the same - just in case the image I copied over had some glitch in it.

    This, too, bombed in the same place with the same error.  I've tried Bing and Google to find comparable errors but no luck so far.  Really hoping someone on this forum has some ideas.


    Mike

    south-central Nebraska

     
  • Montag, 4. Juni 2012 20:04
     
     
    Anmelden
    0

    Did not go through the complete post after replying the first thread, however after a quick look - Seems like you have the wrong Property for USMT Data Location.

    SkipUserData=YES
    UDShare=\\<hostname of Win7 PC>\UserMig
    UDDir=%COMPUTERNAME%
    UDLocation=NETWORK

    Firstly, are you really typing <hostname of Win7 PC> for UDShare in CS.ini? If yes, then that would not work. It should be a network share name like Deploy$\UserMig.

    Second - UDLocation is not a known property (atleast if it is new in 2012). It should be UserDataLocation=NETWORK. See example below.

    UserDataLocation=NETWORK
    UDShare=\\NYC-AM-FIL-01\MigData$
    UDDir=%OSDComputerName%

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Montag, 4. Juni 2012 20:13
     
     
    Anmelden
    0

    To answer your questions...

    <hostname of Win7 PC> is just a placeholder for the real name.

    UDLocation was typed wrong; I was in a hurry to get somewhere.  I meant UserDataLocation.

    Is %OSDCOMPUTERNAME% used regardless of whether I use LTI or ZTI (SCCM)?


    Mike

    south-central Nebraska

     
  • Montag, 4. Juni 2012 20:25
     
     
    Anmelden
    0

    For MDT 2012 it should be UDDir=%ComputerName% (exactly typed) - Most of MDT's properties and values are Case Sensitive.

    In MDT 2010 %OSDComputerName% worked. If you integrate SCCM and MDT - then %ComputerName% should work <--- Guess!! But Need to confirm...

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Montag, 4. Juni 2012 20:43
     
     
    Anmelden
    0

    Ok.  I used:

    UDDir=%COMPUTERNAME%

    Should I NOT have capitalized all the letters?


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 05:03
     
     
    Anmelden
    0
    Not sure about that, however I know that UDDir=%ComputerName% surely works.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 12:16
     
     
    Anmelden
    0

    I may have stumbled on the cause of my problems ...... according a blog post titled "Understanding USMT with MDT 2010" at XtremeConsulting, I should have a folder in the root of my DS named "USMT":

             "When you create your Deployment Share inside of the Deployment Workbench, MDT will
                  create a folder at the root of the deployment share called USMT and copy the USMT files
              into that folder."

    I don't have that folder in this, or in other DS's I've created.  I just tried a 'Repair' of WAIK within the Deployment Workbench to see if it'd create that folder - it did not.

    So .... have I found the problem? And if so, what was the cause and how do I fix it?


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 12:21
     
     
    Anmelden
    0

    For MDT 2012 - MDT creates it under DS\Tools\<architecture>\USMT4. You dont have to do this manually ... etc..

    Mike - I know you have been visiting this thread again with fixes and issues. I would appreciate if you just brief about the current issue which you are facing and someone or myself in this forum will reply.

    This is because there are 2-3 issues in this thread.


    • Bearbeitet Vik Singh Dienstag, 5. Juni 2012 12:34
    • Bearbeitet Vik Singh Dienstag, 5. Juni 2012 12:34
    •  
     
  • Dienstag, 5. Juni 2012 12:48
     
     
    Anmelden
    0

    Vik Singh - Will do.  (I verified that USMT4 folder exists where you said it should be.)

    ================================

    Problem: Unable to capture User Data using Standard Client Replace Task Sequence in MDT 2012.

    'Server':  Dell OptiPlex 580, 250GB hard-drive and 4 GB RAM.  Windows 7 Professional (x86) w/SP1 OS.

    Error:  (from BDD.LOG)   FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information. ZTIUserState 6/1/2012 8:47:57 AM 0 (0x0000).


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 13:10
     
     
    Anmelden
    0

    Could you please upload the CS.ini, ZTIUserState.log, BDD.log and USMTCapture.log (if you find it on that folder) on a public storage website or email it to vikramjs@live.com

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 13:39
     
     
    Anmelden
    0
    They have been sent to your email.


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 13:45
     
     
    Anmelden
    0

    Nothing much in the logs - same as you pasted earlier.

    ok, lets start from scratch :)

    Have you tried this only on 1 machine? Or you see this on multiple machines?

    Next - Can you send the screenshot of Disk Management on this PC?

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 13:54
     
     
    Anmelden
    0

    (1)  I have tried this on 2 different desktops (same make different models), and a laptop.  One of the desktops and the laptop run Win7, the other desktop runs WinXP.

    (2)  This is a anpshot of Disk Management on my MDT 2012 host:


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 13:57
     
     
    Anmelden
    0

    Sorry to be unclear. Do not need the snapshot of the MDT Host - want to see the diskpart from the Client where the capture is initiated.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 14:03
     
     
    Anmelden
    0

    Here it is:


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 14:17
     
     
    Anmelden
    0

    AFAIK - The EISA Partition by the OEM Vendor is the issue.

    You can try to get rid of that and then do the capture - Steps mentioned here - http://everythingsysadmin.wordpress.com/2011/03/14/mdt-refresh-task-sequence-failures/

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 14:51
     
     
    Anmelden
    0

    OK, I deleted the partition (40 MB in size and listed as Partition 1), updated the deployment share and tried again - exact same error.

    It's been a LOT of years so maybe the EISA partition is the one the OEM put on and is listed as RECOVERY.  Here's a screenshot:

    Should I delete the RECOVERY partition?


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 15:02
     
     
    Anmelden
    0

    I think you got it wrong. The screen shot for 40 MB is the WIndows 7 MDT 2012 machine I think.

    You have the delete the partition of 71 MB FAT (EISA) on the client.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 15:28
     
     
    Anmelden
    0
    OK, my mistake.  I deleted the EISA partition on the client WinXP PC, rebooted to my UFD, started the T.S., and ... it 'bombed' again at the same point with the same error.


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 16:10
     
     
    Anmelden
    0
    Delete the Minint folder on the CLIENT machine and reboot and launch the Task Sequence again.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Dienstag, 5. Juni 2012 16:42
     
     
    Anmelden
    0

    I was unable to boot into the Client (an old WinXP PC with a bad HDD - the reason I repalced it a month ago; I was hoping it would 'stay alive long' enough to test with).  So I used one of my two tech PC's - the one with WinXP.  I ensured that the MINIT folder was not present, and I used DISKPART to delete the EISA partition.  I then went to Start -> Run and navigated to the DS and ran LiteTouch.vbs.  It is working now at capturing the User Data on it.  I'll ensure it runs with no errors to the end, but it appears that there are two keys:

    (1) The Client HDD has to be in working order.

    (2) There can't be an OEM - EISA partition.


    Mike

    south-central Nebraska

     
  • Dienstag, 5. Juni 2012 16:59
     
     
    Anmelden
    0
    Finished with no errors!


    Mike

    south-central Nebraska

    • Als Antwort vorgeschlagen findingsanity Montag, 12. November 2012 06:31
    • Nicht als Antwort vorgeschlagen findingsanity Montag, 12. November 2012 06:31
    •  
     
  • Dienstag, 5. Juni 2012 16:59
     
     Beantwortet
    Anmelden
    1

    Yeah, bad hrd drive nothing will work.

    Eisa partition does not do well with MDT

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

    • Als Antwort markiert RV2011 Dienstag, 5. Juni 2012 17:25
    •  
     
  • Dienstag, 5. Juni 2012 17:26
     
     
    Anmelden
    0
    Thanks for the help and sticking with me!


    Mike

    south-central Nebraska

     
  • Freitag, 13. Juli 2012 14:54
     
     
    Anmelden
    0

    See this post, http://www.thedecoderwheel.com/?p=1498

    I know for sure I did not make this change to my task sequence... and the issue was not occurring on MDT2010 - only 2012.  All of my other task sequences were accurate and worked fine.

    Joe