# Enable-OSDCloudODT

{% hint style="danger" %}
This functionality will be removed in the next few weeks.  Let me know if you are using this so I can detail a workaround
{% endhint %}

{% hint style="danger" %}
I would consider this Experimental and I am unsure of the future of this function.  It will more than likely change, so consider this a Sandbox for now
{% endhint %}

This is a new function to add Office M365 and install it in the Specialize phase of Windows Setup.  I had high hopes for this process, but in my testing, there was less than 1 minute difference in installing Office in Specialize versus pulling from an Intune (Office CDN).  I'm sure one of you will look into this further, so this is for now an OSDCloud Opt-In

## Do It

This process should be done before **`Edit-OSDCloud.winpe`**, although it really doesn't matter, but remember after adding this, you need to update your WinPE to see the magic

```
Enable-OSDCloudODT -Verbose
```

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MXmMiCkP0hwAnz4Y7Iq%2F-MXmOCtPiP9nVWOsFy-p%2Fimage.png?alt=media\&token=9ceb3da8-f85a-4af0-b09c-7fc4738d040c)

There is really nothing to it.  As you can see in the Verbose output, it will download the latest Microsoft ODT and expand it into subdirectories

## The Directory Structure

This is probably the most important process to understand, and the step that will probably be messed up the most on your end if you really don't understand.  For you visual people, hopefully this will help you understand, but the key is that the ODT directory sits in the ROOT of your OSDCloud Workspace

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MXmMiCkP0hwAnz4Y7Iq%2F-MXmPknUbE3kINykQapS%2Fimage.png?alt=media\&token=e827ef97-7ba5-4e51-96d9-f9044a0ef148)

### Product

In the ODT directory are two subdirectories that represent the M365 / Office Product.  You can see all the Products that can be used, but its important that your directory represent the Product for better organization.  If you have no plans to work with ProPlus2019Volume, delete it

{% embed url="<https://docs.microsoft.com/en-us/office365/troubleshoot/installation/product-ids-supported-office-deployment-click-to-run>" %}

### Channel

The next subdirectory represents the M365 / Office Channel

{% hint style="success" %}
Delete the Channel directories that you don't need!
{% endhint %}

{% embed url="<https://docs.microsoft.com/en-us/deployoffice/update-channels-changes>" %}

&#x20; It really doesn't matter what you name them, as long as the Channels are separated.  In each Channel directory there should be a copy of setup.exe which was expanded when you ran **`Enable-OSDCloudODT`**.  You can always repeat that function to add  the latest ODT setup.exe as needed, understanding that the XML files will be overwritten

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MXmMiCkP0hwAnz4Y7Iq%2F-MXmQtI9u5SaFxZoeRWh%2Fimage.png?alt=media\&token=6d5d30a1-b888-4960-8feb-02ac6d0ef3ad)

### XML Files

In each of the Channel directories, in addition to the setup.exe, is an Office Configuration File.  Don't edit these as they can be overwritten.  Create your own using this as an example.  The biggest thing is for the Language ID to be set to "MatchOS", but whatever

```
<Configuration ID="002634c3-bedd-416a-82ea-764d564ec07a">
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="MatchOS" />
      <ExcludeApp ID="Groove" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="0" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Updates Enabled="TRUE" />
  <RemoveMSI />
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>
```

## USB Considerations

{% hint style="warning" %}
This isn't entirely working as planned due to the inclusion of the XML files in WinPE.  This should be considered as Concept Under Development for the time being
{% endhint %}

If you are deploying OSDCloud from a USB, you can download the content in advance.  Assuming you have copied the ODT directory to \<USBDrive>:\OSDCloud\ODT then do the following

Type cmd in the Windows Explorer Address Bar and press Enter

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MXmMiCkP0hwAnz4Y7Iq%2F-MXmSYZ2A69-pDsY-SRb%2Fimage.png?alt=media\&token=c91e494d-bb80-4475-9331-8618d4225718)

Now use setup.exe to /download the content specified by the Office Configuration XML.  This will download your Office payload from the CDN

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MXmMiCkP0hwAnz4Y7Iq%2F-MXmT4Lts4X0P5p4cwAf%2Fimage.png?alt=media\&token=24d48150-3ff6-4f91-8e5b-16fbe1be7195)

## Edit-OSDCloud.usb

When you run this command, the necessary files will be added to WinPE

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MVSV22dcsjKDdOxDA6n%2F-MXmTEtEnAu9nJ3nsHWl%2F-MXmh7Gp4l5rrUpbdbo0%2Fimage.png?alt=media\&token=0a4b70d6-13bf-4daf-be57-82353a03e5d6)

## Walkthrough

How it works has been added to the Walkthrough

{% content-ref url="deploy" %}
[deploy](https://www.osdcloud.com/osdcloud-v1/recycle-bin/deploy)
{% endcontent-ref %}