ADK Versions

The ADK Versions section shows which Windows ADK versions have been imported into your OneDeploy environment.

These ADK versions are used to provide the supporting tools and Windows PE components required for device deployment.

This screen is primarily relevant when you install a newer version of the Windows ADK and want to make that version available for use in OneDeploy.

What is this screen used for?

Most environments only require a single ADK version, configured during onboarding.

You would typically use this screen when:

• You install a newer version of the Windows ADK
• You want OneDeploy to recognise and import that version
• You want to make newer Windows PE components available for Boot Profiles

This helps avoid manually copying Windows PE files or ADK tools between file shares, as OneDeploy can manage the import process through the WebApp.

Viewing ADK Versions

To access this screen:

In the navigation pane, expand Pre-Deployment.  Click ADK Versions

The list shows all ADK versions currently available in your OneDeploy environment.

Each entry includes:

• The ADK version
• The version number

Adding a new ADK Version

If you install a newer version of the Windows ADK (for example, upgrading from one release to another), you can import it into OneDeploy.

To add a new version:

1. Install the updated Windows ADK on the machine being used for administration
2. In OneDeploy, go to Pre-Deployment → ADK Versions
3. Click Add

When you add an ADK version, OneDeploy will:

• Load the correct ADK utilities (such as DISM tools)
• Import the associated Windows PE components into the environment

Important: Adding a new ADK version does not automatically change any existing Boot Profiles

Using a new ADK version in Boot Profiles

After importing a newer ADK version, you can choose when to start using it.

For example, you may want to:

• Create a new Boot Profile for testing
• Upgrade an existing Boot Profile when ready

This allows you to introduce newer Windows PE versions safely without impacting production deployments immediately.

Add WinPE from ADK

The Add WinPE from ADK option is used to import an additional copy of Windows PE from an existing ADK version.

This is useful in scenarios where you may want multiple Windows PE environments based on the same ADK version.

For example:

• Maintaining separate WinPE configurations for testing
• Importing additional WinPE copies without reinstalling the ADK

How ADK detection works

When you add a new ADK version, OneDeploy uses the Windows ADK installed on the Management Computer accessing the WebApp.

The ADK is not automatically detected from the OneDeploy server. Instead, the Management Computer must have the required ADK version installed before it can be added.

When you click Add, OneDeploy will import the ADK tools and Windows PE components from the Management Computer into the OneDeploy environment.

Common Questions

Does adding a new ADK version automatically upgrade my Boot Profiles?
No. Boot Profiles are not changed automatically. You decide when to switch to a newer Windows PE version.

When should I use the Add button?
Use Add after installing a newer Windows ADK version, to import its tools and WinPE components into OneDeploy.

What does Add WinPE from ADK do?
It imports an additional copy of the Windows PE environment from an ADK version that is already available in your environment.  You can import multiple copies, even of the same WinPE version to enable testing.

Which machine does OneDeploy use to detect the Windows ADK?
OneDeploy uses the Windows ADK installed on the admin workstation accessing the WebApp. The ADK must be installed locally before it can be added.

This sounds complicated — when will I actually need to use this?
In most environments, you won’t need to use the ADK Versions area at all. It is intended for advanced scenarios, such as when you upgrade to a newer version of the Windows ADK and want to import the updated tools and Windows PE components into OneDeploy.

For the majority of day-to-day deployments, the default ADK version configured during onboarding is sufficient. You would typically only return here in the future if you install a newer ADK version and need to click Add to make it available.

Related Articles

• Boot Profiles
• Windows PE
• ADK Versions Overview
• Deployment Sources