upgrade XP to Win7 with USMT hard link

[Kinom]

Hi all,

 

I deed some tests with SCCM2007, USMT 4.0 and MDT 2010 to update WinXP to Win7.

 

Everything go’s well until the second last step, then I get the following error 0x00000024 :angry:

 

Can someone help me with this problem?

In attachment you will find my 2 SMSTS.logs files

 

Thanks

[Kinom]

Hi all,

 

I deed some tests with SCCM2007, USMT 4.0 and MDT 2010 to update WinXP to Win7.

 

Everything go’s well until the second last step, then I get the following error 0x00000024 :angry:

 

Can someone help me with this problem?

In attachment you will find my 2 SMSTS.logs files

 

Thanks

 

 

 

smsts.log

 

smsts-20091013-194352.log

[Peter van der Woude]

Where is the Hard-Linking in this TS? To use Hard-Links in a TS you need to create three Task Sequence Variables:

1. Name: OSDStateStorePath

Value: %_SMSTSUserStatePath%

2. Name: OSDMigrateAdditionalCaptureOptions

Value: /nocompress /hardlink

3. Name: OSDMigrateAdditionalRestoreOptions

Value: /nocompress /hardlink

 

See also: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx

[Kinom]

Where is the Hard-Linking in this TS? To use Hard-Links in a TS you need to create three Task Sequence Variables:

1. Name: OSDStateStorePath

Value: %_SMSTSUserStatePath%

2. Name: OSDMigrateAdditionalCaptureOptions

Value: /nocompress /hardlink

3. Name: OSDMigrateAdditionalRestoreOptions

Value: /nocompress /hardlink

 

See also: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx

 

Thanks for the reply

 

I will do a new test and let you know

[Kinom]

Hoi Peter,

 

Thanks for helping me

 

I deed another test and it went perfect

 

So it means I don’t need the MDT packages like I read before

 

Cheers

[Peter van der Woude]

Correct, you don't need the MDT Tools for a Hard-Link Migration.

[Kinom]

Correct, you don't need the MDT Tools for a Hard-Link Migration.

 

Thanks

[boognish]

My situation calls for using /md switch during the loadstate. I am having problems getting that to work. Is it still supported using hard link?

 

My Value for OSDMigrateAdditionalRestoreOptions is /nocompress /hardlink /md:OldDomain:NewDomain

[67_dbc]

I know it's an old post..... SIlly question, does this apply to Windows XP to Windows 7 when using SCCM 2012 intergrated with MDT 2012 Update 1? If so, where in the TS does this go? I assume at the top of the TS before Capture User State correct?

 

Can this also be added in in the Capture User State variable or does it need to run on it's own seperate Set Task Sequence Variable line?

 

Been having issues with my Hard-link migrations, where capturing user state is functional, I see the StateStore folder with content inside of it but getting the user data to work under Restore is hanging up. LoadState.log only show it erroring out because it can't create/migrate SetupUser account. I have /ue switches but it's not sticking

 

Any help would be greatly appreciated

 

 

Resolved my issues, needed to include the /lac switches as well.

Edited August 8, 2013 by 67_dbc