My time was limited yesterday, but to answer your questions. . . * I eliminated an unnecessary USMT group in the task sequence. It was using hard linking and I wanted to make sure that process was not causing issues. * Only one mode of PC was tested (old COmpaq DC 5750) * The environment is at a client, so I am not aware of the changes that take place necessarily
I am asking their team to try to get me the smsts.log before the machine reboots so I can review it. PXE booting and doing a "new computer" scenario works but the refresh has the issue. Is there a difference in how the scenarios use the boot image? I hesitate to make major changes to the boot image (like adding drivers) since it works with PXE. Thanks! Jeff On Thu, Jul 17, 2014 at 11:13 PM, Mike Dzikowski < [email protected]> wrote: > Are there any steps that could cause issues, that are ran while in > Windows? Is this happening on all models? Is the firmware up to date? Did > this issue start after making any changes to the environment? Any new > drivers added or updated on the machines? > > Shot in the dark, but have you thought about grabbing the SMSTS.LOG file > before the machine reboots? That might have some clues. . . > > Mike D- > > ------------------------------ > Date: Thu, 17 Jul 2014 15:52:48 -0500 > Subject: [mssms] Odd Task sequence failure > From: [email protected] > To: [email protected] > > > I have an issue in CM07 with a task sequence failing. THe issue is with > refresh scenarios. A large number of the PCs are starting the TS in > Windows, then starting the reboot to Windows PE. After the reboot, the > PC's disk is failed and the task sequence does not continue. It does not > even try to boot WinPE. Subsequent reboots of the PC yield the same result > - black screen with a disk error. > > Has anyone seen this or something similar? > > Thanks, > > Jeff > > >
