SCCM 2016 – ADK for Windows
As our base OS is Windows Server 2016, we will need to install ADK For Windows 10.
This can be downloaded from here
You can Install the ADK Setup via command line using Powershell as per below:
.\adksetup.exe /features OptionId.DeploymentTools OptionId.WindowsPreinstallationEnvironment OptionId.UserStateMigrationTool OptionId.ImagingAndConfigurationDesigner /q
You can remove /q switch to install using GUI but have feature selection done for you.
Alternatively you can install using the GUI. , To install ADK for Windows 10, double click on “adksetup.exe”.
Specify the Install path if required to be other than default path. Click Next to Continue
Select whether or not you would like to participate in Windows Kits Privacy. Click Next to Continue
Accept the License Terms to Continue
Select the required features.
Install the following components
- Deployment Tools
- Windows Pre-installation Environment
- User state Migration tool
- Imaging and Configuration Designer (ICD)
Click Install to begin installation
This will install the ADK for Windows 10.
Use following links to go to required blog
Comments: 6
you don’t mention why we should install the adk…
The Windows ADK provides basic forward compatibility and can be used for image capture, image apply, driver injection, and offline update servicing of Windows.
Hey,
you forgot the SQL Server 2016 installation, right? 🙁
Hi Mark
I did not forget it, but it is not covered in SCCM blog.
If you are looking to install SQL 2016, then please follow SQL 2016 Install blog
https://harmikbatth.com/2017/01/17/installing-sql-server-2016-on-windows-server-2016/
Harmik Batth
Hi,
I have got the following error at the end of the installation process.
ERROR: Failed to execute spConfigureServiceBroker $$
ERROR: Failed to ExecuteConfigureServiceBrokerSp $$
Not recovery mode or not top level site. Skip restoring client piloting packages. $$
~~===================== Completed Configuration Manager Server Setup ===================== $$
Could you help me?
Brgds- Parag
Hi Parag
This is normally caused by firewall and in specific check in the logs.
Check SQL ports are not blocked on SQL Server windows firewall
Rgds
Harmik