> 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/ipxe-ws/4.0/configuration/updating-the-scripts-folder.md).

# Updating the Scripts Folder

The iPXE Web Service installer includes an initial set of scripts in the **Templates** folder inside the installation folder. The first time the iPXE Web Service service starts, it copies them to the **Scripts** folder inside the installation folder (by default **C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts**). The service only does this when the **Scripts** folder has no subfolders, so it never overwrites scripts that you have changed. The script settings in the configuration editor use paths relative to the installation folder, such as `Scripts\Boot\iPXEboot.ps1`. New and additional script examples may be available for download from the [2Pint GitHub repository](https://github.com/2pintsoftware/2Pint-iPXEAnywhere/tree/main).

1. Visit the [2Pint GitHub repository](https://github.com/2pintsoftware/2Pint-iPXEAnywhere/tree/main).
2. Click the **\<Code>** link at the top menu.\
   ![](https://content.gitbook.com/content/oPMTFuBb6yV8Wq1KUzxo/blobs/KGK19A4aHtGVDKeK970i/IPXEAW-GitHubRepoCodeLink.jpg)
3. The green Code button will appear, **select** it, and in the context menu, click **Download ZIP**.\
   ![](https://content.gitbook.com/content/oPMTFuBb6yV8Wq1KUzxo/blobs/HOUBG2jvnRlo1w5lTjxL/IPXEAW-GitHubRepoDownloadZIP.jpg)
4. Download the ZIP and extract the contents. The only folder needed is the "Scripts" folder.
5. Make a backup of your existing **Scripts** folder, then copy the extracted **Scripts** folder to the [iPXE Anywhere Web Service installation folder](/ipxe-ws/4.0/installation/ipxe-anywhere-web-service-install.md), so that the result is **C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts**. Restart the iPXE Anywhere Web Service service.\
   ![](https://content.gitbook.com/content/oPMTFuBb6yV8Wq1KUzxo/blobs/cF0qH9EzH5GRR8BfVuuA/IPXEAW-ScriptsFolderStructure.jpg)

## How the scripts run

The web service runs the scripts itself, using PowerShell 7.6, rather than starting a separate PowerShell process. Keep the following in mind when you write or update scripts:

* Scripts run with an execution policy of **Bypass**, so they do not need to be signed, and the server's execution policy does not block them.
* Scripts can import PowerShell modules, using `Import-Module` or module autoloading.
* Scripts written for Windows PowerShell 5.1 may need changes, because some Windows PowerShell commands and modules are not available in PowerShell 7.
* Scripts run as the service account (Local System).


---

# 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/ipxe-ws/4.0/configuration/updating-the-scripts-folder.md?ask=<question>&goal=<user_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.
