Yeah, I'm not sure what's causing the issue, so very difficult to re-create.
From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Monday, August 26, 2013 12:13 PM To: [email protected] Subject: RE: [MDT-OSD] .NET components missing after Image Deployment Ahh, if you have 148 working it's unlikely it's the image. I would maybe start with an update or patch possibly breaking it. I assume you cant recreate the issue either? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Joshua Searles Sent: Monday, August 26, 2013 3:07 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] .NET components missing after Image Deployment I've not tried manually putting the image down on the disc. Most of the time the TS works great. I've just seen 2 systems in our environment (out of about 150 ZTI deployments) that have given me the behavior of .NET missing. It's a goose chase, and I hate chasing geese. Thanks, Joshua From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Daniel Ratliff Sent: Monday, August 26, 2013 8:58 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] .NET components missing after Image Deployment If you manually lay down the .wim using DISM/imagex does it still have the same .NET issues? If it does, your image is the issue. If it doesn't, something in your task sequence is the issue. That is where I would start. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Joshua Searles Sent: Monday, August 26, 2013 11:54 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] .NET components missing after Image Deployment I see where the misunderstanding is. There is no .NET step in the task sequence. .NET is included in the windows 7 image. The problem is, when the .wim gets laid down on the disk drive, something is getting corrupted, and anything that uses .NET will fail to launch. A .NET repair, scrub, and re-install, will not resolve the issue. So far the only fix is a re-image of the workstation. Thanks, Joshua From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Niall Brady Sent: Wednesday, August 21, 2013 8:32 AM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] .NET components missing after Image Deployment 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]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Tuesday, August 20, 2013 11:51 PM To: [email protected]<mailto:[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]<mailto:[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. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
