> 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/task-sequences/task-sequence-templates/ubuntu-desktop-via-iso.md).

# Ubuntu Desktop via ISO

{% hint style="info" %}
This is only supported in DeployR Enterprise.
{% endhint %}

The **Ubuntu Desktop via ISO** template installs Ubuntu Desktop from an ISO file stored as a DeployR content item. It contains a single step, [Install Ubuntu Desktop from ISO](/deployr/reference/step-definitions/install-ubuntu-desktop-from-iso.md).

After creating a task sequence from this template, edit the step and select two content items: the Ubuntu Desktop ISO, and a second content item with the `vmlinuz` and `initrd` files from the ISO's `casper` folder. The ISO content item must allow anonymous read access. You can also change the storage layout (default `lvm`), the user account to create (default `ubuntu`), and the optional LUKS passphrase.

The whole ISO is downloaded into a RAMdisk, so devices need plenty of memory; 12-16 GB is recommended. For devices with less memory, use the [Ubuntu Desktop via NFS](/deployr/task-sequences/task-sequence-templates/ubuntu-desktop-via-nfs.md) template.

Like the other Linux templates, this task sequence must run from a [Linux boot image](/deployr/deployment-methods/generate-linux-boot-images.md). It does not work from Windows PE.


---

# 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/task-sequences/task-sequence-templates/ubuntu-desktop-via-iso.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.