ConfigMgr OSD FrontEnd


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 easy to use. A frontend provides a graphical user interface for the common tasks that administrators and help desk personnel struggles with on a day to day basis using various custom made solutions.

This software requires the ConfigMgr WebService to function properly. For more information about how to download and install ConfigMgr WebService, visit the following page:

ConfigMgr WebService

  • This version brings a new user interface with many improvements that allows for instance the Regional header name to be 12 characters instead of 8. The overall layout of the frontend now has the menu on the left side instead of at the top. Sections now allow for more settings to be added including more menu sections for future releases.
  • For the Computer section there’s a new Validate button that performs an Active Directory computer object lookup to see if the specified name already exists.
  • A new section named Authenticate have been added providing the capability to authenticate a user in Active Directory. User name, password and domain name are used in combination to securely and encrypted validate the user if he or she is a member of a specific Active Directory group. Members of the group that is configured in the application settings for the frontend application are allowed access to continue with the deployment. Each login attempt through the frontend is logged in the event log for the frontend.
  • Visible task sequences in the drop-down menu for the Deploy section can now be restricted based upon Active Directory group memberships. This require additional configuration and only works when the Authenticate section is enabled, so see the detailed instructions further down in this document for how to use this new capability.
  • For the Apps section, there’s quite a few changes made in this version. Instead of requiring additional deployments for applications to show up in the frontend, applications being shown in the tree view are now based on a new XML file named AppConfig.xml that defines the folder structure and the administrative category in Configuration Manager associated with a folder. This change allows for a custom folder layout within the tree view and easier management of what applications are shown. Apps section is now also loaded directly when the frontend has started.
  • In the User section, it’s now automatically loads the existing UDA relations for the device when there are any available. They’re shown in a data grid similar to what’s used for the Roles section. It’s also possible to clear these existing relations, for scenarios like when the device is re-assigned to another user.
  • FirmwareType and BIOS version properties have been added to the Computer Details.
  • Aspect propertions for the logo.bmp file is now 160x90px.
  • There’s a new application setting named ComputerDetectionType that controls the property used from WMI when the frontend is attempting to identify the computer it’s running on. Previously, this was hard-coded for the UUID (SMBIOS GUID), but it can now be set to the MacAddress also, if needed.
  • xml file has been renamed to RegionalConfig.xml to follow the same naming standard as the rest of the XML files loaded by the frontend.
  • Sample code for running DaRT is now available in the PrestartCommand.ps1 file.
  • An error is now shown when the Apply button is clicked, but there’s no task sequences selected.
  • All referenced assemblies that previously was external to the frontend are now embedded in OSDFrontEnd.exe.
  • Removed application settings from the OSDFrontEnd.exe.config file:
    • AppCollectionID
    • HeaderText

Update 2017-09-27 - Download package updated to address the 'Empty path name is not legal' issue reported.

  • 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 on wards.
  • When using the frontend in a Configuration Manager hierarchy that contains a Central Administration Site with multiple Primary Sites, the hardcoded resource ids for Unknown Computer x64/x86 records caused the software to crash. This has been fixed in this version by querying the TSEnvironment for _SMSTSUnknownComputer[x64/x86]Guid variables to get the proper values.
  • 2 new application configuration settings, DebugUnknownComputerX64ResourceID and DebugUnknownComputerX86ResourceID have been added to support the debug operational mode to list task sequence deployments for unknown computers.
  • Required version of ConfigMgr WebService is now at least 1.3.0 or higher, for the frontend to fully function.
  • Fixed a bug when the ComputerNameFromScript application configuration setting failed to determine the location of the SetComputerName.ps1 script file.
  • Fixed a bug where no task sequence deployments would be listed for Unknown computers when using the ConfigMgr WebService 1.2.1.
  • From this version and onwards, the ConfigMgr OSD FrontEnd will be signed with a code signing certificate.
  • Latest supported version of the ConfigMgr WebService will from this version and onwards not be included in the package. A separate download of the web service is required.
  • Added an application manifest file to require elevated privileges when the application is executed.
  • Logo for executable changed to branding.
  • Improvements when setting the PowerShell execution during the splash-screen, now shows a message popup box with any errors or warnings that might occur when changing the execution policy (this message box will not cause the application to terminate once it has been acknowledged).
  • System.Management.Automation.dll is no longer a required file that needs to be in the working directory of the frontend software. Local assembly will now be referenced instead.
  • New Apps section for application installation, provides functionality to specify mandatory applications including optional.
  • Support for disabling Role, Regional, Apps and User sections. This will not disable the controls inside each tab-page, instead the disabled sections will not be shown at all.
  • Regional section header text can now be renamed by using RegionalTabHeaderText application setting, allowing for a maximum of 8 characters.
  • A welcome screen showing a title and message text, including Continue and Cancel buttons have been added. This message screen could also be utilized as a warning message that the computer is about to be deployed.
  • A splash-screen has been built for the frontend showing different loading stages before the main window appears.
  • Unknown computer objects can now be removed from within the frontend, if detected by the web service. This provides desktop technicians to be able to re-initiate a failed deployment.
  • New preflight check for supported computer models that compares the computer being deployed against a list of supported models located on a web server, configurable via TestSupportedHardwareFileLocation.
  • Frontend will not attempt to format the system volume when running in debug mode and FormatDiskWhenEncrypted is set to True, once the Apply button is clicked.
  • SQL Server related application settings in the frontend has been removed, as they were duplicate to what’s configure for the web service.

Initial release of ConfigMgr OSD FrontEnd.

ConfigMgr OSD FrontEnd provides a rich set of features and has been built with a focus on deployment of unknown devices, but also with the capability to support known devices for re-deployment.

An overview of the features ConfigMgr OSD FrontEnd provides are listed below:

  • Identification of hidden task sequence deployments based upon known or unknown device
    • Support to clear Unknown objects from Configuration Manager
  • Support for Unknown Computer mode in Configuration Manager
  • Computer name configuration
    • Manually enter a computer name
    • Generate computer name by serial number
    • Read computer name from external PowerShell script
    • Detect known device staged in Microsoft Deployment Toolkit and read the computer name
    • Detect known device from Configuration Manager
  • Associate a computer with multiple roles in Microsoft Deployment Toolkit
  • Set native or custom task sequence variables for regional configuration like keyboard layout, OU, time zone and more
  • Installation of mandatory applications and/or available applications
  • Associate a primary user with the device
  • Format hard drive if a volume is detected as encrypted
  • Pre-flight checks
    • Network connection type (not connected to WiFi)
    • ConfigMgr WebService accessibility
    • Power state (see if power adapter is connected)
    • Supported hardware models
  • Customizable color branding of the whole graphical user interface
  • Admin area for access to useful tools when troubleshooting
  • Welcome message with continue or cancel choices

Comments are closed.