Any chance you manually captured an image that contains an _SMSTaskSequence 
folder?  (That would be bad.)

Also, does the task sequence fail right after that error?  Failure to save the 
environment isn’t fatal, at least up until the point of a needed reboot.

Thanks,
-Michael

From: [email protected] [mailto:[email protected]] On 
Behalf Of CESAR.ABREG0
Sent: Tuesday, May 20, 2014 9:00 PM
To: [email protected]
Subject: Re: [MDT-OSD] Apply OS Image step in TS fails

There were probably more error before this one, this error is very genetic.

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 8:04 PM, Brian McDonald 
<[email protected]<mailto:[email protected]>> wrote:
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

Reply via email to