Knowledge Article
Client Management - OS Deployment - Setting up and Initializing the OSD Manager - Install ADK manually
A crucial part after meeting the prerequisites to deploy the operating system on the bare metal machines it to set an OSD manager to create and manage the OSD projects.
BMC Client Management
Client Management
BMC Client Management (BCM) >=12.7
How do I start with the OS Deployment? How to add a new OS Deployment (OSD) manager and initialize it? I heard that the version of ADK that currently ships with BCM is quite old, is there a way to use it with a more recent version of ADK? Is it supported? I have newer hardware, and as a consequence I have to manually add deployment drivers to my projects, is there a way so I don't have to add so many NIC or SATA deployment drivers myself? |
The detailed prerequisites to install an OSD Manager can be found in the official documentation. There are a few important ones that must be met in order to start using BCM.
Some more information on the prerequisites in the official documentation here. There are two ways of installing Windows ADK: A- manually: to use a more recent version than 1703, up to 1903 included, it is necessary to install ADK manually.
B- through the console: ADK 1703 is installed to the console, which is fine but includes drivers that are not up to date for recent hardware. 1- Select an OSD manager: - select the device that is going to be the OSD manager and click OK. This step will enable OSDeployment module on the selected device. - right click on 'Configuration' of the OSD Manager and click Properties. - click 'Test' button to check if the it finds the installation of ADK on the drive. If it shows Installed, then click on "Check Environment" button, and finally click OK. If it is not installed it will not be possible to finish the OSD manager configuration. 2- ADK installation A- Manually: Notes: - Prior to the release of Windows 10 1809, ADK and WinPE were a part of the same installer. Since Windows 10 1809 the ADK and WinPE are released with separate installers and need to be downloaded and installed manually. Download the same or higher version of ADK compared to the images that will be deployed. Example: if Windows 10 1903 image is going to be deployed then download ADK 1903 or higher. The lower version of ADK also works however the drivers must be compatible with the lower version of ADK. - No version > 1903 must be installed as of BCM 20.08. More information in this KA: Client Management: OS Deployment - Is ADK 2004 supported? Installation: - download Windows ADK and WinPE Add-on from Microsoft's official website. adksetup.exe and adkwinpesetup.exe files will be downloaded respectively, as described in this documentation.
- run adksetup.exe and select 'Deployment Tools' feature to install after accepting the EULA. Keep the default installation directory to 'C:\Program Files (x86)\Windows Kits\10\' - run adkwinpesetup.exe and select 'Windows Preinstallation Environment (Windows PE) feature to install after accepting the EULA. B- From the console: It is easier for the admin to install ADK, but as mentioned in the introduction, the ADK version that ships BCM is quite old. Because of this it will be necessary to find and add deployment drivers more frequently that if a more version of ADK would be installed on the OSD manager. Please refer to the KA 000375419 for more information on how to install it manually. 3- Initialization: Once the ADK installation will be complete, either by the automatic or the manual ways, click on "Check Environment, then on "Ok". The winpe files start to build: Check the 'Initialization Status' progress to monitor the progress. Do not start creating projects etc until the status has moved to "Initialization Complete", as shown above. |
Attachment(s):