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.8 Star
(18)
9,544 times
Add to favorites
System Center
7/5/2019
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Supported HWModels.txt
    1 Posts | Last post Wed 11:05 PM
    • Is it possible to have the option for the FrontEnd to check against the ConfigMgr Webservice, https://www.scconfigmgr.com/configmgr-webservice/, for supported hardware models instead of using HWModels.txt
      
      This would help for Lenovo computers where you could support a ThinkCentre M900, but the driver pack doesn't support all sku's of that model.
  • Unknown Devices - DeployRestrictTaskSequenceSelection
    2 Posts | Last post Wed 8:54 AM
    • Question, are all task sequences supposed to be shown in the drop down list even if “DeployRestrictTaskSequenceSelection” is set to true when the device is detected as UNKNOWN?
      
      When I debug from a known machine, I get the correct task per the user’s group. I can also see it check each task against what’s approved in the Logs. But on an unknown machine, it always list all available task sequences. In the logs, it shows that it finds what’s supposed to be available per the user’s group, but afterwards it goes into device detection, detects the device as unknown and then list all task sequences.
      
      Couldn’t find the answer to this in the documentation, hoping to find it here.
    • Digging a little more, I see that I'm having an issue with the web service.  Seeing this error in the event manager "An error occured when attempting to locate Active Directory object. Error message: The specified domain either does not exist or could not be contacted." I'm stumped at this point.  Anyone able to offer any advice? 
  • Restarted workstation when authentication attempt
    1 Posts | Last post November 01, 2019
    • Hello. Many thanks for your development.
      We use ConfigMgr OSD FrontEnd with the step of pre-authentication of the user. There is an Active Directory group with several hundred authorized users to perform deployments. For the vast majority of authorized users, the authentication process and subsequent deployments occur perfectly, except for a single account. At the moment of authentication attempt (Checking group membership for authenticated user) the workstation is restarted. OSDFrontEnd.log file reports a successful user verification and ends with:
      	Authentication: Authenticated user is a member of specified group;
      	Authentication: DeployRestrictTaskSequenceSelection setting enabled, querying for group memberships for authenticated user.
      smsts.log file contains an error entry:
      	Process completed with exit code 3762504530;
      	uExitCode == 0, HRESULT=80004005 (tsmediawizardcontrol.cpp, 545);
      	'OSDFrontEnd.exe' returned error: 0xe0434352;
      	Successfully unregistered Task Sequencing Environment COM Interface.;
      	Authenticator from the environment is empty.;
      	Need to create Authenticator Info using PFX.
      
      The working environment is SCCM CB 1906 with ADK 10. Please help solve this problem.
  • Set Computername base on RegionalConfig
    1 Posts | Last post September 23, 2019
    • Hi,
      
      I try to set the computername by Script using a variable from RegionalConfig.
      This works perfect the first time running the wizard, but when i go back to Region and change the Region i think the script will not be run again.
      
      Thank you for sharing your tool and for any advice
      Michael
      
  • Assistance with name from Script
    3 Posts | Last post September 19, 2019
    • 
      Just wondering if i could get a tiny bit of help with pc naming convention. I am no expert in powershell and try my best but i occasionally get stuck like now. I am trying to make a naming convention that is "location"-"Type"-"Serial", i.e SYD-LT-A3g5c3.   I have the type and serial number down packed using the following script that calls on a xml file.
      
      Script is 
      
      $OSDComputerName = "UnknownModel"
      $ComputerModel = (Get-WmiObject -Class Win32_ComputerSystem | Select-Object Model).Model
      $SerialNumber = (Get-WmiObject -Class Win32_BIOS | Select-Object SerialNumber).SerialNumber
      $HardwareType = New-Object System.Xml.XmlDocument
      $HardwareType.Load("https://barn-sccm.barnho.barnardos.org.au/ConfigMgrWebService/OSDFrontEnd/HardwareType.xml")
      $Prefix = $HardwareType.Models.model |Where-Object {$_.Name -EQ $ComputerModel} | Select Name,Type,Prefix
      if ($Prefix.prefix -eq "HV-")
                      {
                      $OSDComputerName = $LocName + $Prefix.prefix + $serialnumber.substring($SerialNumber.length - 6,6)
                      }
      else
                      {
                      $OSDComputerName = $LocName + $prefix.prefix + $SerialNumber
                      }
      $Name = "$OSDComputerName"
      # Start-Sleep -Seconds 5
      Write-Output $Name  
      
      
      and the XML it reads hosted on the web server is 
      
      <Models>
      		<Model Name="Latitude 5400">
      			<Type>Laptop</Type>
      			<Prefix>LT-</Prefix>
      		</Model>
      		<Model Name="Latitude 5290">
      			<Type>Laptop</Type>
      			<Prefix>LT-</Prefix>
      		</Model>
      
      
      I would like to have the Location determined by the regionalconfig.xml and added to the name.
      
      
      My thinking is i have modified the regionalconfig.xml to have a extra line for setting name "OSDLocPrefix" 
       
    • <Configuration>
      <Site Name="SCCM-TEST">
      	<Setting Name="OSDUserLocale">en-AU</Setting>
      	<Setting Name="OSDInputLocale">en-AU</Setting>
      	<Setting Name="OSDSystemLocale">en-AU</Setting>
      	<Setting Name="OSDUILanguage">en-AU</Setting>
      	<Setting Name="TimeZoneName">A.U.S. Eastern Standard Time</Setting>
      	<Setting Name="OSDDomainOUName">OU=SCCM Test OU,OU=IT Infrastructure,DC=Company,DC=Com</Setting>
      	<Setting Name="OSDLocationName">Test</Setting>
      </Site>
      
      
      I have also changed the order in which the menu's are run by putting regional 1st.  
      
                          <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                              xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                              <string>Regional</string>  
      	         <string>Computer</string>
                              <string>Harddisk</string>
                              <string>Deployment</string>
                              <string>Directory</string>
                              <string>Role</string>
                              <string>Applications</string>
                              <string>Security</string>
                              <string>User</string>
                              <string>Custom</string>
                          </ArrayOfString>
      
      
      
      I can see when the osd runs in debug "TSEnvironment: Adding variable 'OSDLocationName' with value 'Test'"   From the powershell script above, what is the easiest and cleanest way to then read the OSDLocationName Variable and append it to the current name with something like "$OSDComputerName = $LocName + $Prefix.prefix + $serialnumber.substring($SerialNumber.length - 6,6)"
      
      
      Hope someone could give a tiny bit of advice and set me on the right direction.
      
      Thanks in advance.
      
    • I think the simplest way to achieve this is to ignore reading the xml all over again and just read from the location where the "OSDLocationName" is written too after selection the site in regional tab.  Can anyone advise where one the regional site is select and the log states "TSEnvironment: Adding Variable '%%%%%%' with the value '%%%%' . where this is actually added to and if i can read that using powershell.
      
      Pretty Please ;)
  • Application Installation Question
    3 Posts | Last post September 14, 2019
    • Hi,
      
      I am using SCCM Current Branch. And Windows 10 1809 as the image. I have the OSDFrontEND displaying applications. I have the task sequence step to install application and i have set the base variable to APPLICATION (the default in the osdfrontend.exe config file) The applications never install or even act like they are going to. It just breezes through that step. Am i missing something?
    • Hi!
      
      Try updating to the latest version now.
      Before this version, it didnt register pre-selected apps, you had to uncheck and check them again, and then they installed.
      
      
    • make sure you have the checkbox selected on the application in configmgr that says allow this application to be installed in a task sequence even if it is not deployed...that should resolve your issue.
  • does not appear during (pre-)start pxe-boot
    2 Posts | Last post September 13, 2019
    • Hi, 
      
      my problem is, that the frontend does not appear during pxe-boot. 
      My boot-image version 10.0.17763.1.
      I have added following components:
      HTML (WinPE-HTA)
      Microsoft .NET (WinPE-NetFx)
      Windows Powershell (WinPE-Powershell)
      Windows Powershell (WinPE-StorageWMI)
      
      Maybe there is something totally simple wrong. I didn't use the prestart command in my boot images before so I have no experience in this issue. 
      
      Any suggestions?
      
      greetings
      Sven
    • Hi, 
      
      I think I found the reason. 
      There was an error 'OSDFrontEnd.exe' returned 0x000000ff in the smsts.log in PE environment. 
      That was the solution. 
      https://www.scconfigmgr.com/2018/11/23/fix-windows-adk-version-1809-issue-with-crashing-wpf-applications/
      
  • Domain and workgroup
    2 Posts | Last post September 13, 2019
    • Hi!
      
      Has anyone had the scenario that you do both Domain joined devices and some that goes to workgroup/non-domainjoined.
      
      Im not sure how to set this up, cause i want the "Directory" step, but that will always show even when i want devices to go to domain. Can you just skip it in some ways or?
      
      Any tips?
    • Or is it not really a problem?
      If i just have the "networksettings/joindomain"-step disabled in the tasksequence for these non-domain devices, nothing will happen even if i make a choice in the "Directory" step?
      
  • Deployment Dropdown Empty
    5 Posts | Last post August 16, 2019
    • Hi, I really need some help with the Deployment tab's task sequence selector. I'm completely stumped here.
      I have 2 task sequences deployed as available to unknown computers (PXE and media hidden). I've been testing some task sequence changes and repeatedly deleting computer objects from SCCM and re-imaging. But starting last week, two of my test systems started not showing anything in the task sequence drop down - it's just blank.
      Using the same boot media I can test other physical systems or brand new VMs and they show the task sequences just fine.
      I made a new collection, set up advertisements, and used the "Import computer record" but it's not working that way either on these existing machines (it does work fine on brand new test VMs).
      I verified that in the main config file that the default task sequence is named exactly the same as one of my two task sequences that I've deployed (although I also think that shouldn't matter)
      I can't find what I'm missing, and can't find any good guidance on how to find/read logs for what OSDFrontend or the ConfigMgr web services is doing on the backend.
      I've tried recreating the task sequence deployments and that didn't help. I've tried running OSDFrontend in debug mode and that log was not helpful. I'm beginning to suspect that there's some kind of problem with the ConfigMgr web service (1.7.0) or with SCCM itself but the only log I know to find is the IIS one that just helps me verify that a connection to the web service was established.
    • What happens when you close the frontend with the X? Usually you should see the regular task sequence box with the task sequences that are available for your system. If nothing shows there just aren't any task sequences available. If something shows you have an ussie with the way you deployed your task sequences, usually there is no hidden deployment which is required for the TS to show up.
      
      It might also be a wrong record in SCCM. What helps in these cases is to delete the machine from SCCM and create a new entry and add the machine to the right collections that have the TS's deployed to them (one visible deployment, one hidden).
      
      We use the MAC Address of machines for identification.
    • When I close the frontend, I do see 3 or 4 task sequences that are advertised to Unknown Computers (set to boot media and PXE - not hidden. So it seems like SCCM recognizes that these are unknown computers, but the OSD Frontend is not showing my list of task sequences set to hidden and deployed to Unknown Computers.
    • Hi, I have the same problem.
      This one comes from the identification of the computer by the OSDFrontEnd.
      The computer is known in SCCM (Name and MAC Address) but the OSDFrontEnd detects the computer as unknown.
      I assure you that the computer is known otherwise SCCM would never let it start on PXE.
    • Did you solve it Zombie? 
  • Not reading set path for custom and directory configs
    2 Posts | Last post August 15, 2019
    • I have set the config to look on my webserver for all the config files, and it works for all except the above two, it is looking in the default location according to the log.
      
      ApplicationLoading: Loading Custom configuration file from path: http://server.domain.com/ConfigMgrWebService/CustomConfig.xml
      
      ApplicationLoading: Loading Directory configuration file from path: http://server.domain.com/ConfigMgrWebService/DirectoryConfig.xml
      
      I also set IsCustomEnabled to False, but it still wants to read it from the above location.
      
      Any ideas how I can force it to look in the correct place? 
    • Never mind, I just forgot to reload the boot image.....
1 - 10 of 74 Items