ConfigMgr OSD FrontEnd 1.6.0

ConfigMgr OSD FrontEnd has been developed with the goal to function in any environment, making the native operating system deployment experience with System Center Configuration Manager more unified and easier to use.

4.9 Star
9,195 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
Sign in to ask a question

  • Few Feature requests
    2 Posts | Last post January 10, 2019
    • Hi Nickolaj,
      Is it possible to have pre-flight skipped if all checks return OK?
      Also, Is it possible to reference the default config file from a web server to enable on the fly changes/updates as opposed to updating the boot image? maybe a /config:http://site.fq.dn/app/config.xml flag and maybe a fallback config too if the primary is unavailable (Feature is available in UI++ for example).
      Could we also in the AppConfig.xml specify if a group is Mandatory and maybe even put a specifier on their like if ChassisType=Laptop then mandatory etc. This could help reduce the need to manually update the main config file with mandatory apps if we can config as part of the apps specification. The mandatory lock should still have the same effect on these apps too.
    • Hi Marcus,
      Pre-flight will get a facelift in version 1.5.0 with a datagrid instead of the stackpanels and rectangles used today. I'll add this to the list but unsure if I can make that with 1.5.0.
      Unfortunately that's not possible with the OSDFrontEnd.exe.config file, it has to be in the same directory as OSDFrontEnd.exe.
      That's planned for a future release with the mandatory groups for applications. Mandatory applications will be moved from the OSDFrontEnd.exe.config file into a new xml file that's possible to put on a webserver.
  • Windows Authentication bug?
    2 Posts | Last post January 10, 2019
    • Hello Nickolaj!
      Thank you for this really great tool! However, when I configured the Front End 1.4.0 (with webservice 1.6.0) in my lab env, I came across a possible bug during the Windows authentication step. It works fine if I enter my domain account and a correct password. It authenticates me and passes me to the next step. If the password is incorrect, the Front End hangs for a while and then the computer reboots. Is this a known issue? 
      Regards, Christian 
    • Hi,
      This has been fixed in version 1.5.0 that will be released very soon, stay tuned!
  • Only applications?
    2 Posts | Last post January 10, 2019
    • Great tool this frontend!
      I was wondering, we have a TS which is working great but we are looking for a tool which only gives a list of extra applications ready to install.
      Is this possible with this frontend?
      We already are using the driver management tool so the webservice 1.6 is already installed. We have Win7 and Win8.1 ready to migrate to Win10.
      ADK 1809 with CM 1806
    • Hi Michael,
      Sorry for the late reply. Currently with version 1.4.0 it's not possible to only use the frontend for a single purpose, like using the application section only. I'm thinking of enabling this for future versions, but there's quite a lot of code to refactor to support this. It's however on my todo list, but with no commitment yet.
  • Unable to load configuration file
    3 Posts | Last post January 10, 2019
    • Hi,
      The message "Unable to load configuration file for regional setting" always appears. I have the config-file in the same place as the OSDFrontEnd.exe and additionally in "http: //xxxx/ConfigMgrWebService/RegionalConfig.xml". No matter if I leave the item "RegionalConfigFileLocation" empty in OSDFrontEnd.exe.config or write "http: //xxxx/ConfigMgrWebService/RegionalConfig.xml" into it the error message always comes up. The URL is easily accessible in the browser.
    • chipDE,
      If you don't need to use the region file just set the flag "IsRegionalEnbaled" to false in the OSDFrontEnd.xexe.config
      I had the same issue and didn't need to utilise such feature so bye bye it went.
    • Hi guys,
      I'm unfortunately unable to reproduce this error when debugging. I have the RegionalConfig.xml in the root dir of the frontend but a proper URL is also configured for RegionalConfigFileLocation. Could you share a bit more on how to reproduce this?
  • Error in smsts.log when starting OSDFrontEnd.exe
    6 Posts | Last post January 10, 2019
    • Hi there Nikolaj or anyone else using OSD FrontEnd 1.4.0.  I'm getting error 'OSDFrontEnd.exe' returned error: 0x000000ff in the smsts.log in PE environment.  
      The symptoms I have is the VM just starts and OSDFrontEnd.exe never starts and when I view the smsts log this is the error thrown.  I do have have WebService 1.6.0 installed.
      Any suggestions would be appreciated.  What I've done so far.
      Re-download OSDFrontEnd
      Re-install WebService
      Repair WebService
      Removed Boot Image and create a new one.
    • I wanted to check if this has something to do with perhaps the ADK and WinPE 1809 updates?  Paging Nikolaj :)
    • Fix to the issue posted here by Martin Bengtsson 
    • The fix on Martin Bengtsson's site works like a champ.
    • Thank you so much for this!!!
    • This should be the proper solution on how to fix issues with the frontend and ADK 1809:
  • New system in ConfigMgr = Empty Computer Name
    3 Posts | Last post January 10, 2019
    • For some reason the frontend leave the Computer Name blank when we freshly imported a system into Configuration Manager. When we click on Details on the Computer tab all the needed information is there including the unique identifier we use (MAC Address). If we click next we see the advertised Task Sequences and after clicking Apply the frontend kicks off the correct TS and the system is being deployed with the name it is known by in Configuration Manager.
      When the deployment is succesfully finished and after doing some testing we kick of the PXE deployment again with the frontend and this time the Frontend displays the name in the Computer Tab.
      I don't know if we are the only one experiencing this issue. I guess it's easy to reproduce. Just import a new system into Configuration Manager with the MAC address as the unique identifier and start the system via PXE boot. First time system name is blank, all other times the name is correctly retrieved from Configuration Manager.
      Our detection method:
      <setting name="ComputerNameBySerial" serializeAs="String">
                  <setting name="ComputerNameByScript" serializeAs="String">
                  <setting name="ComputerNameFromMDT" serializeAs="String">
                  <setting name="ComputerNameFromCM" serializeAs="String">
                  <setting name="ComputerDetectionType" serializeAs="String">
      Anyone else experiencing this issue? We use Configuration Manager Current Branch 1802 with ADK 1803. All seems to be working fine. 
    • Thank you for reporting this, I'll try to reproduce it and include a fix in version 1.5.0.
    • I've found the issue and a fix has been implemented, would you mind sending me an email at and test out the fixed version?
  • Error message
    3 Posts | Last post January 10, 2019
    • I have configured a few options in the "OSDFrontEnd.exe.config" file and now when I attempt to chk the config by running "OSDFrontEnd.exe debug" I get the following error message:
      "Unsupported accent for application theme detected" and I have no idea what this means. I would guess by the error it was something "theme" related, but I've made no changes to the "theme" and/or interface for the frontend as of yet. Stumped!
    • Hello,
             You'll have to edit the OSDFrontEnd.exe.config. Change what you have currently in your config to make it match the following:
      <setting name="UIAccent" serializeAs="String">
                  <setting name="UITheme" serializeAs="String">
    • DrChuck is right, in the documentation there's a list of the supported values for these two settings.
  • OSDFrontEnd.exe debug not working remotely
    2 Posts | Last post January 10, 2019
    • When I run OSDFrontEnd.exe debug from a remote machine the Deployment section doesn't show any Task Sequences. 
      When I run OSDFrontEnd.exe debug from the SCCM server everything works for the OSDFrontEnd including the Deployment sections.
      Any fix for this type of problem?
    • Could it be that the remote machine you're running it from exist in ConfigMgr with a record but does not have any hidden task sequence deployments targeted?
  • having a few problems with v1.4.0
    2 Posts | Last post September 11, 2018
    • Hi Nickolaj,
      thanks for this nice tool. I'm trying to implement it but I'm running in a few problems. 
      First, I got it working at the beginning of the week, did a couple of loads and all. no problem. Yesterday I added some custom profiles to the regional file (which is served via the link) and today I can't get any test machine to go through the frontend. 
      I boot my usb stick, the frontend starts to load but it exits right after I click away the welcome message. I tried looking for the log file which I seem to recall finding in x:\windows\temp or x:\windows\temp\smstslog before (when the frontend was working) but I can't find it. So is logging only done from some point on, and not during startup of the tool? It could help to figure out why it's not working anymore now. 
      I've already tried with a brand new machine, deleted my regular test machine and imported it again, removed the hidden advertisement on the collection and put it back. Nothing seems to really help. I know initially I configured the <DeploySelectedTaskSequence> option in the config file. As it's not marked as mandatory I can leave it blank for the pull down menu you mention in the docs right?
      any help is appreciated 
    • From my experience troubleshooting- check the following (list not exhaustive but might give you some pointers)
      F8 and check you have a network stack (ip address etc)
      check your SMSTS logs in x:\windows\temp for any issues re the deployment
      Is your web service in place and working correctly? Use a web browser to point to the URL to get a response if you haven't checked.
      Check IIS on the server hosting the webservice and the app pool is running.
      If you get any sort of error where it says it cant read your regional config, triple check the XML file for typos. Easily done.
      Double check your XML config in the Boot ISO itself, and you treble check your config is correct and talking to the web service.
      Hope that helps.
  • TS Variables are not applied:
    1 Posts | Last post September 08, 2018
    • Hi Nickolaj
      Thanks for this great tool. I get the Front-END working, but come TS variables like Regional or Join Domain are not applied during the TS ... the computer name is correctly applied, I have no errors during the TS but the final configuration once is deployed is not the expected.
      I know that maybe this TS variables are overwritten during the TS progress ... but where ? how ? is there any chance to query or retrieve TS variables before TS starts ?
      Thanks a lot
31 - 40 of 67 Items