Automated Deployment for managed devices - Command Line to Configure SEB with encrypted .seb file

[ntbutler-nbcs]

Hi there.

Is it possible to configure SafeExamBrowser after installation (via .msi deployment) automatically?

We have an examination platform that generates an encrypted .seb file which is exported for "configuring a client". For our managed devices, after a re-image or deployment of the SafeExamBrowser software, our staff also are currently needing to log in to each device, download and double click the encrypted .seb file, and then enter the encryption password.

Is it currently possible via command line arguments or similar to specify a .seb file and an encryption password, so that we can script the configuration of the clients during our re-imaging or deployment process?

If not, could this be something added to the next version?

Thanks!
Nathan

[dbuechel]

You can simply place the local client configuration either under %ProgramData%\SafeExamBrowser or %AppData%\SafeExamBrowser, see also https://safeexambrowser.org/windows/win_usermanual_en.html#ConfigFilePane.

[ntbutler-nbcs]

But that doesn't seem get around the fact that we still need to then log in to each machine, launch the browser and enter the password. In fact it then appears to require the configuration password to be entered every time the SEB software is launched, which is further from the solution that we're aiming for?

To clarify further, the exam platform provides a configuration file (with the sebConfigPurpose property set to 1) and the .seb file is encrypted with a password that is provided to us, so we can run the seb file on institution-owned devices, enter the password, and have them set up then with a default configuration. My understanding of the method suggested above is that our seb file would instead have to remain unencrypted, or would have to have the password entered on every launch?

[danschlet]

Password-encrypted configuration files were not meant to be used for client configuration. Password encryption might make sense for exam configuratiions (even though the encryption doesn't help from the moment on when students get the settings/exam password). It's way more important to use an SEB integration which checks the Config Key or Browser Exam Key (or SEB Server with the App Signature Key).

For managed clients, you could use identity certificates (containing a private key). Distribute those onto your managed devices and encrypt the SEB config files with that certificate (see manual).