> 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/getting-started/creating-a-content-item/driver-packs/driver-packs-node.md).

# Driver packs Node

This node can be found inside of the Deployments blade, under DeployR.

<figure><img src="/files/NfIkgPn83X1cJlVQplbE" alt=""><figcaption></figcaption></figure>

To use this feature, simply search for a specific device for which drivers are needed in your environment, click the "Select" toggle, then an import button will magically appear in the upper left section of the frame, that can be pressed to start the process.

This example will show searching for an HP ZBook Studio G10, then importing the desired pack.  Using the search key words studio G10, a list of options appears:

<figure><img src="/files/WneOnT06gDJTJCzgi5HZ" alt=""><figcaption></figcaption></figure>

Using the sort feature on the OS name assists in finding the desired pack.  Note that duplicate do appear, which is causes especially on HPs that have additional meta data, this is being looked into, but for now, select one of the packs needed, then click Import:

<figure><img src="/files/REE83ht9TBENxtIYCysf" alt=""><figcaption></figcaption></figure>

A confirmation prompt will appear with overview of how many packs will be imported, in this example, just 1:

<figure><img src="/files/cDSu4FVvaecYbOTPoYQp" alt=""><figcaption></figcaption></figure>

Once OK is clicked, a message will slide in from the buttom right.

<figure><img src="/files/SbcdYCWzmFVJEldz0le7" alt=""><figcaption></figcaption></figure>

To monitor the process, logs are generated on the DeployR server in the DeployR content log folder, prefixed with the name "ImportOEMDriverPack-" and suffixed with a random GUID.  Opening the log will show the status of downloading, extracting generating the content item and uploading into DeployR:

<figure><img src="/files/F7SrYrWCjeVvb9JoXc6a" alt=""><figcaption></figcaption></figure>

It will now show in the Content items area:

<figure><img src="/files/b7jo2afN3WwN6LkzQGaR" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/pkvgFdztHBEcW9KvaHx7" alt=""><figcaption></figcaption></figure>

### Updates to Driver Pack Catalog

The Catalog is refreshed several times a day, there might not be any changes, but there are processes that scan the OEMs several times a day looking for changes, if there are, then the catalog is updated to reflect the addtional driver packs released.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/deployr/getting-started/creating-a-content-item/driver-packs/driver-packs-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.