> 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/content-management/driver-packs.md).
# Driver packs
To create a driver pack content item manually in the dashboard, first create the content item:
Next, create a driver pack version and specify the manufacturer and model of the devices that should use it:
Select a folder containing the driver files, then click **Upload All** to upload them to the DeployR server. DeployR combines all files into a single WIM file and extracts them before injecting the drivers on the target device.
{% hint style="info" %}
Note: The manufacturer and model strings are matched using either the exact values found in the firmware (SMBIOS) of the device, or simplified MakeAlias, ModelAlias, and/or SystemAlias values. Check the DeployR.log to see the specific values for a given device.
You can also create driver pack content items with PowerShell (see [Generate Driver Pack Content Items](/deployr/automation-and-powershell/scripting-for-deployr-server/automating-content-item-creation/generate-driver-pack-content-items.md)) or import them from the 2Pint catalog (see [Driver packs Node](/deployr/content-management/driver-packs/driver-packs-node.md)).
{% endhint %}
---
# 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/content-management/driver-packs.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.
