ConfigMgr Prerequisites Tool – Version 1.4.1 has been released

Now that Windows ADK 10 has been released for managing deployment for Windows 10, I’ve updated the ConfigMgr Prerequisites Tool with capabilities of downloading the latest version of Windows ADK.

Release notes

This minor update to the tool includes the following:

  • Support for Windows ADK 10 and previous version Windows ADK 8.1. A new ComboBox has been added giving you the option to choose what version to install.
  • Minor fixes in the code.

I plan to add more options to this tool in the future, like installing prerequisites for a Distribution Point on Windows 7 or Windows 8.1

Download the ConfigMgr Prerequisites Tool

As with previous realeses, you can download the tool from the TechNet Gallery.
I hope you enjoy this new version, and please report any issues that you may have with it.

Nickolaj Andersen

Chief Technical Architect and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences such as Microsoft Ignite, NIC Conference and IT/Dev Connections including nordic user groups.


  • I am having major problems running this on a Server2008R2 box. I keep getting the error:
    You must provide a value expression on the right-hand side of the ‘-‘ operator.
    My command is “powershell -file .\filename.ps1
    It is also being ran under Unrestricted execution policy

    • Hi Steve,
      You need to install Windows Management Framework 3.0 (which includes PowerShell 3.0) for the tool to work.

  • First: great site and scripts.
    Though, found an issue in the script.
    You enumerate string values like integers. As they are evaluated by position, your script incorrectly handles ie buildnumbers wrong when it comes to Windows 10 / Server 2016.
    I used your script on Windows Server 2016 build 10514 and it would say that OS is not supported. Culprit is here:
    line 469:
    if (($OSProductType -eq 3) -and ($OSBuildNumber -ge 9200)) {
    Changing it to following solves it:
    [int]$OSBuildNumber -ge 9200
    Perhaps you could change your script to change datatypes accordingly before evaluation.
    Cheers, keep up the good work!

    • Hi Herman,
      Great find, huge mistake when you’re testing the code on Windows Server 2012 R2 where it actually works, but for Windows 10/Windows Server 2016 TP it doesn’t as you’re showing. I’ll update this, thanks for pointing it out. I think I’d have to do a thorough code review, as much of it are still pretty old that I wrote when I was a newbie at PowerShell.


Categories use cookies to ensure that we give you the best experience on our website.