> For the complete documentation index, see [llms.txt](https://www.osdcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdcloud.com/osdcloud-v1/tips/using-osdcloud-with-a-custom-wim.md).

# Using OSDCloud with a Custom WIM

April 23. 2021 | OSD 21.4.23+

You can use a CustomImage with Start-OSDCloud by either specifying a URL, or placing the file on a USB or Network Share

## -ImageFileUrl

If you happen to have a URL for a WIM or an ESD, you can specify that using the **`-ImageFileUrl`** parameter.  Make sure you include **`-ImageIndex`**, otherwise it will default to 1

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MZ0zix7ToueWwCxDOsC%2F-MZ12p94JwzoegwZwye8%2Fimage.png?alt=media\&token=abca2b54-44f6-410a-adc9-02ea2d9be5c9)

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MZ0zix7ToueWwCxDOsC%2F-MZ145LSqQYsUI1tzU8v%2Fimage.png?alt=media\&token=6d04f531-e0af-4d1d-b278-e61ef2c8a9b4)

### Invoke-OSDCloud Variables

These are passed from **`Start-OSDCloud -ImageFileUrl`** to **`Invoke-OSDCloud`** for processing

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MZ0zix7ToueWwCxDOsC%2F-MZ136XUplec5SgzcmDo%2Fimage.png?alt=media\&token=edafc6b9-2060-4bd9-9db1-8dd2fa88b5b9)

## -FindImageFile

If you have a Custom WIM or an ESD file, simply place it in a the following path (subdirectories are good) on a USB Drive or Network Share

```
<DriveLetter>:\OSDCloud\OS\*
```

OSDCloud will scan the above path on available drives for image files, as long as they are WIM or ESD Files

{% hint style="warning" %}
Only Drive Letters D-Z  except X: because that's WinPE (C: isn't checked because it will be wiped)
{% endhint %}

In my example below, I have mapped a Network Drive which contains the OSDCloud OS Path and 4 OS Images have been found.  After selecting an ImageFile, I will be prompted to select an ImageIndex

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYpIhdrGB_TF9Yt_v24%2F-MYpxddl_gOOYk6s2k2w%2Fimage.png?alt=media\&token=4615d813-aa91-4017-8778-a78c1ff5308b)

### Invoke-OSDCloud Variables

My example above will pass these variables to Invoke-OSDCloud for processing

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYpxpWF4UIMUEWaxxt2%2F-MYpyO_xUk5mmAGNZjcx%2Fimage.png?alt=media\&token=72d2a55a-61fa-41a8-8878-190689723a3a)


---

# 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://www.osdcloud.com/osdcloud-v1/tips/using-osdcloud-with-a-custom-wim.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.