> 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/recycle-bin/guides/osdcloud-wim.md).

# OSDCloud WIM

April 15, 2021

{% hint style="warning" %}
Make sure you are running OSD Module 21.4.15.4 or newer.  There was a bug in the previous version that will make this fail
{% endhint %}

So you want to use your custom WIM wth OSDCloud?  This is how you do it.  This is a LOCAL wim file for now, but this will be expanded to download a wim from a URL in the near future

## OSDCloud OS

In your OSDCloud Workspace, you have an OS directory.  Put your WIM in here.  In my case, I downloaded the Windows Server 2022 Insider Preview ISO and simply expanded it with 7-Zip.  Don't over-complicate this and make it difficult.  Give it a path so you know what it is

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYLy78ouP6lWvLCpNvc%2Fimage.png?alt=media\&token=24b35e82-91d8-4689-9345-47dafbbeb24b)

{% embed url="<https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewserver>" %}

### USB Considerations

If you are using an OSDCloud USB, then the process is similar, put it in the OSDcloud\OS directory of your OSDCloud partition.  Again, don't over-complicate this

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYLzHhR3DQmivFVTW0q%2Fimage.png?alt=media\&token=b3c7a2cc-3b82-444f-80bd-ceb087a674f7)

## The Path

It is important for you to remember this about the Path.  For OSDCloud to find it, it must be in a similar path (which is recursed)

```
<PSDrive:>\OSDCloud\OS\* -Recurse
```

That said, if my OSDCloud Workspace is at D:\OSDCloud, and I am in a Virtual Machine on the same computer, I can simply Map a Network Drive using DaRT if you have it installed, or a command line.  Make sure you don't map to an OS Drive Letter (C: R: S: X:) and you'll be fine.  I use O: for OSDCloud personally

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM-9xxvU5V5JcPNyI_%2Fimage.png?alt=media\&token=66ae3f18-9005-4db7-b523-e62a51616567)

### USB Considerations

None.  If you are on a Physical computer and you put it in the OSDCloud OS path, then you're fine

## Start-OSDCloudWim

I always recommend installing the newest OSD Module first, then get cracking.  You will be presented with a Menu to select your Wim and Image Index

```
Install-Module OSD -Force
Import-Module OSD -Force

#Set the Display Resolution to whatever you want if you are in a VM
Set-DisRes 1600

Start-OSDCloudWim
```

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM2XTqZzi5EMWPM044%2Fimage.png?alt=media\&token=762961dd-c9de-4cda-99bb-db4678c153d7)

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM35evlq8TFeDoFx_p%2Fimage.png?alt=media\&token=480a01ee-2901-4238-b70a-66e9b9e6ad2e)

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM3nNryrqLXcr93k0X%2Fimage.png?alt=media\&token=bde8db09-806f-4d33-8d04-cf22a4dcdb7e)

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM3p8S1z1k8dNJMaYh%2Fimage.png?alt=media\&token=395613b4-fd54-4046-bc11-da7cc5f000ff)

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM3qasmLhGaGd7KxuF%2Fimage.png?alt=media\&token=ede8dfee-4b39-4d66-9278-f0e36fa1c524)

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM3sM1ORmVqhK5fg5N%2Fimage.png?alt=media\&token=586b0b69-236a-4d9b-b22f-3dd5ece7f42a)

### Parameters

The ones you know and love are all there

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MYLxC1Kd9VjEBevex9H%2F-MYM0hftUDAte8bnfaq0%2Fimage.png?alt=media\&token=c154bfbf-a3bb-4fba-a907-21de970253f0)


---

# 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/recycle-bin/guides/osdcloud-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.