Programmatic Importing of Laser Profiles/Devices

[jpsimmonds (Justin)]

Good Day,

I have just been given the task of rolling out LightBurn to the school’s fleet of computers for use (floating licence) and whilst I have managed to automate the install and licencing of the product utilising available data I now need to import a laser profile/device configuration and ideally do this through command line as we cannot be opening the app on every device manually to configure it. Is there a way to achieve this?

[LightBurn (Oz)]

Do the users log in as themselves, or is there a specific account they’d log in to? The settings are all stored in the user profile, but you could pre-populate it with the preferences from a single initial system, and that would work. You can also export / import a device from the ‘Devices’ window, however we don’t have a way of doing this from the command line.

[jpsimmonds (Justin)]

The users sign in as themselves, so pre-populating is probably the way to go, how and where are the settings stored? if its registry based for instance I could simply put the keys in place, is it a file that I can dump?

[Stroonzo (Jeff)]

@jpsimmonds,

I think this is what you are looking for:

Upgrade - Lost settings

In LightBurn, go to File > Open prefs folder, then quit. In the prefs folder, you should see a folder called backup (if you’ve been keeping current). In there will be older copies of your preferences. Copy one of them over your prefs.ini file and run LightBurn.

[LightBurn (Oz)]

Jeff is correct - In LightBurn, open the prefs folder, then quit. Copy that prefs.ini file to the same location on other user profiles. Every LightBurn setting, including device config, is in there.

[jpsimmonds (Justin)]

Thanks guys, I will give that a shot

[Stroonzo (Jeff)]

I PowerShell
Just an idea… (possibly you could add this to the machines to run on log in, and if you ever wanted to update the master preferences, they would automatically cascade to the students on their next log in)

$MasterConfig = "\\ABC123\Share\prefs.ini"   #CHANGE THIS VARIABLE to be set to the UNC pointing to the prefs.ini source

$CurrentUser = $env:USERPROFILE   #current user's windows profile location
$Target = $CurrentUser + "\AppData\Local\LightBurn\"   #appending the current windows profile with the potential existance of a LightBurn folder

if(Test-Path -Path $Target){   #checks for the LightBurn folder

    Copy-Item -Path $MasterConfig -Destination $Target -Force   #if the folder exists then the master file is copied to the machine
    exit   #after copy, script exits

}

    else{
            exit   #if the LightBurn folder does not exist (application is not installed), the script exits
}

[jpsimmonds (Justin)]

We are kind of doing something similar at this point we are just pushing the prefs to the default profile so they are added to the users when they log in for the first time. This is possible as the devices are getting imaged, in future if we need to update the prefs we will go for something like this or an MSI that replicates itself to each user depending on how much InTune is capable of at that point

[Stroonzo (Jeff)]

Another issue I hadn’t considered (that you may face) is discussed in this thread:

Locking down machine settings

We got several machines using lightburn at a makerspace and would love to prevent users from going into machine settings. Is there any way to lock it down to require a password ? Thanks

Maybe this is a topic you and @achtepa can toss around for ideas on how to stop others from modifying the controller settings.