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

Download

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:

  • ConfigMgr OSD FrontEnd now supports running a single command while the splash screen is shown and before the frontend loads. While this prestart command may only seem to support a single command being executed, it’s designed to support executing PowerShell that could be leveraged to run additional commands inside a PowerShell script file.
  • When the splash screen is shown, a new functionality is added to this phase of loading the frontend. While loading, the frontend will now wait for an active network connection for any WiFi or Ethernet adapter.
  • In previous versions, you could not use ConfigMgr OSD FrontEnd as a prestart command for USB boot media. This has now been fixed, and the error that occurred when clicking the Apply button is now gone, and the frontend is now capable of logging correctly.
  • ConfigMgr OSD FrontEnd and ConfigMgr WebService version information is now shown in the flyout menu.
  • In addition to the check running after the splash screen is shown whether the ConfigMgr WebService is reachable, another check is introduced in this version that validates the minimum required version of ConfigMgr WebService is being used.
  • SerialNumber property from WMI is now shown in the details panel (expandable) under the Computer tab.
  • A bug to the control showing the operation details above the progressbar has been addressed. Some messages were cut off due to insufficient space set for the control.
  • The check that runs to verify that ConfigMgr WebService is reachable, used to have a timeout of 2 seconds. This timeout has been increased to 10 seconds from this version and onwards.

Dependencies

ConfigMgr OSD FrontEnd 1.2.0 requires ConfigMgr WebService 1.4.0. You can download ConfigMgr WebService from below:

ConfigMgr WebService 1.4.0

Documentation and usage

Embedded in the download package for ConfigMgr OSD FrontEnd is a PDF file called ConfigMgr OSD FrontEnd 1.2.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
Principal Consultant 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. Currently working for TrueSec as a Principal Consultant. 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 and user groups.

(2018)

comments
  • André Lindqvist
    Posted at 08:49 September 22, 2017
    André Lindqvist
    Reply
    Author

    Nice!

  • Dillon
    Posted at 20:52 September 26, 2017
    Dillon
    Reply
    Author

    Hello,
    I am getting an error when trying to hit apply after running the OSD.

    “Error”
    Empty Path name is not legal

    I do not see any issues with the config file. The web service is running 1.4.0

    • Nickolaj Andersen
      Posted at 17:34 September 27, 2017
      Nickolaj Andersen
      Reply
      Author

      Hi Dillon,

      Yeah, this was an issue that has now been addressed. Just re-download the package and replace OSDFrontEnd.exe with the updated one.

      Regards,
      Nickolaj

  • Gareth
    Posted at 08:35 September 27, 2017
    Gareth
    Reply
    Author

    Very cool Nickolaj. I have an error just before applying the Build saying “Empty path name is not legal.” Do you know if this could be related to information in exe.config file that is missing perhaps?

    • Nickolaj Andersen
      Posted at 17:35 September 27, 2017
      Nickolaj Andersen
      Reply
      Author

      Hi Gareth,

      There’s nothing wrong in your configuration, this was an issue on my end that has now been corrected. Please re-download the package and replace OSDFrontEnd.exe.

      Regards,
      Nickolaj

  • Daniel
    Posted at 04:54 October 11, 2017
    Daniel
    Reply
    Author

    Just to add to this, When i go to the Webservice url https://Server.Name/ConfigMgrWebService/

    it says at the top of the page

    Web service for ConfigMgr Current Branch developed by Nickolaj Andersen (v1.4.0)

    The following operations are supported. For a formal definition, please review the Service Description.

    ********-****-****-****-**********

    Everything works when i do queries from the webservice page and it is pulling correct information from SCCM /AD. I am not sure why the OSDFrontEnd component is seeing something different

  • Daniel
    Posted at 23:49 October 11, 2017
    Daniel
    Reply
    Author

    OK im seriously stuck with this, i posted yesterday but it seems to have gone. I had Web Service (1.3) installed on my sccm server. I have installed 1.4.0 over it and trying to use the OSD 1.2 however it says unsupported version of configmgr webservices installed. I tried to run this on a completely new server that has never had any of these tools before however the problem just follows. I keep getting Unsupported version of ConfigMgr WebService detected. Required minimum version is 1.4.0, current implemented version is BLANK.

    This tool looks really handy however it just wont detect that the webserver version 1.4 is installed. HELP!!

    Any advise would be greatly appreciated. I am not sure if its a problem with the webservices or a problem with the OSD Front End 1.2.0 download.

  • Daniel
    Posted at 11:06 October 13, 2017
    Daniel
    Reply
    Author

    Ok After a week of banging my head i found out what the problem was and it was nothing to do with the registry keys. I was using https:// with mydefault website configured on port 443. Fort he fun of it i enabled port 80 on IIS for the default website and changed it from https:// to http:// within the OSDFrontend .xml file. Guess what, it worked. I am now able to launch the osdfront end in debug mode without any errors.

    Atleast now i know where to look to try and resolve this issue. Just thought id let you all know

  • Pete
    Posted at 21:59 October 16, 2017
    Pete
    Reply
    Author

    Thank you @Daniel for letting us all know. I have exactly this issue and also have been banging my head against the wall.

  • Leave a Reply