I'd have to go spelunking to find a specific bug if there is one, but a quick note regarding the task sequence engine bits included with MDT...if you look at the version on those files you'll see they are a few versions back. :( We have a work item that didn't make it into 2013 but a high priority item for our next release to revise the task sequence binaries in MDT so they are current. So potentially just doing that may fix some issues.
Aaron From: [email protected] [mailto:[email protected]] On Behalf Of Keith Garner Sent: Wednesday, May 21, 2014 9:05 AM To: [email protected] Subject: RE: [MDT-OSD] Apply OS Image step in TS fails I am aware of this bug, from what I understand it's a problem/bug in the SCCM Task Sequencer Engine. http://keithga.wordpress.com/2014/03/05/failed-to-save-the-current-environment-block/ >From what I recall, this is an interaction issue with Windows 6.1 (Windows 7 >and/or WAIK 3.0) *AND* Modern uEFI 2.3.1 Firmware systems *AND* the SCCM Stand >Alone Task Sequencer when run together. I have only observed this on MDT >LiteTouch, however since MDT LiteTouch uses the same Task Sequencing engine >from SCCM, it's reasonable to assume the issues are the same. When I first saw this (2012?), the only machines that supported uEFI 2.3.1 were Touch Machines (Surface Pro), and you just don't install Win7 on them, but over the past few months we have been seeing more and more Secure Boot devices where the OEM explicitly says that they support Windows 7 (HP? :)). Can you upgrade to Windows 8.x? Can you change the firmware on these machines to CSM mode? Or.. File a bug with Microsoft support to fix the SCCM task sequencing engine? If anyone else has any insights on this, please let me know... -k From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Tuesday, May 20, 2014 8:04 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Apply OS Image step in TS fails The SMSTS.log file shows the following: Failed to save environment to D:\_SMSTaskSequence\TSEnv.dat Failed to save the current environment block. Permissionson the requested may be configured incorrectly. Access is denied. (Error: 80070005; Source: Windows) Failed to persist execution state. Error 0x(80070005) Failed to save execution state and environment to local hard disk. It appears the .WIM file is being applied to D:\, but I will need to confirm when I return to the office tomorrow. Yes, Network Access Account is good. If I attempt to deploy the same sequence using a Windows 7 installer package the image deploys just fine. My captured .WIM is 8.5 GB in size. Not sure if that would have anything to do with it? Brian ________________________________ Subject: Re: [MDT-OSD] Apply OS Image step in TS fails From: [email protected]<mailto:[email protected]> Date: Tue, 20 May 2014 19:49:50 -0700 To: [email protected]<mailto:[email protected]> What does the SMSTS.LOG says? Is the wim getting applied to the correct drive? Is the network account configured on you server? Some things I would check. Cesar A. Meaning is NOT in words, but inside people! Dr. Myles Munroe My iPad takes half the blame for misspells. On May 20, 2014, at 5:09 PM, Brian McDonald <[email protected]<mailto:[email protected]>> wrote: I'm banging my head against this one all day now. In need of some help/suggestions here. I have created a ref Win7 image using MDT 2013. Build/Capture process works flawlessly and I'm following best practices. I take my .WIM file and setup an MDT/SCCM integrated TS in my CM12 R2 CU1 environment. When I deploy my TS the deployment fails at the Apply OS Image step. It downloads the .WIM file then seems to run for 10-15 minutes before failing. Here are the errors in the SMSTS.log that are getting me no where real fast: Failed to save environment to D:\_SMSTaskSequence\TSEnv.dat Failed to save the current environment block. Permissionson the requested may be configured incorrectly. Access is denied. (Error: 80070005; Source: Windows) Failed to persist execution state. Error 0x(80070005) Failed to save execution state and environment to local hard disk. I have attempted re-creating my .WIM file (which took several hours as I am patching the image with a local WSUS instance as well as installing .NET framework, Windows Installer and various versions of Visual C++ in the image. Anyone might be aware of what could be causing this issue? Is there something wrong with my image? Why would I be getting a permissions issue when applying the OS? Makes no sense...or does it? Thanks! Brian
