The Pre-Deployment section is where you prepare and manage the core components required for building and deploying devices with OneDeploy. These settings define where deployment files are stored, how devices boot into the deployment environment, and which versions of Windows PE are available and supported.
Most organisations will configure this area during initial onboarding and only return to it when introducing new hardware, testing newer deployment environments, or updating Windows ADK versions.
This section is divided into four main areas, each covering a different part of the deployment preparation process. Each section is documented separately. A summary is provided below:
Deployment Sources
Deployment Sources are the file shares that store all of the content required to perform a build, such as operating systems, drivers, software packages, and scripts.
By default, OneDeploy is configured with a single Master Deployment Source, which acts as the primary location for all deployment content. For many environments, this single source is sufficient.
If required, you can also create additional Downstream Deployment Sources. These are typically used in larger or distributed environments to replicate content closer to deployment locations, reducing network traffic and improving deployment performance.
Boot Profiles
A Boot Profile represents a specific version of the Windows PE (Preinstallation Environment) used when devices start a deployment.
During onboarding, OneDeploy creates a default Boot Profile automatically. This default profile is suitable for most standard deployment scenarios and does not usually need to be modified.
Additional Boot Profiles can be created when you want to:
- Test updated or alternative Windows PE versions
- Validate new or updated Windows PE drivers
- Support different hardware requirements without impacting existing deployments
Windows PE
The Windows PE section lists the available Windows PE environments for each supported Processor Architecture. These environments are extracted from the Windows ADK and form the foundation of the boot environment used during deployments.
From this area, you can:
- View the available Windows PE versions
- Control which drivers are integrated into Windows PE
- Recompile Windows PE after adding or updating Windows PE drivers in the library
This ensures that deployed devices have the correct Driver support when booting into the deployment environment.
ADK Versions
The ADK Versions section shows the Windows ADK versions that OneDeploy has detected and used to populate the Windows PE operating system list.
If you install or update the Windows ADK on your system, this area allows you to:
- Confirm which ADK versions are available
- Import newer Windows PE versions
- Ensure OneDeploy is using the correct ADK components for deployment
Keeping this list up to date helps ensure compatibility with newer hardware and operating system versions.
Common Questions
Do I need to change anything in Pre-Deployment after onboarding?
In most cases, no. The default configuration is sufficient unless you are testing newer Windows PE versions, or updating the Windows ADK.
When would I need multiple Deployment Sources?
Multiple Deployment Sources are typically used in larger or distributed environments where content replication and network efficiency are important.
Is it safe to create additional Boot Profiles?
Yes. Creating additional Boot Profiles allows you to test changes without affecting existing, production deployments.
Are there any licensing limits on how many Deployment Sources I can create?
No. You can create as many Deployment Sources as needed, and there are no licensing implications or additional costs associated with adding extra Deployment Sources. This allows you to scale your deployment infrastructure freely, for example by adding Downstream Deployment Sources in different locations.
Related Articles
- Deployment Sources
- Boot Profiles
- Windows PE
- ADK Versions