Crugory Posted June 12, 2012 Report post Posted June 12, 2012 My Build and Capture Task Sequenses fail to install Windows. The TS launches no problem, copies down the OS Installer files to the C:\_smstasksequences\packages\<packageid> folder but doesn't launch the windows setup. The stange thing is that it reports that windows has been installed and moves on to trying to install drivers and configure windows, which causes the TS to fail. I've refreshed the OS Installer files a few times with the same result. I've also tried using Windows 7 RTM, Windows 7 SP1 and Windows 2008R2 all with the same result. I've also rebuild the TS Several times... I'm fresh out of idea's and am really hoping someone here can help. Below is a snippet from the smsts.log on the client. Wiping C:\ ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Set "C:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Skipping C:\_SMSTaskSequence for wipe ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Calculating expected free space. ApplyOperatingSystem 6/12/2012 11:59:01 AM 1052 (0x041C) Reporting deletion progress. ApplyOperatingSystem 6/12/2012 11:59:01 AM 1052 (0x041C) Successfully wiped C:\ ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Opening image file C:\_SMSTaskSequence\Packages\FMC000F0\sources\install.wim ApplyOperatingSystem 6/12/2012 11:59:01 AM 1752 (0x06D8) Closing image file C:\_SMSTaskSequence\Packages\FMC000F0\sources\install.wim ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Found the image language: 'en-US' ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Found the Windows setup program at C:\_SMSTaskSequence\Packages\FMC000F0\sources\setup.exe ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) The file C:\_SMSTaskSequence\Packages\FMC000F0\sources\setup.exe is version 6.1 and architecture 0 ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Opening image file C:\_SMSTaskSequence\Packages\FMC000F0\sources\install.wim ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting schema.dat from image index '1' ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Applying image 1 to volume C:\_SMSTaskSequence\OSD\Vista ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32 ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI\Store ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI\Store\Machine ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI\Store\Machine\SCHEMA.DAT ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32 ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI\Store ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Extracting \Windows\System32\SMI\Store\Machine ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Closing image file C:\_SMSTaskSequence\Packages\FMC000F0\sources\install.wim ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Setting hive location to "C:\_SMSTaskSequence\OSD\Vista\Windows\System32\SMI\Store\Machine" ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Getting namespace "Microsoft-Windows-Setup" for architecture "x86" ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Added list item with key value '/IMAGE/INDEX' ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Getting namespace "Microsoft-Windows-Deployment" for architecture "x86" ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "x86" ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Getting namespace "Microsoft-Windows-International-Core-WinPE" for architecture "x86" ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Writing configuration information to C:\_SMSTaskSequence\unattend.xml ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Preparation completed sucessfully. ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\FMC000F0 ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) reference count 1 for the source C:\_SMSTaskSequence\Packages\FMC000F0 before releasing ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Released the resolved source C:\_SMSTaskSequence\Packages\FMC000F0 ApplyOperatingSystem 6/12/2012 11:59:02 AM 1752 (0x06D8) Process completed with exit code 0 TSManager 6/12/2012 11:59:02 AM 1376 (0x0560) !--------------------------------------------------------------------------------------------! TSManager 6/12/2012 11:59:02 AM 1376 (0x0560) Successfully completed the action (Apply Operating System) with the exit win32 code 0 TSManager 6/12/2012 11:59:02 AM 1376 (0x0560) Thanks for your help! Quote Share this post Link to post Share on other sites More sharing options...
Iroqouiz Posted June 13, 2012 Report post Posted June 13, 2012 Can you post screenshots of your TS steps? Quote Share this post Link to post Share on other sites More sharing options...
timungless Posted March 7, 2014 Report post Posted March 7, 2014 Hi Did you ever work out what was causing this problem? I am seeing the same thing. thanks Quote Share this post Link to post Share on other sites More sharing options...
kevlar01 Posted March 10, 2014 Report post Posted March 10, 2014 Perhaps you can try to use an Operating System Image, rather than an Operating System Installer (the old-skool method) ? Quote Share this post Link to post Share on other sites More sharing options...