We're currently working to integrate USMT w/hard links into our Windows 7 OSD Task Sequence for use with in-place upgrades from Windows XP. The TS works as designed in our lab; however, on 2 of the 5 initial runs on production clients, the TS failed with the error message "Task Sequence failed with the error code (0x8007001B)". Reviewing the smsts.log from one of these clients, it appears that two directories in temp folders on one user's profile could not be deleted during the disk wipe, leading to the error (see attached image): Are the folders noted in the log, in fact, the reason for the TS failures? If so, what can be done to client PC's prior to imaging that will mitigate this risk? Any direction or suggestions provided are greatly appreciated.

Dear I have faced the same problem before, since you are using hard link so all your data has been backed up on your local drive and there no space to install windows, the other option that you have a system drive or the boot drive (which will be around 100 MB) and this one is the one formatted and the SCCM considering it as the main drive for windows so when you try to install it you got message directory is not empty, check the details of the drives of machine you are installing too and update me. Regards, Medhat Rizk

Hi You may refer to below link for this issue. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/c9b9bc3d-8cc9-47db-8337-3a759e3a683f/ Also check what does scanstate.log say during this failure. You'll definitely get more clues from this log file. It may be privilege issue. You also need to check which option you are selecting at "Apply Operating System Image" step like "logical drive letter stored in a variable" or "fixed drive letter"Cheers | Navdeep Sidhu

have you tried running chkdsk prior to scanstate ? create a run command line step with the following options.. cmd.exe /c CHKDSK "C:" /F /R /X Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Thanks Navdeep. The link you provided led to another thread, which identified the temp files that cannot be deleted during the disk wipe as files created by the Office Isolated Conversion Environment. Since we're not running SCCM with MDT Integration, the scripts provided in that link will not work; however, I'll follow Niall's suggestion and run CHKDSK on a test client with one of these temp files present, to determine if this will delete the files in question.