scratch space in boot image

Question

_{Friday, May 23, 2014 7:54 AM}

What is scratch space in boot image?

What impact it will have if we increase the space of it in OS deployment. 

Is the error code  0x8007000E , have any connection with this.becuase for this type of issue comes with machine having agent status as YES and in  this case we need to delete the asset and readd. So increasing the space will resolve the issue?

Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

All replies (2)

_{Friday, May 23, 2014 8:02 AM ✅Answered}

Hi,

Johan explains it here: http://www.deploymentresearch.com/Research/tabid/62/EntryId/159/WinPE-5-0-scratch-space-in-MDT-2013-and-ConfigMgr-2012-R2.aspx

Regards,
Jörgen

-- My System Center blog ccmexec.com -- Twitter @ccmexec

_{Friday, May 23, 2014 12:33 PM ✅Answered}

No, it's not related to 0x8007000E and increasing the scratch space (which you can't do anymore in WinPE 5.0 as Johan explains in his post anyway) wouldn't help.

0x8007000E is caused because there is a hard limit on the "size" of a task sequence. The size is not measured in number of tasks though, it's measured in the memory (RAM) overhead required by the TS and includes things like the number of tasks, the size of the tasks (tasks are not all the same size), the complexity of the task sequence (things like conditions, groups, values), the number of policies applied to the client (and of course in turn their size), and the size of the values stored in task sequence variables.

The hard limit in 2012 R2 is 32MB although I haven't heard of anyone hitting this. In 2012 SP1 and RTM it was 10MB.

Jason | http://blog.configmgrftw.com