# OSDCloud VM

{% hint style="warning" %}
**This page is under construction and the update hasn't even been released, so there is nothing you can do yet.  Be patient**
{% endhint %}

Let's have an intimate conversation about Hyper-V and OSDCloud.  For starters, I do almost all of my testing in Hyper-V on my Workstation, and I've been creating Virtual Machines hundreds of times ... all of that wasted time.  So how about automating this process for OSDCloud

## Admin Rights

Let's start with the obvious, you will need Admin Rights.  You won't even see the **`New-OSDCloudVM`** function without it.  Got it?

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FevieQvFOjIg8rLJ0jqIt%2Fimage.png?alt=media&#x26;token=721561ce-87de-42d1-9d59-0348e2039408" alt=""><figcaption></figcaption></figure>

## Hyper-V

Get your Hyper-V in working order.  This is a new function, and I don't have all the checks in place so expect things to go sour if you haven't at least created a Virtual Machine

## Workspace

Your OSDCloud Workspace should be in good order as well.  You can easily check this with **`Get-OSDCloudWorkspace`**.  What is important to know is that OSDCloud VM uses the OSDCloud\_NoPrompt.iso to boot.

If you need to change your OSDCloud Workspace, use the **`Set-OSDCloudWorkspace`** function

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FDbWcA4m7aD2xqcmNB31l%2Fimage.png?alt=media&#x26;token=c54477d6-0068-4d18-ae09-6f1a90853af9" alt=""><figcaption></figcaption></figure>