SOLVED SCCM USMT Task Sequence not take in charge my config.xml

[BrunoBoy]

Hello,
Perhaps you could help me.
SCCM 12, USMT 5
I have configured a tasksequence and use for the variable :

for Backup :
OSDMigrateAddtionalCaptureOptions
the value : /config:"%_SMSTSMDataPath%\Packages\%_OSDMigrateUsmtPackageID%\%PROCESSOR_ARCHITECTURE%\ConfigBB.xml"

But when I run it, no config file is used :
log : Command line: C:\WINDOWS\ccmcache\1a\amd64\scanstate.exe \\sva0031.xx.xxx.net\SMPSTOREF_B88950F3$\19FA2E72C12325C31554C8587E4626CAB3D74AAD8FD7ADCB6DE73006164C6FFE /o /localonly /encrypt /keyfile:**** /efs:skip /v:5 /vsc /l:C:\WINDOWS\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\scanstateprogress.log /i:C:\WINDOWS\ccmcache\1a\amd64\MigUserBB.xml

For Restore :
I did the same thing for the variable : OSDMigrateAddtionalRestoreOptions
value : /config:"%_SMSTSMDataPath%\Packages\%_OSDMigrateUsmtPackageID%\%PROCESSOR_ARCHITECTURE%\ConfigBB.xml"

when I run it, this time my configBB.xml is taking in charge :
log : Command line: C:\WINDOWS\ccmcache\18\amd64\loadstate.exe \\sva0031.xx.xxx.net\SMPSTOREF_B88950F3$\C417B62D0993DF54DB962D31CC2B91616ADE08F9E97B544272B3C5A474A1A6CF /decrypt /keyfile:**** /ue:*\* /ui:LIADOM01\lmdsab /v:5 /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\WINDOWS\ccmcache\18\amd64\MigUser.xml /config:C:\_SMSTaskSequence\Packages\%_OSDMigrateUsmtPackageID%\AMD64\ConfigBB.xml

So Why for the backup, SCCM do not take in charge my configBB.xml file ?

More, I see that MigUserBB.xml is well found in : C:\WINDOWS\ccmcache\1a\amd64\ (where my package is downloaded).
Why for the restore, it search it in : C:\_SMSTaskSequence\Packages\%_OSDMigrateUsmtPackageID%\AMD64\ and not in C:\WINDOWS\ccmcache\1a\amd64\ ?
It's important for me to use my configBB.xml

any Idea ?

PS. When I use scansate et loadstate manually with my configBB.xml, all works fine...

Thanks a lot and have a nice day.

 

[BrunoBoy]

Hello,

I just found the solution. In fact I had to create a package that copy my file. Add a new task in my sequence to execute it, and use the new path on the computer with my variable.

 

[Prajwal Desai]

Cool.. that was quick !!