Hi Guys, Hope this is an easy one. I have my task sequence building new computers all is working great. However i thought it would be good if i could add a task in the task sequence that will capture the users entire harddrive in a WIM file to one of our file servers. this way if users moan and complain about losing a file, we have a backup of their entire file system. My only problem with this, is i can't seem to figure out how to use a dynamic filename for the wim file. I would want to put something like this in the destination field: \\server\share\%COMPUTERNAME%.wim in WinPE the %COMPUTERNAME% variable is just "MiniPC" or something like that, so that won't work. but i assume the actual computer name must be in a task sequence variable somewhere? can i use it in this case? or is there some other way i can achieve my goal of having a unique filename/location for each captured WIM image? Thanks! Nick.

%_SMSTSMachineName% or %OSDComputername%... A suggestion though, is to capture to the same WIM, using the append command, in that way you will not have a huge amount of wim files taking up lots of space, but rather one withe lots of index files. The benefit is that files from one image is reused in the next image meaning that the actual image does only increase with the files that differ. This of cause only workers if you capture to the same file name... Try and take a look at this post I wrote http://blog.coretech.dk/osdeploy/capture-none-syspreped-image-using-sccm-running-imagex-from-a-ts/ Michael http://kongkuba1.spaces.live.com

There is actually a Task Sequence provided my integrating MDT 2010 into OSD that will do exactly what you want and will utilize a State Migration Point. http://blogs.technet.com/b/mniehaus/archive/2010/07/20/mdt-2010-update-1-fixes-to-configmgr-state-migration-point-scenarios.aspx/ It will use the same SMP that is used by USMT to capture a backup of the current drive with the actual computer name as it was not from PE. After you integrate MDT 2010 into OSD, a toolkit package will need to be created as described here: http://blog.coretech.dk/osdeploy/creating-and-using-toolkit-package/ These two posts helped me setup something very similar!

hi Michael, Thanks for this article, looks perfect! I have set up the Toolkit and the task sequence steps as the initial 4 steps of my task sequence to build my Win7 machine. It all goes well, however my next step after backing the current drive up to a WIM is to partition and format the drive. here it gets stuck with: Disk 0 contains protected path "C:\_SMSTaskSequence\StateStore" FALSE, HRESULT=00000005 and it fails here. I never had this problem before adding this ZTIBackup.wsf task, so i can only assume something with this task has done it. I had a look in the C:\_SMSTaskSequece\StateStore\ folder, and it's empty (after the error occurs, so i'm not sure if it was cleared before i got to see it or not). Should i just create another task that deletes this StateStore folder before i attempt to partition the drive? EDIT - i tried this and it doesn't work. even if i delete the StateStore folder and reboot before trying to partition, it says that the StateStore folder is protected and it won't partition the drive (even though there's no StateStore folder anymore!) thanks!

hi Michael, Thanks for this article, looks perfect! I have set up the Toolkit and the task sequence steps as the initial 4 steps of my task sequence to build my Win7 machine. It all goes well, however my next step after backing the current drive up to a WIM is to partition and format the drive. here it gets stuck with: Disk 0 contains protected path "C:\_SMSTaskSequence\StateStore" FALSE, HRESULT=00000005 and it fails here. I never had this problem before adding this ZTIBackup.wsf task, so i can only assume something with this task has done it. I had a look in the C:\_SMSTaskSequece\StateStore\ folder, and it's empty (after the error occurs, so i'm not sure if it was cleared before i got to see it or not). Should i just create another task that deletes this StateStore folder before i attempt to partition the drive? EDIT - i tried this and it doesn't work. even if i delete the StateStore folder and reboot before trying to partition, it says that the StateStore folder is protected and it won't partition the drive (even though there's no StateStore folder anymore!) thanks!

hi Michael, Thanks for this article, looks perfect! I have set up the Toolkit and the task sequence steps as the initial 4 steps of my task sequence to build my Win7 machine. It all goes well, however my next step after backing the current drive up to a WIM is to partition and format the drive. here it gets stuck with: Disk 0 contains protected path "C:\_SMSTaskSequence\StateStore" FALSE, HRESULT=00000005 and it fails here. I never had this problem before adding this ZTIBackup.wsf task, so i can only assume something with this task has done it. I had a look in the C:\_SMSTaskSequece\StateStore\ folder, and it's empty. Should i just create another task that deletes this StateStore folder before i attempt to partition the drive? thanks!

Hey Nick Just add a step to set the task sequence variable OSDStateStorePath to be tha same as your ComputerbackupLocation value ex. OSDStateStorePath = \\server\share Michaelhttp://kongkuba1.spaces.live.com

this fixed it, thanks!