none
MDT 2012 USMT - How to copy data from additional partition and merge the partitions

    Question

  • Hello,

    I am working on migrating few hundred machines from Windows XP to Windows 7. We are using MDT 2012 for this task.

    All our Windows XP machines have an extra partition (D: Drive) that has some user data on it. We intend to have only a single partition on all the Windows 7 machines.

    I am trying to copy all the data from D drive to a folder on C: drive called Old_D_Drive. After this I intend to recreate the partition using task sequence so that there is only a single partition (C: drive).

    How can I accomplish this?

    Thanks in advance,


    SinghP80

    Tuesday, October 15, 2013 6:36 PM

Answers

All replies

  • What I would do, but I'm not an USMT expert is specify which folders should be backed-up by USMT, (this can be done by modifying the USMT xml files in your USMT folder located at: DeploymentShare\Tools\x86\USMT4) and specify which folders to backup. There you can also specify which additional drives/folder locations to back-up.

    Then USMT copy's data to a designated network share, usb drive or something like that.

    Thereafter, you install / migrate from Windows XP to Windows 7 with MDT, and choose to format and partition your entire disk. Which leaves you with one partition remaining, after which USMT will begin restoring the back-upped content back to your disk, on a designated folder.

    It is perfectly possible, I just don't have experience in configuring the MigUser.xml file, but it cant be that hard. Since there are comments present which exactly tell you what the following statements are doing.

    Good luck!


    If this post is helpful please click "Mark for answer", thanks! Kind regards

    Wednesday, October 16, 2013 8:19 AM
  • Thanks Rens. As mentioned, I also understand that it is possible to accomplish this with USMT. I am looking for assistance on what changes do I need to make in the USMT mig*.XML file/files so that the data on D drive is also copied as part of user data capture and then restored on the new C drive.

    Regards,


    SinghP80

    Wednesday, October 16, 2013 12:15 PM
  • I was able to accomplish this using the reference below:

    http://technet.microsoft.com/en-us/library/hh824836.aspx



    SinghP80

    • Marked as answer by ITCP80 Wednesday, October 16, 2013 1:33 PM
    Wednesday, October 16, 2013 1:33 PM
  • I was able to accomplish this using the reference below:

    http://technet.microsoft.com/en-us/library/hh824836.aspx



    SinghP80


    Were you able to actually re-route the content captured from "D:\" into "C:\Old_D_Drive\" - because from what I have tried so far it just does not seem possible for USMT to re-route content from a D: drive into a new folder on C: - I just end up with the Content from D: being loosely deposited on the Root of the C: drive.  The loadstate.log shows that the content relocation rule was skipped due to there being no D: drive present on the destination computer.  If I DO have a D: drive present then the content simply goes back there, and not where the relocation rule states.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    Tuesday, February 04, 2014 8:14 PM
  • I was able to accomplish this using the reference below:

    http://technet.microsoft.com/en-us/library/hh824836.aspx



    SinghP80


    Were you able to actually re-route the content captured from "D:\" into "C:\Old_D_Drive\" - because from what I have tried so far it just does not seem possible for USMT to re-route content from a D: drive into a new folder on C: - I just end up with the Content from D: being loosely deposited on the Root of the C: drive.  The loadstate.log shows that the content relocation rule was skipped due to there being no D: drive present on the destination computer.  If I DO have a D: drive present then the content simply goes back there, and not where the relocation rule states.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    It has been a while but absolutely it works. We migrated data for over 300 users and if a user had a D drive, the data was dumped in to C drive under the folder specified. If D drive was not present, then it was simply skipped.

    Something to the effect of this I believe:

    <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
    <component type="Documents" context="User">
      <displayName>Move D drive data to C drive</displayName>
      <role role="Data">
         <rules>
          <!-- Migrate all directories and files present in D: Drive -->
          <include>
            <objectSet>
              <pattern type="File">D:\* [*]</pattern>
            </objectSet>
          </include>
          <!-- This migrates all files and directories from D: to specified folder.-->
          <locationModify script="MigXmlHelper.RelativeMove('D:\','C:\Old_D_Drive')">
            <objectSet>
              <pattern type="File">D:\* [*]</pattern>
            </objectSet>
          </locationModify>
        </rules>
       </role>
     </component>
    </migration>




    SinghP80


    • Edited by ITCP80 Tuesday, February 04, 2014 8:35 PM
    Tuesday, February 04, 2014 8:35 PM
  • I was able to accomplish this using the reference below:

    http://technet.microsoft.com/en-us/library/hh824836.aspx



    SinghP80


    Were you able to actually re-route the content captured from "D:\" into "C:\Old_D_Drive\" - because from what I have tried so far it just does not seem possible for USMT to re-route content from a D: drive into a new folder on C: - I just end up with the Content from D: being loosely deposited on the Root of the C: drive.  The loadstate.log shows that the content relocation rule was skipped due to there being no D: drive present on the destination computer.  If I DO have a D: drive present then the content simply goes back there, and not where the relocation rule states.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    It has been a while but absolutely it works. We migrated data for over 300 users and if a user had a D drive, the data was dumped in to C drive under the folder specified. If D drive was not present, then it was simply skipped.

    Something to the effect of this I believe:

    <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
    <component type="Documents" context="User">
      <displayName>Move D drive data to C drive</displayName>
      <role role="Data">
         <rules>
          <!-- Migrate all directories and files present in D: Drive -->
          <include>
            <objectSet>
              <pattern type="File">D:\* [*]</pattern>
            </objectSet>
          </include>
          <!-- This migrates all files and directories from D: to specified folder.-->
          <locationModify script="MigXmlHelper.RelativeMove('D:\','C:\Old_D_Drive')">
            <objectSet>
              <pattern type="File">D:\* [*]</pattern>
            </objectSet>
          </locationModify>
        </rules>
       </role>
     </component>
    </migration>




    SinghP80



    Yeah, it all looks and sounds like it should work, but no joy yet.  Do you still have your xml files you used for migration to share?  Try as I might I just can't get files captured from other drives into a folder (C:\RestoredData)  Grr.

    My Personal Blog: http://madluka.wordpress.com

    Tuesday, February 04, 2014 9:48 PM
  • I will try to get the files but can't promise. It was for a client. I am guessing you are using USMTMIGFILES parameter in your CS.INI for MDT and calling the Miguser.xml and other files from there.

    Regards,



    SinghP80

    Wednesday, February 05, 2014 5:01 PM
  • Actually at the moment I'm just using the SCANSTATE and LOADSTATE via the command line manually on two different systems until I can get it to do what I want it to do.

    For testing, I am using just a single MigData.xml (based on your above xml) and by using the /nocompress switch I get an uncompressed StateStore created and I can see exactly what I am getting captured, so far so good.  I am having absolutely no joy when restoring that data getting it to redirect to a folder on C:\ - the closest I have is that it dumps it on the root of C:

    Most frustrating.


    My Personal Blog: http://madluka.wordpress.com

    Wednesday, February 05, 2014 5:27 PM
  • Yes. I wonder if it makes any difference if you instead add the above section in MIGUSER.XML. Probably not but I am just curious.

    My arguments were as below not that it should make any difference:

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


    SinghP80

    Wednesday, February 05, 2014 5:46 PM
  • I did start with the D:\* [*] pattern in the MigUser.xml originally, but that wasn't working out. I would also like the data captured under SYSTEM context from C: and D: to be placed into separate folders and I am not sure if more than one LocationModify can be used in the same xml. Trial and Error continues...

    My Personal Blog: http://madluka.wordpress.com

    Thursday, February 06, 2014 7:15 PM