We’re proud to announce the release of ConfigMgr OSD FrontEnd version 1.5.1.
More information about ConfigMgr OSD FrontEnd is available on the following page, including download link and release notes:
- Fixed a bug when the ComputerNameFromCM application configuration setting was set to True, causing existing user relations in the User section not to load.
- Improved the unknown computer object detection, that previously required the end user to enable a slider control, by now showing a message box with a remove button that’ll remove the object and allow for task sequences to be shown in the drop down menu.
ConfigMgr OSD FrontEnd 1.5.1 requires ConfigMgr WebService 1.7.0. You can download ConfigMgr WebService from below:
Documentation and usage instructions
Embedded in the download package for ConfigMgr OSD FrontEnd is a PDF file called ConfigMgr OSD FrontEnd 1.5.1 – 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.
A couple of questions:
1. How should the task sequence be configured for the Front End?
2. How to start the FrontEnd from bootable media?
Check out the documentation (PDF) included in the zip-file you downloaded. It covers all your questions.
How do I configure our Task Sequence in conjunction with the FrontEnd? What needs to be configured in the Task Sequence?
We’re running ConfigMgr WebService 1.7.0 and everything works for Modern Driver Management. But when trying OSD FrontEnd 1.5.1, it says the required minimum version is 1.7.0, current implemented version is blank. It doesn’t have one. I saw where previously this was an issue with incompatibility in a new function call. Could this be similar?
Could you simply just try to get the ConfigMgrWebService.dll from the downloaded .zip file and put it in the /bin folder of the web service?
I am having an issue with this version which happens on about 1/3 of clients. After running through the wizard and continuing, there is not TS found, and the logs show this message:
Provided preferred deployment XYZ000012 is not found among the available deployments. This workstation is an existing workstation and is not unknown. It exists in the collection that gets that provided deployment ID. Also, I have troubleshot similar issues where the unknown device IDs are duplicated, but that is not the case here. I am on the latest version of both the OSD FrontEnd and the WebService. Thanks in advance!
Actually, it looks like this was already covered here: https://msendpointmgr.com/2018/11/23/fix-windows-adk-version-1809-issue-with-crashing-wpf-applications/
Does anyone have OSDFrontEnd working with an 1809 boot image?
We just upgraded from a functional 1.4 install on an 1803 boot image to an 1809 boot image with 1.5.1 and Web Service 1.7, and the OSDFrontEnd exe runs fine on a PC in debug mode, but in PE it immediately exits with code 255. I’ve tried swapping 1.5.1 with 1.4 and see the same behavior, I also confirmed that the necessary optional components are selected for the boot image and have tried building a new boot image.
Just want to say that the OSD Front End is awesome! But there is one thing I’ve noticed and I’m not sure if it is expected.
I currently have the “ComputerNameLock” set to TRUE and I use only a “ComputerNameByScript” for naming. After my script inputs the computer name, the textbox is locked and not editable. Then if you select “validate”, afterwards the textbox will now be editable by the user.
Is this to be expected?
This is not expected and fixed in 1.6.0 that’ll be released shortly.