Hi Everyone, I'm using SCCM 2007 SP2 R3 with MDT 2012 integrated and have a question about the Side-By-Side Migration scenario. My standard REFRESH task sequence works fine for PXE builds and refreshing existing PC's. In this task sequence I am using Hardlinks and setting the OSDMigrateAdditionalCaptureOptions and OSDMigrateAdditionalRestoreOptions variables to set my command lines for loadstate and scanstate to use "/hardlink /nocompress /ue:%computername%\*" so I exclude migrating local users. All seems to be good with this TS and systems capture/restore user state properly using hardlinks and my custom XML in a standard REFRESH scenario. Now we bring in Side-By-Side migration... I have created a TS for capturing user state to the State Migration Point (SMP) and it runs and captures user data OK (after tying ccmcertfix.exe into the sequence) to the SMP. My question is on the Restore. In all the guidance I have read it says to use the normal REFRESH TS to deploy your machine and that the User State data will automatically come back (as long as you created your Computer Association BEFORE running the Capture). But how is this going to work with OSDMigrateAdditionalRestoreOptions set to include "/hardlink /nocompress" in the TS right before the restore step? Will it fallback to the SMP if it doesn't find USMT hardlinked data locally and just ignore these parameters? Do I need to have two steps for setting OSDMigrateAdditionalRestoreOptions with one set for Hardlink (Standard Refresh) and the other not (Replace) and then have conditions on each of these so it sets it appropriately? If so, would you set condition based on the "DeploymentType" variable or "USMTLOCAL" variable or something else? Any additional insight would be much appreciated. I really need to get this going today. :) Thanks! -Jeff    

Looks like I'll answer my own question. :) Just finished testing both REPLACE and REFRESH scenarios doing exactly what I said above with the OSDMigrateAddtionalRestoreOptions. I have two steps in my TS to set this variable. Both steps are right before the "Restore User State" step. The first one I setup for for REFRESH and the second one is for for REPLACE. On the REFRESH step I'm setting TS variable OSDMigrateAdditionalRestoreOptions to /hardlink /nocompress /ue:%computername% with a condition on the step for TS variable "DeploymentType" equal to REFRESH. For the next step I'm setting the same variable (OSDMigrateAdditionalRestoreOptions) with only "/ue:%computername%" (without the quotes) with a condition of USMTLOCAL not equals TRUE. With this configuration my user state captured and restored successfully for both REFRESH and REPLACE scenarios using harlinks for REFRESH and my State Migration Point for the Side-By-Side migration. Checking LOADSTATE.LOG in both scenarios shows that the correct command line parameters were used. Now to see why Office profile settings didn't come over... But that appears to be related to a USMT hotfix KB2023591.