Upgrading to Windows ADK
Upgrading to Windows ADK
Due to the new UEFI compatibility in OSD, the previously used Windows AIK cannot be used anymore and must be replaced by the Windows ADK. The following scenarios are possible:
- Internet connection is available on the OSD Manager
The OSD Manager configuration window has a button that allows the user to download and start the installation of the Windows ADK. No Internet connection or proxy on the OSD Manager
The Windows ADK must be installed manually, using cached files from a computer with Internet connection and a specific command line to download the cache.Failed to execute the [confluence_note] macro.
Upgrading to WADK with Internet
This procedure guides you through the steps to install the Windows ADK (WADK) via the CM console. This procedure requires a working Internet connection on the OSD Manager device.
- Select the OS Deployment > Your OSD Manager node.
- Select the Configuration subnode.
Click Properties
.The Properties window appears on the screen. If you have already upgraded the agent to version 12.1 the former Windows AIK path was replaced with the default WADK installation path. The Windows ADK Status box displays the Unknown message and the overall Status box shows Windows ADK could not be found. . 
- (Optional) If you want to install the WADK not in its default location, modify the path in the Windows ADK Path box.
- Click Test next to the Windows ADK Status box.
The CM agent now verifies if the OSD Manager has a working Internet connection and displays the result in the Windows ADK Status box. If the OSD Manager does not have a working Internet connection, see Installing the Windows ADK manually for instructions on how to install the WADK manually. If the status Internet installation available is displayed the label of the button changes to Install Windows ADK . - Click the Install Windows ADK button.The CM agent starts the download of the WADK installation package now and runs the installation. You can follow the progress via the different status values displayed in the Windows ADK Status box. The final status is Windows ADK installed . If the installation fails, see Installing the Windows ADK manually for instructions on how to install the WADK manually.
- When the final status is displayed click the Check Environment button at the bottom next to the overall Status box to verify your environment.If the WADK installation is correct and all your other parameters are still valid the status OK is displayed.

Your OSD Manager is now updated and correctly configured; it is ready for creating and deploying operating systems in your network.
Installing the Windows ADK manually
If your OSD Manager does not have an Internet connection, you must download the Windows ADK (WADK) via another computer with Internet connection.
- On a computer with Internet access go to http://www.microsoft.com/en-US/download/details.aspx?id=39982 .
- Download the adksetup.exe and save it locally.
Run in a terminal window as administrator the following command:
adksetup /layout <path>
whereby <path> is the location where the downloaded files are to be stored.
- Copy the complete download with all directories and files to the OSD Manager.
- Open a terminal window on the OSD Manager as administrator.
- Go to the location of the downloaded cache.
Run the following command:
adksetup /quiet /installpath <path> /features
OptionId.WindowsPreinstallationEnvironment OptionId.DeploymentTools /log <path>
whereby
- installpath <path> is the full path to the installation directory of the Windows ADK.
- log <path> is the full path, where the WADK installation log is to be stored.
Installing the Windows ADK manually with Internet connection
It is also possible to manually install the Windows ADK on the OSD Manager with an Internet connection.
- Go to http://www.microsoft.com/en-US/download/details.aspx?id=39982 .
- Download the adksetup.exe and save it locally.
- Launch the adksetup.exe .
The installation wizard appears on the screen.

- Select at least the Deployment Tools and Windows Preinstallation Tools (Windows PE) components, these are required for OSD to properly function.
- Follow the installation instructions as explained by Microsoft: https://msdn.microsoft.com/en-us/library/hh825494.aspx .