OneDeploy can perform deployments using two types of Deployment Source:
- A Windows file share for LAN-based deployments
- A USB Deployment Source for USB-based deployments
Both methods use the same build definitions and deployment logic. Depending on how builds are authored, OneDeploy can operate without internet access, and in some cases without any network connectivity at all.
LAN-Based Deployment Sources (File Share)
A LAN-based Deployment Source is the default and recommended method for most environments.
It consists of a Deployment Source hosted on a Windows file share, accessed over the local network during deployment.
LAN-based Deployment Sources have the following characteristics:
- Suitable for performing large numbers of deployments across a local network
- Can be replicated to additional file shares to support multiple deployment locations
- Act as the master source for creating USB Deployment Sources
- Can be kept up to date using the OneDeploy Web UI and OneDeploy CLI
- Do not require external media at the endpoint, as all content is delivered over the LAN
This approach is best suited to environments with reliable local network connectivity. Internet access for devices being deployed is not essential.
USB-Based Deployment Sources
In some deployment scenarios, a USB-based Deployment Source may be more appropriate than a LAN-based file share.
USB-based deployment is commonly used where portability, offline operation, or restricted networks are required.
USB Deployment Sources have the following characteristics:
- Can be used as a portable Deployment Source by engineers
- Can support deployments without internet access
- Can enable self-service or remote deployments without on-site IT staff
- Must be kept synchronised, otherwise USB media can become out of date
Note: A LAN-based Deployment Source is still required as the authoritative source for creating and updating USB Deployment Sources.
Two Types of OneDeploy USB Deployment
OneDeploy supports two distinct USB deployment methods, each serving a different purpose.
1. USB Boot Media (WinPE Boot Only)
The first type of USB stick is used only to perform the initial boot into the pre-deployment environment (Windows PE).
This method is typically used when:
- PXE booting is not available
- Network Boot infrastructure (DHCP/TFTP) cannot be configured
In this model:
- The USB stick boots the device into Windows PE
- The deployment then continues using a LAN-based Deployment Source
- The USB is not used to host build content
This approach replaces PXE booting but still relies on network access to the Deployment Source.
2. Full USB Deployment Source (Fully Offline Deployment)
The second type of USB stick contains a fully portable Deployment Source.
This USB includes everything required to perform a deployment, such as:
- Operating system installation media
- Software Packages
- Drivers
- Build configuration and metadata
When using a Full USB Deployment Source:
- The target computer does not need access to a LAN
- The target computer does not need internet access
- The deployment runs entirely from the USB device
The only external resource required during deployment is the USB stick itself.
This method is suitable for fully isolated environments, remote field work, or situations where no network connectivity is available or permitted.
Offline Deployment Considerations
OneDeploy can perform deployments without internet access when all required content is available locally, either from a LAN-based or USB-based Deployment Source.
When planning offline deployments, ensure that:
- Application installers do not attempt to download components during installation
- All required drivers, packages, and OS media are included in the Deployment Source
- Build steps do not depend on external network services
Full USB deployment takes this one step further by removing the requirement for any local network connectivity, not just internet access.
Keeping USB Deployment Sources Up to Date
USB Deployment Sources can become outdated unless they are regularly refreshed.
All files required to build USB media are stored within the LAN-based Deployment Source, which acts as the master copy.
A LAN-based Deployment Source may be used solely for:
- Staging build content
- Maintaining configuration
- Creating and updating USB sticks
In this scenario, no DHCP or TFTP configuration is required if PXE booting is not being used.
Common Questions
Do I need internet access to perform a OneDeploy deployment?
No. OneDeploy can deploy entirely from LAN or USB without internet access, provided all build components are available locally.
When should I use a Full USB Deployment Source?
Use Full USB deployment when no network connectivity is available or permitted during deployment.
Can USB deployment replace a LAN Deployment Source permanently?
USB can be used for standalone deployments, but most environments still maintain a LAN-based Deployment Source as the master source for updates and synchronisation.
Does a domain-based build require connectivity to a domain controller?
Yes. If a build includes Domain Join operations, the target device must be able to reach a domain controller at the point those actions are performed.
This typically means:
- Network connectivity is required during the relevant stage of deployment
- Fully offline (Full USB) deployments are not suitable for domain-joined builds unless domain connectivity is restored before the join occurs
For domain-based builds, ensure network availability is planned accordingly.
Is network or internet connectivity required at the end of a build (for example, for Autopilot)?
It depends on the post-deployment requirements.
Some scenarios, such as Autopilot enrolment, cloud-based management, or policy/application delivery, require:
- Network connectivity
- Often internet access
- In some cases, access to specific cloud services
OneDeploy can complete the operating system deployment without internet access, but any post-deployment processes that rely on external services will require connectivity once the build has completed.
When planning offline or USB-based deployments, consider how and when the device will regain connectivity after deployment. Consider centrally managed Wi-Fi profiles if possible. The Autopilot/OOBE will guide the user through connecting to the internet if no connection is available.
Related Articles
- Deployment Sources
- Windows PE Overview
- USB Boot Media
- Offline Deployment Planning
- Getting Started Guide