i'd recommend you place the pause step before and after the .NET step, is the .NET step option tab set to continue on error ? if so it'll continue as you are noticing, otherwise you could dig out any logs related to .NET installation.
On Wed, Aug 21, 2013 at 4:49 PM, Joshua Searles <[email protected]>wrote: > Thanks Naill, I didn’t know about the pause ability. I’ll keep that on > the list for future reference. Unfortunately my task sequence from the > system that .NET was missing from completed successfully, and I have yet to > notice any indication of errors(unexpected that is) in the log. **** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Niall Brady > *Sent:* Tuesday, August 20, 2013 11:51 PM > *To:* [email protected] > *Subject:* Re: [MDT-OSD] .NET components missing after Image Deployment*** > * > > ** ** > > you could be guessing all you want, far better to examine the *smsts.log*file > to reveal what went wrong in the installation, to make things easier > I'd suggest you use some form of Pause > ability<http://www.windows-noob.com/forums/index.php?/topic/8846-how-can-i-pause-a-task-sequence-in-system-center-2012-configuration-manager/>in > the task sequence (here's a guide to doing it in CM12, you can do the > same thing in CM07) and place a pause step before (and after) the steps you > think are causing it to fail, thereby finding out what is really going > wrong. > > **** > > ** ** > > On Wed, Aug 21, 2013 at 12:14 AM, Joshua Searles <[email protected]> > wrote:**** > > SCCM 2007, MDT 2010**** > > **** > > So last night was our first deployment in a live environment of our > Windows 7 migration. We deployed to 5 machines, 3 were successful, 1 was > at a system recover screen (OS had finished loaded and almost completed the > installation process), and the last one seems to have necessary .NET > components missing. Powershell won’t work, can’t launch eventvwr, can’t > manage my computer. Anyone seen anything remotely similar? Any thoughts > would be appreciated. This came up in testing once, and we never could > find a cause. These systems are encrypted with PGP Whole Disk Encryption, > and I suspect that may be playing part of the role, but I can’t blame it > yet.**** > > **** > > Thanks,**** > > **** > > Joshua**** > > ** ** > ------------------------------ > > Confidentiality Notice: This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential > and privileged information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message.**** > > ** ** >
