> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/customization/extra-files.md).
# Extra Files
This content item contains additional files that are included in the WinPE boot media during generation. When looking at the WinPE boot media generation log, it will show the referenced content item:
Near the end of the process, the log shows the files being copied recursively into the file structure:
The copy is recursive, preserving the content item's folder structure. For example, if the content item has the following structure, the files are copied to the same locations in the boot media:
Content Item:
\preinit.ps1\
\postinit.ps1\
\postauth.ps1\
\Windows\System32\wmiexplorer.exe\
\Windows\System32\winpe.jpg
After the boot image starts, the files are available at their respective paths in WinPE, as shown below:\
X:\preinit.ps1\
X:\postinit.ps1\
X:\postauth.ps1\
X:\Windows\System32\wmiexplorer.exe\
X:\Windows\System32\winpe.jpg
### Related Topics
* [Brand WinPE Background](/deployr/customization/brand-winpe-background.md)
* [Preinit, Postinit, Postauth ps1](/deployr/customization/preinit-postinit-postauth-ps1.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/deployr/customization/extra-files.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
