Somtimes you have a Migration scenario that’s not best practies, so you have constellations for migrations that verry customized.
In this Post is only spoken from SCCM SP2 R2 Tasksequence!
Here You have a Blog from Peter van der Woude, thanx for him to Post verry helpfull stuff and also
greatfull Blog over Windows-Noob from Niall,
so i have to mix this two and Customize my self;
The Problem was we have a scanstate MIG File, this in a other Prozess so the User can open a Tool/website to time his Rollout self, in this Prozess the Scanstate execute automaticly.
in the TS (Task Sequence) was not so easy to bring the MIG-File back and load it with loadstate
IMPORTAND: we did’nt use Hardlink, some Computeres changes to a new Hardware in the Rollout Szenario
in the Posts from Peter and Niall you can use the steps thats included by TS’s
So here is the example that i used:
- inklude a new Group in TS (called: USMT loadstate)
- inklude a run command step (called: xcopy loadstate) so we copy the sources from USMT 4.0 local to machine
xcopy /Y /i /s “\\Server\usmt$\USMT4\USMTamd64” C:\USMTamd64
set User with rights to share -> User: Domain\Username - inklude a run command step (called: xcopy MIG)
xcopy /Y /i /s “\\Server\usmt$\migration_data\%_SMSTSMachineName%” C:\USMTamd64
set User with rights to share -> User: Domain\Username - inklude a run command step (called: run Loadstate)
Loadstate_W7_64_v4_1.bat /s
no User set here
in the Loadstate_W7_64_v4_1.bat only this Lines:
c:
cd C:\USMTamd64
loadstate /c “C:\USMTamd64” /i:migapp.xml /i:miguser.xml /i:hslu_xml\MigFolder.xml /ue:%computername% /ui:Domain\* /lac /v:13 /l:logFile\load.log
the next steps are free, you can remove the Folders that you created with xcopy or you can us it later for manually restore UserMIG
no guarente, have fun and Happy Migrate
additional Sources:
loadstate syntaxes
Leave a Reply