Bit of a long winded question I'm afraid, please bare with me!
I've set up an OS deployment task sequence (SCCM 2007 R2 and MDT 2010) using a 'Client Task Sequence' template from the 'Create Microsoft Deployment Task Sequence' option. During the Capture User State task we get the "/encrypt can't be used with /nocompress" error. I didn't knowingly set up hardlinking but I guess USMT 4 does this automatically? (Question 1: Is that correct?).
Anyway it would appear that the way around this is to declare a TS variable of OSDMigrateAdditionalCaptureOptions with a value of /nocompress /hardlink as described in http://blogs.technet.com/b/configurationmgr/archive/2010/06/30/how-to-use-usmt-4-hardlinking-in-a-configuration-manager-2007-task-sequence.aspx
My questions are:
Q2: Presumably the Scanstate command that has been run in my task sequence has the /nocompress and /encryt parameters in it, does declaring a value for the OSDMigrateAdditionalCaptureOptions variable overwirte the exising parameters for Scanstate in my TS or
append them?
Q3: This question is direct at Nial Brady as I know he reads these and has been very helpful previously (Hi Nial!), we downloaded the "...using the Hardlinking.xml" task sequence (from here: http://www.windows-noob.com/forums/index.php?/topic/1633-sample-xp-to-windows-7-task-sequences/)and it didn't seem to have anything in particular to deal with hardlinking and did not set a TS variable for OSDMigrateAdditionalCaptureOptions. I was wondering what is different about this TS as compared to the standard task sequence template I mentioned at the start of this post?