ConfigMgr OSD FrontEnd – Version 1.5.0 released

We’re proud to announce the release of ConfigMgr OSD FrontEnd version 1.5.0.


More information about ConfigMgr OSD FrontEnd is available on the following page, including download link and release notes:

ConfigMgr OSD FrontEnd

What’s new

Below is a list of enhancements and new features made available in this release:

  • New Harddisk section that allows for selecting what hard-disk the operating system image should be installed to. This section detects all available physical disks on the system and displays them in a datagrid.
  • Authenticate section has been improved to support an Enter keystroke that triggers the Log in button without manually clicking it. In addition, this section now includes a new feature that counts the amount of remaining login attempts. When the specified amount of failed login attempts is reached, the frontend will display a message and then shutdown causing the system to restart.
  • Authenticate group box is now called User authentication instead of previous Windows authentication, this change was introduced for a more convenient end user experience.
  • Preflight section has been improved and now features a datagrid showing either red or green depending on the state of each check that has been enabled. This change aligns better with the overall design of the frontend and supports for future additional checks to be added without a graphical change in the controls used. In addition, a new application configuration setting is added to allow for automatically bypassing the Preflight section if all checks passed.
  • Application section has been improved and now supports specifying if a whole group of applications should be pre-selected in the frontend. Additionally, configuring individual mandatory and/or pre-selecting applications is now included in the AppConfig.xml. This removes the requirement of specifying mandatory apps in the OSDFrontEnd.exe.config file and can more dynamically be handled like with the other XML configuration files on a remote server. With this change, the AppsMandatory and AppsMandatoryLock application configuration settings are now deprecated and should not be used from this version and onward.
  • A new application configuration setting named DirectoryDNRoot has been added to specify the starting distinguished root for the Directory section.
  • A Refresh button has been added to the Directory section to re-load the directory data from the domain controller.
  • Computer section label next to the computer name field has been changed to Name of the computer.
  • New computer details have been added to show status for TPM ownership, if the TPM chip is enabled and if it’s activated.
  • When the computer name is being validated against Active Directory, if an object with the specified name already exists, the description of that object is displayed in the message that appears.
  • The main progress bar is now shown when the frontend is loading task sequence details, this was not the case in previous versions.
  • Improved the button style layout for the fly-out admin mode to align with other button styles used in the frontend.
  • Added a Refresh button for the Regional section to re-load the XML configuration from RegionalConfig.xml.
  • Improvements to the XML load behavior of the frontend has been made. If there’s a parsing error or file missing or not found issue, an error message is displayed.
  • Fixed an issue where the frontend would crash if the Directory section was enabled and the user would click on the top-level domain name in the tree view.
  • Fixed an issue where the frontend would crash if the wrong password for an user was entered in the Authenticate section.
  • Fixed an issue where the computer name would not be retrieved from ConfigMgr when the computer entry was manually imported using the MacAddress identifier.
  • Fixed an issue where the Application section would show retired applications.
  • Fixed an issue where the keyboard layout was not loaded quick enough and would populate with a value a few seconds after the frontend was visible to the end user.
  • The following is a list of the new application configuration settings that have been added in this version:
    • IsHarddiskEnabled
    • HarddiskAutoContinue
    • PreflightCheckSuccessContinue
    • DirectoryDNRoot
    • DirectoryDomainName
    • AuthenticationMaxLoginAttempts
    • AuthenticationMaxAttemptsTitle
    • AuthenticationMaxAttemptsMessage
  • These application configuration settings have been deprecated in this version:
    • AppsMandatory
    • AppsMandatoryLock


ConfigMgr OSD FrontEnd 1.5.0 requires ConfigMgr WebService 1.7.0. You can download ConfigMgr WebService from below:

ConfigMgr WebService 1.7.0

Documentation and usage instructions

Embedded in the download package for ConfigMgr OSD FrontEnd is a PDF file called ConfigMgr OSD FrontEnd 1.5.0 – Documentation. This file contains all the information regarding how to get started, detailed explanation of how to use the frontend and some tips and tricks.

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.


  • Sorry if this is a duplicate, but I can’t see my original post 🙁

    Since i updated my boot image to 1809 OSD Front End no longer works. No errors or anything, it just starts, stops immediately and returns error 255. It works fine everywhere else, just not in the PE environment. Is there a missing dependency somewhere?



  • Quick question: on which site servers is the ConfigMgr Web Service required for this solution to be fully functional? We have an extensive environment with 9 primaries and ~230 DPs… is it required on the DPs or just the primaries where policy is pulled?

    • Hi, you can install it basically anywhere as long as you’re able to communicate with the SMS Provider (meaning on what server it’s currently installed). I normally recommend the primary site server if possible. Regards, Nickolaj

  • Lost functionality when upgrading to SCCM 1810
    “no task sequence available for this computer”

    I think the problem started when I upgraded the Boot Images to 10.0.17763.1

    smsts.log =
    SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (..\tsremovablemedia.cpp,387)
    No assigned task sequence.

    tips are appreciated 😉


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