Release Notes

21.8.10 August Update

There typically aren't any Release Notes for OSDCloud as they are bundled in with the OSD Module, but this release has quite a few changes, so it's important to get through them

OSDCloud Config Files

Autopilot Profiles are being relocated. Review the following link

In previous releases, the Autopilot Profiles were located in the following location

C:\ProgramData\OSDCloud\Autopilot\Profiles

While this made sense in the beginning, the addition of other configuration for AutopilotOOBE and OOBEDeploy makes it necessary to bundle files used for configuration into a proper parent directory

The next time you update your OSDCloud Template you will receive a Warning (and a short delay). This Warning will continue (and the delay will increase in the future) until you remove C:\ProgramData\OSDCloud\Autopilot manually

Remove these directories!

Template and Workspace Issues

You will be unable to create or update an OSDCloud Workspace until the Autopilot Profiles are moved in both your OSDCloud Template and your working OSDCloud Workspace

This change will impact the following commands

New-OSDCloud.workspace
Edit-OSDCloud.winpe

ODT Changes

I plan on phasing out the Office 365 installation during the Specialize phase in the next few weeks. Pleae contact me if you use this and I'll help you come up with a workaround. There are no changes ODT in this release

Edit-OSDCloud.winpe

I strongly recommend rebuilding your WinPE by rebuilding your OSDCloud Template and OSDCloud Workspace to ensure full compatibility with the new changes in WinPE

Drivers

In addition to the CloudDriver and DriverPath parameters, you now have the option to use the DriverHWID parameter to ensure that a driver for a specific Hardware ID is installed. All three Driver parameters are arrays, so you can add multiple options for each parameter

$Params = @{
CloudDriver = 'Dell','WiFi'
DriverHWID = 'PCI\VEN_8086&DEV_2526','PCI\VEN_8086&DEV_15BB'
DriverPath = 'D:\OSDCloud\Drivers\Chipset','D:\OSDCloud\Drivers\SATA'
}
Edit-OSDCloud.winpe

When using DriveHWID, the driver will be downloaded from Microsoft Update Catalog and added to WinPE. This feature has been present in the OSD Module for the last month, but has not been fully documented yet

Startup

There are several changes to the WinPE startup, so I hope you can keep up

StartOSDCloudGUI

This parameter will add Start-OSDCloudGUI to the Startnet.cmd

Edit-OSDCloud.winpe -StartOSDCloudGUI

Start-OSDCloudGUI will automatically minimize the Startnet.cmd window

StartOSDCloud

If you prefer to stick to the Command Line, then use the StartOSDCloud parameter. Unlike the Switch parameter of StartOSDCloudGUI, this is a String, meaning you need to provide your Start-OSDCloud switches for it to work properly

Edit-OSDCloud.winpe -StartOSDCloud '-OSBuild 1909 -OSEdition Pro -OSLanguage es-es -OSLicense Retail'

StartOSDPad

This parameter will allow you to use OSDPad to deploy using scripts on GitHub. I'd with I could say more now, but this is still being developed

StartScript

This parameter is simply a rename of WebPSScript, although its important to understand the position. This will add an entry to the Startnet.cmd after StartUpdate and before any StartOSDCloud or StartOSDCloudGUI lines. This will allow you to completely any pre-flight, although since this is in a separate PowerShell session, Variables cannot be carried outside of the WebPSScript. Be aware this doesn't work well with URL's with spaces (working on it)

Startnet

Finally, the Startnet parameter will add whatever you want to the Startnet.cmd file so if you want to tinker and play around, this is for you.

$Startnet = @'
start /wait PowerShell -NoL -C Install-Module OSD -Force -Verbose
start PowerShell -NoL -C Start-OSDCloudGUI
'@
Edit-OSDCloud.winpe -Startnet $Startnet

More information on these changes are included in the following link