Hi :)

I've run into a problem that I've been spending far to much time on already :P

I'm trying to use USMT hardlink functionallity for future re-installations, but it will not work unless I do a manual reboot during.

It looks like this:
Task 1, copy files:
-----
    rem copying files...
    xcopy *.* /e /v /y C:\Windows\USMT\
------

Task 2, run the scanstate:
------
  @ECHO On

  echo Removing old USMT store if it exist...
  rem Usmtutils.exe /rd c:\USMTstore /Y
  if exist c:\USMTstore rd c:\USMTstore /S /Q

  c:
  cd Windows\USMT

  echo Setting USMT_WORKING_DIR
  set USMT_WORKING_DIR=C:\Windows\USMT
  echo USMT_WORKING_DIR was set to: %USMT_WORKING_DIR%

  echo Running ScanState...
  C:\Windows\USMT\scanstate.exe c:\USMTstore /v:13 /o /c /offlineWindir:C:\Windows /hardlink /nocompress /efs:hardlink /i:C:\Windows\USMT\MigApp.xml /i:C:\Windows\USMT\MigDocs.xml

  Y:
-----------
If I run this I will end up with an error when Windows 7 comes to Expanding files
Error: "Windows cannot install required files. Make sure all files required for installation are available, and restart the installation"

If I then reboot, and run the installation without the Scanstate hardlink component in it, then it works like a charm and all the files are still there and I can do a loadstate.
But I'm forced to do a reboot after, it seems like the hardlink process locks the disk or something.


Anyone have any good ideas?

This would save a lot of time during re-installs if we can avoid copying all the user data before and after a rebuild, we are currently running split drives one for windows/programs and one for user files, but every now and then Windows and Programs size keep increesing so we have to resize disks, and that is what I'm trying to avoid.


I tried to do a diskpart to do a "remove" to unload the C drive and map it again, but I cannot "remove" it :/


Edit: added full error msg

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
0

Hey Rene,

What i did was create a bat file to do the migration.

scanstate.exe c:\store /v:13 /o /c /hardlink /nocompress /efs:hardlink /i:MigApp.xml /i:MigDocs.xml /offlineWinOld:c:\windows.old\windows
loadstate.exe c:\store /v:13 /c /lac /lae /i:migapp.xml /i:migdocs.xml /sf /hardlink /nocompress


I put the bat in the USMT folder and zipped it all up.

Uploaded the whole thing as an application and call my bat file for the command line.

Just remember NOT to format the partitions when you lay down Win7 or else you won't get the windows.old.

Hard link migration works like a champ!

Answered 07/20/2011 by: dchristian
Red Belt

  • David can you go into more details on exactly how you accomplished this with the K2000?  I'm doing a scripted install and would like to use the hardlink migration as part of that scripted install.  I am using the offline user state scan to gather user states.  I'd like to modify that to do it with hardlinks.  Any thoughts?

  • This task needs to be a POSTINSTALL task.  That's what I didn't get first time around.

Please log in to comment
0

Thanks :)

I guess the only diffrence would be that I use "/offlineWindir" and you use "/offlineWinOld"

I'll give it a try, I guess you run it as a post install task in windows then or still in PE ?

Answered 07/21/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0

I'll run it inside of windows.

Usually as the last task.

Answered 07/21/2011 by: dchristian
Red Belt

  • I'm trying to set up hardlink migration tasks for XP to Win7 x64 migrations we are doing. I'm new to the hardlink aspect of things so I'm not sure I'm understanding this completely. I assumed the process was something like this:

    1. Run the scanstate commands as a preinstall task within the WinPE environment after PXE booting the machine to KBOX. Let it run.
    2. Perform the scripted install as usual and let Win 7 install.
    3. Run the loadstate command as a post install task at or near the end from within the new OS.

    Is this correct or am I misunderstanding anything? I've tried a few different task trials so far without luck. I'm guessing its something simple I'm missing, but if anyone can post or share any details about what process has worked for them for hardlink that would be great.

    Thanks.

Please log in to comment
0

Perfect thanks, I'll test it right away :)

I don't know why I didn't notis the "OfflineWinOld" command, I guess it was too close to the "OfflineWinDir" :)

Answered 07/21/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0

it works like a charm ;)

Thanks a lot :)

Answered 07/21/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0

I'm trying to set up hardlink migration tasks for XP to Win7 x64 migrations we are doing. I'm new to the hardlink aspect of things so I'm not sure I'm understanding this completely. I assumed the process was something like this:

1. Run the scanstate commands as a preinstall task within the WinPE environment after PXE booting the machine to KBOX. Let it run.
2. Perform the scripted install as usual and let Win 7 install.
3. Run the loadstate command as a post install task at or near the end from within the new OS.

Is this correct or am I misunderstanding anything? I've tried a few different task trials so far without luck. I'm guessing its something simple I'm missing, but if anyone can post or share any details about what process has worked for them for hardlink that would be great.

Thanks.

Answered 09/20/2012 by: timantheos
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity