☁️
OSDCloud.com
OSDeploy.comTwitter
  • About
  • Contributors
    • Damien Van Robaeys | MVP
    • Ákos Bakos
    • David Segura | MVP
    • Gary Blok
    • Jérôme Bezet-Torres | MVP
  • OSDCloud
    • Local Setup
      • OSDCloud Template
        • Build Process
        • Logs
        • Named Templates
        • WinRE WiFi
        • Public Content
        • Languages
        • Cumulative Updates
        • ISO Boot Media
        • Universal WinPE
      • OSDCloud Workspace
        • Get-OSDCloudWorkspace
        • Set-OSDCloudWorkspace
        • New-OSDCloudWorkspace
          • Restore from ISO
          • Restore from ISO URL
          • Restore from USB
        • Update-OSDCloudWorkspace
        • Configuration Files
      • OSDCloud WinPE
        • Default Wallpaper
        • Wallpaper
        • Drivers
        • PSModule
        • Startup
      • OSDCloud ISO
      • OSDCloud USB
        • New-OSDCloudUSB
        • Update-OSDCloudUSB
        • USB Drives
        • Secure USB Drives
      • 🚧OSDCloud VM
        • Get-OSDCloudVMDefaults
        • Get-OSDCloudVMSettings
        • Set-OSDCloudVMSettings
        • Reset-OSDCloudVMSettings
        • New-OSDCloudVM
    • Deployment
      • WinPE
        • Start-OSDCloud
          • OS Parameters
          • ZTI
        • Start-OSDCloudGUI
          • Parameters
          • Defaults
          • Global Variable
          • Customize
        • Start-OSDCloud Wrapping
      • First Boot
      • OOBE
      • Windows
  • Sandbox
    • OSDCloud
      • sandbox.osdcloud.com
      • WinPE Usage
      • OOBE Usage
      • Functions
    • OSDCloud Azure
      • az.osdcloud.com
    • WinPE Downloads
  • OSDCloud Automate
    • 🆕Basic Configuration
    • 🆕OSDCloudGUI Defaults
    • 🆕Autopilot
    • 🆕Provisioning
      • 🆕Windows Configuration Designer
      • 🆕MSI Application PPKG
      • 🆕Bulk Enroll PPKG
      • 🆕PowerShell Script PPKG
    • 🚧Scripts
  • OSDCloud Azure
    • Azure Setup
      • Azure Portal
        • Storage Accounts
        • Storage Containers
          • BootImage
          • DriverPack
        • Storage Access Control (IAM)
      • Infrastructure As Code
        • Prerequisites
        • Technicien
        • Workspace
        • Bicep
        • Terraform
        • Configure Azure
    • Deployment
      • Testing
      • OSDCloudRE Azure
    • Deep Dive
      • Cloud Functions and Scripts
      • Connect Azure in WinPE
      • Azure Tags
      • Log Files
  • Offline Deployment
    • ISO: Adding a WIM
  • Integration
    • ADK: Use the OSDCloud Boot.wim
    • MDT: Use the OSDCloud Boot.wim
    • MDT: Add OSDCloud WinPE Drivers
    • MDT: Use OSDCloud DriverPacks in a Task Sequence
    • OSDCloud IPU
      • Windows In-place Upgrades
      • Windows Media Download
  • Archive
    • 💡Tips
      • 🆕Media Cleanup
      • Firmware Update
      • Quick Setup
    • 🌎Community
      • OSDCloud: The ZTI Way
      • OSDCloud - Image devices without need of infrastructure
      • Trying out Windows 10 Deployment with OSDCloud
      • Deploying Windows 10 to bare metal devices with just WinPE & internet
    • 💔Under Review
      • ISO
      • WIM
    • 🪦Recycle Bin
      • Release Notes
      • Enable-OSDCloudODT
      • Deploy
        • OOBE Phase
      • Guides
        • OSDCloud WIM
        • Custom OSDCloud
        • AutoPilot
          • AutoPilot Configuration File
          • AutoPilot in Audit Mode
          • AutoPilot in OOBE
        • WiFi
      • OOBE
        • Start-OOBE.settings
        • Start-OOBE.wifi
        • Start-OOBE.autopilot
      • Concepts
        • K.I.S.S.
        • OSD Disks Logically
        • Office365 Specialize
        • Specialize DriverPacks
        • Model Reference Image
        • MDT OSDCloud DriverPacks
        • MDT DriverPacks
      • Blob SAS URL
      • Storage Containers (Public)
Powered by GitBook
On this page
  • Requirements
  • [Default] fromWorkspace
  • fromIsoFile
  • fromIsoUrl
  • USB Content
  • Disk Management

Was this helpful?

Export as PDF
  1. OSDCloud
  2. Local Setup
  3. OSDCloud USB

New-OSDCloudUSB

OSD 23.5.22.1+ Updated May 22, 2023

PreviousOSDCloud USBNextUpdate-OSDCloudUSB

Last updated 2 years ago

Was this helpful?

This function requires elevated Admin Rights

There are two reasons for creating an OSDCloudUSB. The first reason is to simply boot to WinPE and let everything download from the Internet. The second reason is to support OSDCloud Offline, which works without any internet connection at all

To create an OSDCloud USB, use the New-OSDCloudUSB OSD function. This OSD Function is used for both OSDCloud WinPE and OSDCloud Offline

Requirements

[Default] fromWorkspace

To get started, open PowerShell with Admin rights. Simply enter New-OSDCloudUSBto prepare a new or used USB Drive

You will be presented with a table of the USB Drives that are present on your system, regardless of whether you have 1 or 5. Simply enter the DiskNumber to make a selection

After selecting a DiskNumber, you will be prompted to Confirm the selection as this is a destructive process. Once you Confirm, the USB Drive will be Cleared, Initialized, Partitioned, and Formatted. When the USB Volumes are ready, your OSDCloud Media will be copied to the Boot partition. The whole process should take between 1-2 minutes to complete

fromIsoFile

If you have an OSDCloud ISO, you can use this to create an OSDCloud USB using the -fromIsoFile parameter

fromIsoUrl

If you have an ISO saved on the Internet, you may be able to use the -fromIsoUrl parameter

This is not guaranteed to work in all situations due to firewall and proxy configuration

USB Content

When you create a new OSDCloud USB, only the WinPE partition will contain files. If you do not plan on using OSDCloud Offline, you can rename the OSDCloud partition and use it for something else

Disk Management

As you can see in Disk Management, the USB Drive will contain two partitions. The first partition will be the OSDCloud NTFS partition, with the second being the 2GB FAT32 Partition. Other guides may tell you to create the FAT32 partition first, but they are wrong, and I am right. For one reason, FAT32 gets corrupted all the time. Its easier to destroy and recreate at the end of the drive without messing with the NTFS partition. Secondly, you are free to shrink and extend this smaller partition. If the partitions were reversed, you would not be able to extend the start point of the second partition without losing all the NTFS data

OSD/New-OSDCloudUSB.md at master · OSDeploy/OSDGitHub
Online Help
Logo