I looked at the ZTIUserState.wsf script and it the following base capture and
restore parameters are as follows:
LoadStateArgs: /v:5 /c /lac
ScanStateArgs: /v5: /c /o
After researching this I thought all I would need to do is add /lac to my
SetOSDMigrateAdditionalRestore options, but it looks like this is already set
by default.
Any ideas?
Thanks,
Brian
From: [email protected]
To: [email protected]
Subject: [MDT-OSD] LoadState Task Sequence fails
Date: Mon, 24 Mar 2014 11:03:05 -0500
I have created two separate task sequences 1) to execute ScanState and 2)
executes LoadState
My ScanState TS is fairly Straight forward.
1) Use Toolkit Package
2) Gather
3) Make Directory (\\server\migdata$\%osdcomputername%)
4) Set OSDStateStorePath (\\server\migdata$\%osdcomputername%)
5) Set OSDMigrateAdditionalCaptureOptions (/UEL:90)
6) Capture User State
LoadState TS is as follows:
1) Use Toolkit Package
2) Gather
3) Set OSDStateStorePath
4) SetOSDMigrateAdditionalRestoreOptions (/UE:%ComputerName%\*
5) Restore User State
6) Restart Computer
The LoadState.log file states the following: The account PCname\Admin is chose
for migration, but the target doesn't have the account PCname\Admin. See
documentation for /lac, lae, /ui and /uel options.
Can I get by with adding /lac switch to my
SetOSDMigrateAdditionalRestoreOptions step? Or do I need to make changes to my
ScanState TS step for OSDMigrateAdditionalCaptureOptions?
Thanks,
Brian
I lo
