I was having a similar problem late last year and found that a condition set in the format partition step was preventing it from being run. Because a format and partition was never being executed it was trying to access the bit locker enabled disk and couldn't for the purposes of downloading files from the DP. I'm not sure if this is the same problem you're experiencing?
I removed that variable and then the format and partition step would run. Having said all this, I recently re-created all my Task Sequences following an update to MDT 2013 Update 2 and the format and partition step no longer has that condition. I'm not sure if you have MDT integrated Task Sequences but take a looking at the variables against the that step as a starting point. Hope this helps. Cheers Damon From: [email protected] [mailto:[email protected]] On Behalf Of Ortega, Clint Sent: Monday, 4 April 2016 9:15 AM To: [email protected] Subject: [mssms] RE: Error 80070070 when kicking off TS This would be happening in both instances, bare metal and refresh. Thanks, Clint Ortega Systems Administrator II From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Friday, April 1, 2016 5:32 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Error 80070070 when kicking off TS Just to confirm, Is that happening for bare metal scenario or refresh scenario? Cheers Damon From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ortega, Clint Sent: Saturday, 2 April 2016 7:26 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Error 80070070 when kicking off TS Good afternoon all, We are experiencing an issue where devices getting reimaged are receiving the following error. This error occurs after we select the Task Sequence, but before the Task Sequence kicks off. We can clear past this error by running a diskpart and cleaning the disk before we proceed with selecting a TS. Has anyone found the root cause of this issue or know how to automate a fix by chance? Google has not turned up much. We have two boot images, with several task sequences. The trigger seems to be that a TS requires a different boot image instead of our default boot image. We run into this issue when we try to load this boot image. We use a Bitlocker encryption that creates a 300MB partition, and it appears this is where the image tries to load. And it can't load here because in an area that is now too small. Should we run a pre-execution command to run a diskpart automatically? Any thoughts on how anybody else has resolved this issue? If you want to reference the following article, it explains the solution we are having, but it doesn't give a good solution. I also attached our smts.log if further info is needed. Please advise! http://social.technet.microsoft.com/wiki/contents/articles/31542.bitlocker-not-able-to-stage-boot-image-on-bitlocker-partition.aspx [cid:[email protected]] Thanks, Clint Ortega Systems Administrator II CHRISTUS Health Information Management 469-282-0295 [email protected]<mailto:[email protected]> The two basic principles of Windows system administration: * For minor problems, reboot * For major problems, reinstall CONFIDENTIALITY NOTICE: Confidential information, such as identifiable patient health information or business information, is subject to protection under state and federal law. If you are not the intended recipient of this message, you may not disclose, print, copy or disseminate this information. If you have received this in error, please reply and notify the sender (only) and delete the message. Unauthorized interception of this e-mail is a violation of federal criminal law. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. CONFIDENTIALITY NOTICE: Confidential information, such as identifiable patient health information or business information, is subject to protection under state and federal law. If you are not the intended recipient of this message, you may not disclose, print, copy or disseminate this information. If you have received this in error, please reply and notify the sender (only) and delete the message. Unauthorized interception of this e-mail is a violation of federal criminal law. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
