I have a Refresh TS setup in SCCM using USMT and it works just fine, except one thing - The /NoCompress argument I am including in my CustomSettings.ini file is not being read by ScanState. Background: Using Virtual machines, I'm migrating XP clients to Win7 clients in SCCM enterprise (with MDT2010 integrated). I am not using an SMP yet (management has not authorized it yet) and they want me to use a Network Share instead. I am successfully using ScanState with the configuration .XML files to capture what i need, but they always end up in .MIG format. I have the Gather TS and a TS that sets my OSDStateStore Path wvariable prior to the ScanState working just fine. When I look in the scanstate.log file it has all the parameters as checked in my Capture State Store Task (using customized MigApp.xml and Miguser.xml files, enabling 'Continue if some files can't be copied', etc.). I even have my variable OSDMigrateAdditionalCaptureOptions=/ue:%computername%\* being read just fine in the CustomSettings.ini file. But I can't seem to get the ScanStateArgs=/NOCOMPRESS argument to be read. I don't have the conflicting /encrypt switch being used so that can't be the cause. CustomSettings.ini file (acual server names were removed for security reasons); [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES SkipBDDWelcome=Yes DeploymentType=REFRESH ComputerBackupLocation=NONE ScanStateArgs=/NOCOMPRESS OSDMigrateAdditionalCaptureOptions=/ue:%computername%\* Home_Page=http://www.google.com/ WSUSServer=http://'wsus server' SLShare=\\'network share'\OSD_Logs-Refresh$ - resulting scanstate.exe command from the scanstate.log for the virtual XP client: 26 May 2011, 09:46:04 -04:00, 00:00:00, program, scanstate.exe, productVersion, "6.1.7600.16385 (win7_rtm.090713-1255)", computerName, D193564-V2, commandLine, "\\'domain server'\IMAGES$\SMSPKG\CDC00183\x86\scanstate.exe \\server\StateStore$\D193564-V2 /o /localonly /c /efs:copyraw /l:C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstateprogress.log /i:\\'domain server'\MAGES$\SMSPKG\CDC00183\x86\MigUser.xml /i:\\'domain server'\IMAGES$\SMSPKG\CDC00183\x86\MigApp.xml /ue:D193564-V2\*" Also, if I run my desired command manually from the client in a batch file it succeeds in creating the uncompressed file structure: \\'server'\IMAGES$\SMSPKG\CDC00183\x86\scanstate.exe \\'server'\StateStore$\%ComputerName% /o /localonly /c /efs:copyraw /l:C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\WINDOWS\system32\CCM\Logs\SMSTSLog\scanstateprogress.log /i:\\'server'\IMAGES$\SMSPKG\CDC00183\x86\MigUser.xml /i:\\smp-at1-dp12.cdc.gov\IMAGES$\SMSPKG\CDC00183\x86\MigApp.xml /nocompress /ue:%ComputerName%\* Has anyone got any ideas or experienced a similar problem? Please help...I'm at my wits end on this issue! Thanks. Thanks, WinRoller

I'm afraid this i by known issue when using MDT integration for that scenario! Here is a takeout from the MDT chm file _____________________________________________________________________________________________________________________________________ The following is a list of known issues, limitations, and recommendations for saving and restoring user information in MDT 2010: · For LTI deployments, do not add any of the following USMT command-line parameters to the ScanStateArgs or LoadStateArgs properties, as they cause the saving and restoration of user state information to fail: · /hardlink · /nocompress · /encrypt · /key · /keyfile · /vsc · /l · /i · User state migration data may not be restored properly depending on the disk configuration of the target computer when deploying Windows 7. This issue can occur when the target computer has two physical hard disks, Disk_0 and Disk_1. Disk_0 contains the C volume, which is encrypted using BitLocker Drive Encryption. The MDT 2010 deployment process is configured to deploy a new operating system to Disk_1. The problems in the deployment process occur as follows: · Early the deployment process, the minint and smstasksequence folders are copied to the existing C volume, which is encrypted. · Disk_1 is partitioned and formatted properly in preparation for deploying the target operating system. · The target operating system is installed on the new partition and disk volume on Disk_1. · During the State Restore Phase, the original C volume is not assigned a drive letter, so the task sequence steps in the State Restore Phase cannot access the minint and smstasksequence folders on the BitLocker Drive Encryption–encrypted drive. The restoration of the user state migration data fails. The result is that the target operating system is installed, but the restoration of the user state migration data fails. _______________________________________________________________________________________________________________________________________ I would either run a command line, if you know that work, or consider hardlink Michael Petersen http://blog.coretech.dk/mip/

Thanks... I just verified that the command line added as a TS works fine so I guess I'll be using it that way.Thanks, WinRoller

Seems like the way to go.. I would definitely look into Hardlinking though, makes things allot easierMichael Petersen http://blog.coretech.dk/mip/

Seems like the way to go.. I would definitely look into Hardlinking though, makes things allot easierMichael Petersen http://blog.coretech.dk/mip/