ConfigMgr OSD FrontEnd 1.6.0

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 ;)

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.

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/

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?

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? 

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.....

Anyone have any issues imaging a HP EliteBook x360?

I was able to get it to PXE Boot with the correct drivers, however when I get to the final OSD Frontend screen and click apply\start the WPF application shuts down and the device reboots.  I have confirmed that the Task Seq ID was set correctly in the log before hitting start, but it does not actually start the task sequence.

Ideas?

Hi,

i'm trying to get working this great tool, but when I set the OU path on OSD Frontend once the TS finishes the computer is no moving to that OU.

Regional and other stuff is working fine ... what I'm supposed to check ? the Root path is filed, so the frontend shows the source OU and subfolders .... but no matter what OU I choose ... nnothing happens at the end.

Any suggestion would be appreciated

Thank in advance

Hi,

If the computer is already created and placed in one OU, the object will not be moved, if the object is not preexisting in the AD, the object will be created in the OU selected at the directory tab.

I had the same problem and didnt understand why untill i got some answers.
The Directory is the same as the "join Domain"-step, its only a domainjoin function and not moving between different OU's.

I made a powershellscript that works for me, that uses the variable set in the "directory"-step, and then use the web service to move the object if already existing.
Otherwise, it will just be created at the OU selected.

LoveA, any chance of seeing hat powershell script? Would be nice to add to my TS to get the computer moved where I want.

Sure, send me and email and i will send it over.

I uploaded the script to a repository.
It's just an edited script from the samples folder, but i found it working quite well. 

https://github.com/Love-A/Love-A/blob/master/MoveADComputerToOU.ps1

Thank you kindly!

Hi,

OSD FrontEnd 1.6

I am some issues with the Restricted Task sequences.  It works in all cases if the machine is an Unknown Device, correctly states that they are authorized packages, and displays them in the drop down.   However if it is a Known device, the log will see the FrontEnd will see the task sequences, but state that it is not authorized.  I have about 6 Deployments to both a separate known and unknown collections.  I have also verified that the Package IDs are listed in the DeployConfig.xml file as authorized packages.  

Anyone have any ideas?  Workaround is to just disable the restriction, but it is a really nice feature and I would like to use it.

Any ideas at all?  Still seeing the same behavior and it is quite frustrating...

I am just trying to figure out the functionality. How does the Task sequence selection works out. What should i change in DeployConfig.xml??? How to make it appear in the Front end????
Thank you noobs

Is this actually a serious question?  Cannot tell from how you phrased it...

All of that is described pretty thoroughly in the Documentation that is included in the download.